summaryrefslogtreecommitdiff
path: root/test/integration/test-pin-non-existent-package
diff options
context:
space:
mode:
authorDavid Kalnischkies <david@kalnischkies.de>2017-08-01 15:22:09 +0200
committerDavid Kalnischkies <david@kalnischkies.de>2017-10-05 17:30:25 +0200
commit012932793ba0ea9398a9acd80593bed8e77cfbfc (patch)
treedadc8fac126a1e23a5e81b9a4a0d2bbce0a17922 /test/integration/test-pin-non-existent-package
parent19e525aac9a802f452100884fa142c5dc68b2db6 (diff)
ignore unsupported key formats in apt-key
gpg2 generates keyboxes by default and users end up putting either those or armored files into the trusted.gpg.d directory which apt tools neither expect nor can really work with without fortifying backward compatibility (at least under the ".gpg" extension). A (short) discussion about how to deal with keyboxes happened in https://lists.debian.org/deity/2017/07/msg00083.html As the last message in that thread is this changeset lets go ahead with it and see how it turns out. The idea is here simply that we check the first octal of a gpg file to have one of three accepted values. Testing on my machines has always produced just one of these, but running into those values on invalid files is reasonabily unlikely to not worry too much. Closes: #876508
Diffstat (limited to 'test/integration/test-pin-non-existent-package')
0 files changed, 0 insertions, 0 deletions