Hi,
thanks very much for your help, it works now.
> It is not possible for OpenPGP card to have user's PIN with length of
> less than 6. Your user's PIN would be the factory default still.
You were right, my PIN had a length of 5 and was still set to factory default.
After changing it all proble
On 02/09/2015 02:41 AM, Rainer Keller wrote:
> In .gnupg/sshcontrol I have added the correct keygrip and "ssh-add -l" shows
> the right key:
>
>> 4096 XX:XX:XX cardno: (RSA)
Well, you don't need to add this manually, for your smartcard.
>> gpg-agent smartcard signing failed: Bad PIN
>
> It
> Gpg-agent uses the smartcard key which is identified by the $AUTHKEYID
> attribute:
>
> $ gpg-connect-agent 'scd getattr $AUTHKEYID' /bye
> S $AUTHKEYID OPENPGP.3
> OK
I get the same output for my card.
> Thus only the keys listed in ~/.gnupg/sshcontrol will be used.
The keygrip from the
On Mon, 16 Feb 2015 20:40, m...@rainerkeller.de said:
> For me it looks like the authentication private key uses the encryption pin
> (Auth ID 0x02) while it should use the signature pin.
> It tried to set the encryption pin via "pkcs15-tool --auth-id 02
[ You should not use this tool for the Op
> According to the error message gpg-agent is unable to sign using the card:
> > ssh user@server
> > Agent admitted failure to sign using the key.
> > Permission denied (publickey,keyboard-interactive).
I had a look on the card with pksc15-tool (removed irrelevant parts):
PKCS#15 Card [OpenPGP C
Hello,
I am trying to use gnupg smart card for ssh connections.
According to the error message gpg-agent is unable to sign using the card:
> ssh user@server
> Agent admitted failure to sign using the key.
> Permission denied (publickey,keyboard-interactive).
In .gnupg/sshcontrol I have added th
