Subject: bug#22726: Git HEAD can't read key from the GPG card

From: Manoj Srivastava <[email-masked]>
Date: Thu, 18 Feb 2016 12:17:29 -0800

> Could you follow the reporting steps described in:
> http://www.gnu.org/software/emacs/manual/html_node/epa/Bug-Reports.html#Bug-Reports
> which I mentioned it in your last bug report:
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22405#15

        The report was already generated by M-x report-emacs-bug.

--8<---------------cut here---------------start------------->8---
_> gpg --version
gpg (GnuPG) 1.4.20
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/srivasta/lib/.sec
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
--8<---------------cut here---------------end--------------->8---

--8<---------------cut here---------------start------------->8---
gpg (GnuPG) 2.1.11
libgcrypt 1.6.5
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/srivasta/lib/.sec
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
--8<---------------cut here---------------end--------------->8---

--8<---------------cut here---------------start------------->8---
# Uncomment the next line to get rid of the copyright notice
no-greeting
# I use a gnupg agent to avoid having to type in my phrase all the
# time. The phrase expires in 5 minutes
use-agent

# If you have more than 1 secret key in your keyring, you may want
# to uncomment the following option and set your preffered keyid
# default-key 621CC013

# If you do not pass a recipient to gpg, it will ask for one.
# Using this option you can encrypt to a default key.  key validation
# will not be done in this case.
# The second form uses the default key as default recipient.

#default-recipient some-user-id
#default-recipient-self
hidden-encrypt-to 0xC5779A1C
#default-recipient 0x7DBB2DF3!

# lock the file only once for the lifetime of a process.
# if you do not define this, the lock will be obtained and released
# every time it is needed - normally this is not needed.
# we only need to do this once while the gpg process is using the ring
lock-once

## Other fun options

# Because some mailers change lines starting with "From " to ">From "
# it is good to handle such lines in a special way when creating
# cleartext signatures; all other PGP versions it this way too.
# To enable full OpenPGP compliance you have to remove this option.
escape-from-lines

# If you do not use the Latin-1 (ISO-8859-1) charset, you should
# tell GnuPG which is the native character set.  Please check
# the man page for supported character sets.
#charset koi8-r
charset utf-8

## The debian project keyrings
#keyring debian-keyring.gpg
##keyring debian-keyring.pgp
##keyring /usr/share/keyrings/debian-keyring.pgp
##keyring /usr/share/keyrings/debian-keyring.gpg

## The new, gpg keyrings
secret-keyring secring.gpg
keyring        pubring.gpg
## gpg adds keys to this keyring, by default.
primary-keyring pubring.gpg

# GnuPG can import a key from a HKP keyerver if one is missing
# for sercain operations. Is you set this option to a keyserver
# you will be asked in such a case whether GnuPG should try to
# import the key from that server (server do syncronize with each
# others and DNS Round-Robin may give you a random server each time).
# Use "host -l pgp.net | grep www" to figure out a keyserver.

keyserver-options auto-key-retrieve include-revoked

#keyserver x-hkp://pgp.mit.edu
#keyserver keyring.debian.org
#keyserver x-hkp://subkeys.pgp.net
#keyserver keys.gnupg.net
keyserver pool.sks-keyservers.net

auto-key-locate keyserver

# If this is not set, gpg nags
auto-check-trustdb

# Thigs to show when listing keys and verifying them
list-options show-keyring=Yes,show-sig-expire=Yes,show-unusable-subkeys=Yes,show-unusable-uids=Yes,show-uid-validity=Yes,show-policy-urls=Yes,show-notations=Yes
verify-options show-policy-urls=Yes,show-notations=Yes

# These options select a "safe" set of ciphers and digest algorithms,
# specifically, they try to not use SHA-1, which is now deprecated
personal-cipher-preferences AES256 TWOFISH BLOWFISH
s2k-cipher-algo AES
personal-digest-preferences SHA512 SHA384 SHA256
cert-digest-algo SHA512
default-preference-list SHA512 SHA384 SHA256 AES256
personal-compress-preferences ZLIB BZIP2 ZIP

# Add policies and notations to the signatures I make.
cert-policy-url !http://www.golden-gryphon.com/download/policy.20090821.txt?version=1.0&sha256sum=03b987f1eefa098c350929157e9c6ef5d234970c406e748935e65c0efcceaebb
cert-notation [email-masked]=%k_by_%g
sig-notation [email-masked]=%g_%c

default-cert-level 3
ask-cert-level
--8<---------------cut here---------------end--------------->8---

        Manoj
-- 
A door is what a dog is perpetually on the wrong side of. Ogden Nash
Manoj Srivastava <[email-masked]> <http://www.golden-gryphon.com/>  
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C