gnupg 1.2.4: Keyring locking bug
Adrian 'Dagurashibanipal' von Bidder
avbidder at fortytwo.ch
Sat Mar 6 15:17:43 CET 2004
running gpg --refresh-key in a few instances in parallel gives things like
gpg: keyring_get_keyblock: read error: invalid packet
gpg: keydb_get_keyblock failed: invalid keyring
gpg: [don't know]: invalid packet (ctb=02)
(with various values for ctb=, I observed 02, fe and 2f)
This happens with either the default setting and with lock-once set.
(Connected with this:
- what is the rationale for using STDERR for the normal status messages,
instead of just STDOUT?
- a --refresh-if-older <x> option which would refresh a key before use if the
last refresh is more than <x> days back. (Perhaps force <x> >= n to avoid
hammering the keyservers). I think this one has been talked about before.
Dizer a verdade é como escrever bem
Aprende-se a custa de exercícios.
Existe um remédio para qualquer culpa: Reconhece-la
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 331 bytes
Url : /pipermail/attachments/20040306/e1502486/attachment.bin
More information about the Gnupg-devel