outdated keyring on write lock

Werner Koch wk at gnupg.org
Fri Sep 23 10:04:29 CEST 2005

On Thu, 22 Sep 2005 21:48:01 +0200, Michael Holschbach said:

> 3. close first program with "save"
> new keyring files are written to disk, including the new signature
> 4. close second program with "save"
> new keyring files are written to disk, but the first signature is lost

This is the standard strategy, last save wins.  It is the same as with
all text editors (although some may warn about trying to save a
meanwhile changed file).

> So, is there a "read lock" available in gpg? Or a way to reload the keyring 
> after the write lock is acquired?

No.  It does not make much sense out of two resons:

* A stale process might hold the read lock and it would be cumbersome
  for the user to walk/login to that machine and close the edit there.

* In almost all cases there is something wrong if you are editing two
  keys or even the same key at the same time.  gpg is not a database
  application and thus provides no means of locking.  Well, there is
  some locking but it is only required to maintain the integrity of
  the keyrings.



More information about the Gnupg-devel mailing list