On 15/04/14 16:34, Florian Wolters wrote:
> How does GnuPG decide wether to ask for the Pin on screen or to let it
> be entered on the pinpad?
AFAIK, only the internal CCID driver supports entry on the pinpad, and it is by
default enabled when using the internal CCID driver. However, if you have p
Hi @ll,
I got one further question regarding the Chipdrive. This device is one
with a pinpad. But currently the PIN is asked on the monitor and to be
entered with the keyboard rather than the pinpad. Can that be associated
with running just "gpg2 --card-status"?
How does GnuPG decide wether to as
On Sat, Apr 5, 2014 at 3:57 PM, Florian Wolters
wrote:
> But concerning the keys I got another question: How can I tell gnupg to
> use keys that are already stored on the card? I do have my private key
> on the card already and want to use this card on another computer? Do I
> have to import my k
Hi all,
> It works for me. I have an SPR 532 with firmware v5.10, and I'm running Debian
> testing x86_64. I'm using GnuPG's internal CCID driver.
I got this working as well. The problem oviously indeed lies with the
firware version of the smartcard reader. I managed to update the
firwamre to 5.1
On 03/04/14 14:42, Florian Wolters wrote:
> Has anyone this combination up and running and could point me into the
> right direction to get this working?
It works for me. I have an SPR 532 with firmware v5.10, and I'm running Debian
testing x86_64. I'm using GnuPG's internal CCID driver.
I couldn
Hello,
I bought a Chipdrive SPR 532 (aka Pinpad Pro) to read and write my PGP
RSA Keys on the OpenPGP smartcard V2. The reader is connected to a PC
running Ubuntu Linux 13.10. I passed all that gpg-agent vs.
gnome-keyring manager stuff successfully.
The problem is that I cannot authenticate an SS
