-
Notifications
You must be signed in to change notification settings - Fork 696
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch Ubuntu APT sources to use HTTPS #7438
base: develop
Are you sure you want to change the base?
Conversation
Ubuntu now supports HTTPS on their primary mirrors, including archive.ubuntu.com and security.ubuntu.com. While APT verifies integrity using PGP signatures, there have been a few vulnerabilities in APT that would've been prevented by also layering TLS on top. No attempt is made to update the configuration on existing instances; instead this change will be made during the noble migration. Fixes #3286.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No attempt is made to update the configuration on existing instances; instead this change will be made during the noble migration.
In that case, @legoktm, shouldn't these tests be parameterized on securedrop_target_platform
? Otherwise, won't an Admin Workstation updated to v2.12 expect to see https://
URLs on a Focal-based Server running v2.12 still with http://
URLs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, yes but also if someone does a focal fresh install on 2.12, then they'll also get HTTPS URLs.
But also with 2.12 we will enable noble fresh installs so maybe no one should be doing focal fresh installs at that point and we don't need to worry about it?
Or is tying this with the noble migration a bad idea and we should just have a mechanism to update the sources.list file outside of ansible installs regardless?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The case I'm concerned about is "upgrade to v2.12, but not yet Noble, and run testinfra", e.g.:
Time | Admin Workstation tag | Testinfra checks for | Server OS version | Server SecureDrop version | URLs | ? |
---|---|---|---|---|---|---|
0 | 2.11.1 | http:// |
Focal | 2.11.1 | http:// |
✓ |
1 | 2.12.0 | https:// |
Focal | 2.12.0 | http:// |
✗ |
Put another way, I read the current diff as saying: "If you've upgraded to v2.12, but haven't yet upgraded to Noble, then test_automatic_updates.py
will fail." Am I contriving an edge case without consequence?
Or is tying this with the noble migration a bad idea and we should just have a mechanism to update the sources.list file outside of ansible installs regardless?
I think having largely separate installation and upgrade configuration paths is a bad idea, but I know we can't fix that here! :-)
Just a note that I'm not pursuing this for 2.12/noble migration, we'll do it after everyone is on noble. |
Status
Ready for review
Description of Changes
Ubuntu now supports HTTPS on their primary mirrors, including archive.ubuntu.com and security.ubuntu.com.
While APT verifies integrity using PGP signatures, there have been a few vulnerabilities in APT that would've been prevented by also layering TLS on top.
No attempt is made to update the configuration on existing instances; instead this change will be made during the noble migration.
Fixes #3286.
Testing
How should the reviewer test this PR?
Deployment
Any special considerations for deployment? Consider both:
Checklist