Locking broken in gnupg 1.4.2 ?
list at jth.net
Sun Oct 16 13:16:26 CEST 2005
I frequently get missing signatures and I have traced it down to the fact that
several instances of the program is running simultaneously:
secmem usage: 2464/2464 bytes in 7/7 blocks of pool 2464/32768
gpg: fatal: can't read `/home/jth/.gnupg/random_seed': No such file or directory
Shouldn't there be some locking mechanism to take care of this?
I use calls like this:
/usr/bin/gpg --lock-once --default-key yyyyyyyy --pgp8 --batch --passphrase-fd 0
--clearsign "inputfile" <xxxx
- Jørgen Thomsen
More information about the Gnupg-devel