Page MenuHome GnuPG
Create Task
Maniphest T1377

gpg-agent ignores default-cache-ttl-ssh
Closed, InvalidPublic
Actions

Description

From http://bugs.debian.org/606759:

gpg-agent seems to ignore default-cache-ttl-ssh:

From .gnupg/gpg-agent.conf:

max-cache-ttl <TTL>
default-cache-ttl-ssh <SSH-TTL>

(<SSH-TTL> > <TTL>)

From debug log:

2010-12-11 11:24:34 gpg-agent[12425] DBG: agent_get_cache `<SSH-ID>'...
2010-12-11 11:24:34 gpg-agent[12425] DBG: ... miss
2010-12-11 11:24:34 gpg-agent[12425] starting a new PIN Entry
2010-12-11 11:24:34 gpg-agent[12425] DBG: connection to PIN entry established
2010-12-11 11:24:39 gpg-agent[12425] DBG: agent_put_cache `<SSH-ID>' requested
ttl=0 mode=4
[...]
2010-12-11 11:37:11 gpg-agent[12425] DBG: agent_get_cache `<SSH-ID>'...
2010-12-11 11:37:11 gpg-agent[12425] DBG: ... hit
[...]
2010-12-11 13:57:24 gpg-agent[12425] DBG: expired `<SSH-ID>' (<TTL>s after
creation)

I removed the actual values for privacy reasons...

Details

External Link
http://bugs.debian.org/606759
Version
2.0.18

Event Timeline

eric_kuroneko.ca added projects: gpgagent, gnupg, Bug Report, Debian.Oct 16 2011, 8:37 AM
eric_kuroneko.ca set Version to 2.0.18.
eric_kuroneko.ca added a subscriber: eric_kuroneko.ca.
• werner set External Link to http://bugs.debian.org/606759.Nov 6 2012, 11:31 PM
• werner added a project: Not A Bug.Nov 7 2012, 3:25 PM
• werner added a subscriber: • werner.

This is not a bug. The description of --max-cache-ttl reads:

  Set the maximum time a cache entry is valid to @var{n} seconds.  After
  this time a cache entry will be expired even if it has been accessed
  recently.  The default is 2 hours (7200 seconds).

Thus even if you set the cache-ttl-ssh > max-cache-ttl, it will expire after
max-cache-ttl seconds.

• werner closed this task as Invalid.Nov 7 2012, 3:26 PM
• werner removed a project: Bug Report.