Werner Koch wrote:
On Wed, 16 Dec 2009 16:27:29 +0100, Marco Steinacher wrote:
option (scdaemon) seem to work. I have set all timeouts to very low
values but the PIN is still cached forever (by the card?), as long as
There is no cache for a PIN. A card is usually unlocked after the PIN
Olav Seyfarth wrote:
Hi Marco,
I'm using gnupg with an OpenPGP smartcard since a few days now and
basically it works very well. However, one thing bothers me a bit:
Neither the cache-timeout options (gpg-agent) nor the card-timeout
option (scdaemon) seem to work. I have set all timeouts to
On Thu, 17 Dec 2009 11:27:53 +0100, marco+gn...@websource.ch wrote:
As I wrote in my posting I have tried to use this option but it does not
work. I added 'card-timeout 15' to my scdaemon.conf and nothing happens
15 seconds after accessing the card. The card remains unlocked as long
Actually
Werner Koch wrote:
On Thu, 17 Dec 2009 11:27:53 +0100, marco+gn...@websource.ch wrote:
As I wrote in my posting I have tried to use this option but it does not
work. I added 'card-timeout 15' to my scdaemon.conf and nothing happens
15 seconds after accessing the card. The card remains
Hi,
I'm using gnupg with an OpenPGP smartcard since a few days now and
basically it works very well. However, one thing bothers me a bit:
Neither the cache-timeout options (gpg-agent) nor the card-timeout
option (scdaemon) seem to work. I have set all timeouts to very low
values but the PIN is
On Wed, 16 Dec 2009 16:27:29 +0100, Marco Steinacher wrote:
option (scdaemon) seem to work. I have set all timeouts to very low
values but the PIN is still cached forever (by the card?), as long as
There is no cache for a PIN. A card is usually unlocked after the PIN
as been given until the
