Your message dated Wed, 17 Aug 2016 07:31:07 +0200 with message-id <20160817053107.zpsqgfjljkhxbmv4@crossbow> and subject line Re: Bug#834565: apt-key: no keyid listed has caused the Debian Bug report #834565, regarding apt-key: no keyid listed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 834565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834565 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: apt-key: no keyid listed
- From: Zhang Jingqiang <zh_jq@outlook.com>
- Date: Wed, 17 Aug 2016 12:35:36 +0800
- Message-id: <[🔎] 147140853672.8854.5656839835321426998.reportbug@DWORK>
Package: apt Version: 1.3~rc1 Severity: normal Hello, With the morden gpg, `apt-key list` wont't list keyid. Replace the --fingerprint param with --list-sigs may be a temp solution. Thanks -- Package-specific info: -- (no /etc/apt/preferences present) -- -- (no /etc/apt/preferences.d/* present) -- -- (/etc/apt/sources.list present, but not submitted) -- -- (/etc/apt/sources.list.d/vivaldi.list present, but not submitted) -- -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'work'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apt depends on: ii adduser 3.115 ii debian-archive-keyring 2014.3 ii gpgv 2.1.14-5 ii init-system-helpers 1.42 ii libapt-pkg5.0 1.3~rc1 ii libc6 2.23-4 ii libgcc1 1:6.1.1-12 ii libstdc++6 6.1.1-12 Versions of packages apt recommends: ii gnupg 2.1.14-5 ii gnupg2 2.1.14-5 Versions of packages apt suggests: pn apt-doc <none> ii aptitude 0.8.3-1 ii dpkg-dev 1.18.10 pn powermgmt-base <none> ii python-apt 1.1.0~beta4 -- no debconf information
--- End Message ---
--- Begin Message ---
- To: Zhang Jingqiang <zh_jq@outlook.com>, 834565-done@bugs.debian.org
- Subject: Re: Bug#834565: apt-key: no keyid listed
- From: David Kalnischkies <david@kalnischkies.de>
- Date: Wed, 17 Aug 2016 07:31:07 +0200
- Message-id: <20160817053107.zpsqgfjljkhxbmv4@crossbow>
- In-reply-to: <[🔎] 147140853672.8854.5656839835321426998.reportbug@DWORK>
- References: <[🔎] 147140853672.8854.5656839835321426998.reportbug@DWORK>
Hi, On Wed, Aug 17, 2016 at 12:35:36PM +0800, Zhang Jingqiang wrote: > With the morden gpg, `apt-key list` wont't list keyid. > Replace the --fingerprint param with --list-sigs may be a temp solution. That is correct, but what is the problem? Short or even long keyids aren't considered strong enough to refer to a key anymore as collisions can be created easily see e.g. evil32.com. As such gpg does only print the fingerprint – which as a bonus contains short as well as long keyids… (= the end of fingerprint). If there is a valid reason you really really really really really really have to: "apt-key finger --keyid-format=long Debian" works for the time being (see gpg manpage about this option), but you should really get used to fingerprints. So, as I fail to see the bug here as this is intended behavior from gpg I am closing as not-a-bug. Best regards David KalnischkiesAttachment: signature.asc
Description: PGP signature
--- End Message ---