On Sun, Sep 11, 2016 at 03:50:24PM +0900, Hideki Yamane wrote:
> gpg1 and 2 output different secret key information,
This is because the command being used isn't intended for mechanical
consumption. Also, gpg2 defaults to using the fingerprint while gpg1
defaults to the short keyid format.
I didn't actually see a difference at first, since my config sets
"keyid-format 0xlong".
> and now Debian moves to
> gpg2 for default. It's neccesary to update it to deal with it.
>
> $ gpg1 -K
> /home/henrich/.gnupg/secring.gpg
> --------------------------------
> sec 1024D/C4C7264B 2004-06-11
> (snip)
$ gpg1 --fixed-list-mode --with-colons --fingerprint -K
sec::1024:17:0DBDD4A661326D40:1062547112::::::::::
fpr:::::::::FB46A48FF8D28AEA1F9A9F490DBDD4A661326D40:
uid:::::::717664CEC688080636F458E758F5A06EDA93AB7F::James Vega
<vega.ja...@gmail.com>:
(snip)
> $ gpg2 -K
> /home/henrich/.gnupg/pubring.gpg
> --------------------------------
> sec dsa1024 2004-06-11 [SC]
> 455582ED38B6C870E099388C22ED21CBC4C7264B
> (snip)
$ gpg2 --fixed-list-mode --with-colons --fingerprint -K
gpg: keyserver option 'ca-cert-file' is obsolete; please use 'hkp-cacert' in
dirmngr.conf
sec:u:1024:17:0DBDD4A661326D40:1062547112:::u:::scESC:::+::::
fpr:::::::::FB46A48FF8D28AEA1F9A9F490DBDD4A661326D40:
grp:::::::::42B2B7327D641BC37122AA5851CE18EF4C321BD9:
uid:u::::1270517060::373C7996ED7C46EBA0CD6A7E22F52E0CC21C9C01::James Vega
<james...@debian.org>:::::::::
(snip)
The fingerprint can be selected with "| awk -F: '/^fpr/{print $10}'" or
the long id with "| awk -F: '/^sec/{print $5}'".
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
