summaryrefslogtreecommitdiff
path: root/cmdline
diff options
context:
space:
mode:
authorDavid Kalnischkies <david@kalnischkies.de>2014-04-14 18:24:17 +0200
committerDavid Kalnischkies <david@kalnischkies.de>2014-09-27 00:12:14 +0200
commitc46a36adaf51fc28464ea1a0e826c754ee60672b (patch)
treebfe38bcb00f7d39febd1e3427b4b75d58f1727e3 /cmdline
parent0b94a7bc2ebb42453d9e22dc58dde76b9261de50 (diff)
add and use 'apt-key verify' which prefers gpgv over gpg
gnupg/gnupg2 can do verify just fine of course, so we don't need to use gpgv here, but it is what we always used in the past, so there might be scripts expecting a certain output and more importantly the output of apt-cdrom contains messages from gpg and even with all the settings we activate to prevent it, it still shows (in some versions) a quiet scary: "gpg: WARNING: Using untrusted key!" message. Keeping the use of gpgv is the simplest way to prevent it. We are increasing also the "Breaks: apt" version from libapt as it requires a newer apt-key than might be installed in partial upgrades.
Diffstat (limited to 'cmdline')
-rw-r--r--cmdline/apt-key.in8
1 files changed, 8 insertions, 0 deletions
diff --git a/cmdline/apt-key.in b/cmdline/apt-key.in
index a9a729cce..83a7a31b9 100644
--- a/cmdline/apt-key.in
+++ b/cmdline/apt-key.in
@@ -450,6 +450,14 @@ case "$command" in
$GPG "$@"
merge_back_changes
;;
+ verify)
+ setup_merged_keyring
+ if which gpgv >/dev/null 2>&1; then
+ gpgv --homedir "${GPGHOMEDIR}" --keyring "${GPGHOMEDIR}/pubring.gpg" --ignore-time-conflict "$@"
+ else
+ $GPG --verify "$@"
+ fi
+ ;;
help)
usage
;;