[Bug 1744318] Re: changelogs.ubuntu.com should be using HTTPS
Sebastien Bacher
seb128 at ubuntu.com
Thu Oct 24 11:30:24 UTC 2019
The change seem to be buggy, at least it created bug #1849004 which
changelog fetchning stopped working in case without proxy in use
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1744318
Title:
changelogs.ubuntu.com should be using HTTPS
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in update-manager package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader source package in Xenial:
Fix Released
Status in update-manager source package in Xenial:
Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
Fix Released
Status in update-manager source package in Bionic:
Fix Released
Bug description:
[Impact]
Although the packages listed in meta-release files on changelogs.ubuntu.com are signature-checked there doesn't appear to be any way to verify the meta-release files are valid so a man-in-the-middle could maliciously supply an alternate meta-release.
meta-release files should be signed with the archive GPG key and/or
delivered over HTTPS.
[Test case]
Block port 80 access to changelogs.ubuntu.com and check that do-release-upgrade still works
[Regression potential]
This breaks any clients behind a proxy where HTTPS (CONNECT on the proxy) is not allowed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1744318/+subscriptions
More information about the foundations-bugs
mailing list