summaryrefslogtreecommitdiff
path: root/test/integration/apt.pem
diff options
context:
space:
mode:
authorDavid Kalnischkies <david@kalnischkies.de>2014-10-13 08:12:06 +0200
committerMichael Vogt <mvo@ubuntu.com>2014-10-13 11:29:46 +0200
commit07cb47e71f4de7e3c57f9dcfbfb82e4e5566aed6 (patch)
tree2a37a6e25fb33737919a222e8cd47257600f45b5 /test/integration/apt.pem
parent862bafea48af2ceaf96345db237b461307a021f6 (diff)
trusted=yes sources are secure, we just don't know why
Do not require a special flag to be present to update trusted=yes sources as this flag in the sources.list is obviously special enough. Note that this is just disabling the error message, the user will still be warned about all the (possible) failures the repository generated, it is just triggering the acceptance of the warnings on a source-by-source level. Similarily, the trusted=no flag doesn't require the user to pass additional flags to update, if the repository looks fine in the view of apt it will update just fine. The unauthenticated warnings will "just" be presented then the data is used. In case you wonder: Both was the behavior in previous versions, too.
Diffstat (limited to 'test/integration/apt.pem')
0 files changed, 0 insertions, 0 deletions