Package: signing-party Version: 1.1.11-1 Severity: normal Hi folks,
When fetching some keys (presumably those with expired subkeys), I get errors from caff. Here's the command and output to reproduce: matthijs@grubby:~$ caff e1c21845 [INFO] Fetching keys from pgp.mit.edu, this may take a while... [NOTICE] Got unknown reply from gpg: [GNUPG:] KEYEXPIRED 1232899269 [NOTICE] Got unknown reply from gpg: [GNUPG:] SIGEXPIRED deprecated-use-keyexpired-instead [NOTICE] Got unknown reply from gpg: [GNUPG:] KEYEXPIRED 1276022045 [NOTICE] Got unknown reply from gpg: [GNUPG:] SIGEXPIRED deprecated-use-keyexpired-instead [NOTICE] Got unknown reply from gpg: [GNUPG:] KEYEXPIRED 1276606926 [NOTICE] Got unknown reply from gpg: [GNUPG:] SIGEXPIRED deprecated-use-keyexpired-instead [NOTICE] Got unknown reply from gpg: [GNUPG:] KEYEXPIRED 1339692236 [NOTICE] Got unknown reply from gpg: [GNUPG:] SIGEXPIRED deprecated-use-keyexpired-instead [INFO] Sign the following keys according to your policy, then exit gpg with 'save' after signing each key gpg --homedir=/home/matthijs/.caff/gnupghome --secret-keyring /home/matthijs/.gnupg/secring.gpg --no-auto-check-trustdb --trust-model=always --edit-key E0D3FAAA6F50A5DA9D5B293833961588E1C21845 showphoto sign gpg (GnuPG) 1.4.18; Copyright (C) 2014 Free Software Foundation, Inc. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. gpg: moving a key signature to the correct place [ This line repeats a lot of times ] pub 4096R/E1C21845 created: 2007-01-25 expires: 2024-06-27 usage: SC sub 2048R/DCBA43DF created: 2007-01-25 expired: 2009-01-25 usage: S sub 2048R/7AB399FF created: 2007-01-25 expired: 2009-01-25 usage: E This key was revoked on 2008-06-16 by RSA key E1C21845 Thijs Kinkhorst <[email protected]> sub 2048R/EC5DCE28 created: 2008-06-08 revoked: 2008-06-16 usage: S This key was revoked on 2008-06-16 by RSA key E1C21845 Thijs Kinkhorst <[email protected]> sub 2048R/88CC9563 created: 2008-06-08 revoked: 2008-06-16 usage: E sub 2048R/8C55A01C created: 2008-06-15 expired: 2010-06-15 usage: S sub 2048R/435434E1 created: 2008-06-15 expired: 2010-06-15 usage: E sub 2048R/B6897E7B created: 2010-06-15 expired: 2012-06-14 usage: S sub 2048R/3861CF70 created: 2010-06-15 expired: 2012-06-14 usage: E sub 2048R/401DAC04 created: 2012-06-16 expires: 2015-06-30 usage: S sub 2048R/1001EBD3 created: 2012-06-16 expires: 2015-06-30 usage: E [ unknown] (1). Thijs Kinkhorst <[email protected]> [ revoked] (2) Thijs Kinkhorst <[email protected]> [ unknown] (3) Thijs Kinkhorst <[email protected]> [ unknown] (4) Thijs Kinkhorst <[email protected]> [ unknown] (5) Thijs Kinkhorst <[email protected]> It seems that the key is properly imported regardless of these notices, but I guess it would be good to handle them properly anyway? Gr. Matthijs -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.0-rc3+ (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages signing-party depends on: ii gnupg 1.4.18-4 ii libc6 2.19-11 ii libclass-methodmaker-perl 2.21-1+b1 ii libgnupg-interface-perl 0.50-3 ii libmailtools-perl 2.13-1 ii libmime-tools-perl 5.505-1 ii libnet-idn-encode-perl 2.201-1 ii libterm-readkey-perl 2.32-1+b1 ii libtext-template-perl 1.46-1 ii perl 5.20.1-1 pn python:any <none> ii qprint 1.0.dfsg.2-2 Versions of packages signing-party recommends: ii dialog 1.2-20140219-1 ii exim4-daemon-light [mail-transport-agent] 4.84-2 ii libgd-perl [libgd-gd2-perl] 2.53-1+b1 ii libpaper-utils 1.1.24+nmu3 ii whiptail 0.52.17-1 Versions of packages signing-party suggests: ii fonts-droid 1:4.4.3r1.1-1 ii imagemagick 8:6.8.9.6-4 ii mutt 1.5.23-1.1 pn qrencode <none> ii texlive-font-utils 2014.20140821-1 ii texlive-latex-recommended 2014.20140821-1 pn texlive-xetex <none> pn wipe <none> -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
