[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gnupg-devel
Subject:    Locking broken in gnupg 1.4.2 ?
From:       Jørgen Thomsen <list () jth ! net>
Date:       2005-10-16 11:16:26
Message-ID: rfd4l1l4b9eji4q9bj79kf6tm9g2qe5egl () 4ax ! com
[Download RAW message or body]

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

_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-devel

[prev in list] [next in list] [prev in thread] [next in thread]