[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: gpg keys on multiple machines



Willie Wonka wrote:


On the web I found this;

--------------------------------------------------------------------
Bug#302692: gnupg-agent: Don't use (undocumented) max-cache-ttl switch

Package: gnupg-agent
Version: 1.9.15-5
Severity: normal


Hi!

If one wants to set default-cache-ttl to a large value, e.g. one day
the line "default-cache-ttl 86400" in ~/.gnupg/gpg-agent.conf alone
doesn't do the trick, but one also must add "max-cache-ttl 86400". This
later parameter is undocumented and confusing and should be removed,
i.e. one should be able to set large values directly by just
default-cache-ttl.

Thanks!
  Georg

-- System Information:
Debian Release: 3.1
 APT prefers testing
 APT policy: (990, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-gw2
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages gnupg-agent depends on:
ii  libc6                       2.3.2.ds1-20 GNU C Library: Shared
libraries an
ii  libgcrypt11                 1.2.0-4      LGPL Crypto library -
runtime libr
ii  libgpg-error0               1.0-1        library for common error
values an
ii  libpth2                     2.0.1-2      The GNU Portable Threads
ii  zlib1g                      1:1.2.2-3    compression library -
runtime

-- no debconf information

------------------------------------------------------------------------

Don't know what to make of all this - but perhaps *gnupg2* is where the
new(er) stuff is?


It''s utterly confusing, especially Georg's paragraph which seems to tell us to use max-cache-ttl and not to use it at the same time. whithout giving reasons for either.

So what are we to make of it? And who can we ask? It's not as if it's a trivial issue.



Reply to: