> What version was your card? It should work fine on a 2.0 smart card,
> but, it's by design made to brick 1.X cards.
It should be a 2.0 card. At least I bought is as such.
> Also, if it was a 2.0 smart card, what key was it?
What do you mean with "key"?
I had a 4096bit authentication key on the c
On 07/02/15 21:45, Rainer Keller wrote:
> Unfortunatly this seemed to brick the card.
> "gpg: OpenPGP card not available: Not supported"
> Gnupg does not detect the card anymore.
Fortunately, your card is not bricked. But GnuPG can't access it anymore. If you
have a recent enough version of GnuPG,
On 07/02/15 20:43, Hugo Osvaldo Barrera wrote:
> I don't think I'm doing something wrong, but: Am I? Did I miss something?
Yes, you have interpreted it wrong. What you are doing now is this statement:
"I trust Hugo Osvaldo Barrera checks identities carefully before signing keys.
However, I do not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear list,
A Gentoo user has run into an issue[0] with using HKPS from a static
build of GnuPG 2.0.26. I seem to be able to replicate this behavior in
a virtual machine, but my debugging seems to stop around the configure
detection of curl being usa
> This gpg-connect-agent script ought to get your card back on its feet.
Thanks very much.
It worked and my card seems to operate again.
Just out of curiosity is there a way to reset the PIN user counter without
resetting the card?
___
Gnupg-users mai
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
I revoked my gpg key yesterday because it was superceded by a newer one.
Now recepients of my messages during the last few years are getting a warning
that the key is invalid - even though it was perfectly valid the date the
messages were signed:
gpg: Signature made 2015-02-05T19:28:21 ART usin