Hey there Spencer! Thanks for the bug report, and sorry for not replying
earlier. I looked into this and did not (yet) find a concrete answer as
to why we don't consider the `trusted=yes` field.
I am hesitant to migrate these sources since the `trusted=yes` option
should ever only be used in a local or testing context -- not on an
ordinary system. We don't support third-party sources either (only
*allow*), and permitting *unsigned* third-party sources during the
upgrade feels even more sketchy.
Right now I don't see any clear use cases beyond the test context, and
I'd suggest the integration tests be changed to use signed repositories
instead. Consider the case where a third-party source gets compromised;
the attacker wouldn't even need to sign their changes. Of course the
system is still at risk *before* the upgrade, but we shouldn't encourage
it.
All the best,
Simon
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2169768
Title:
Third-party sources in non-deb822 format lose trusted=yes on
Noble->Resolute
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2169768/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
