concurrent key edit ops
Werner Koch
wk at gnupg.org
Wed Apr 16 11:25:02 CEST 2003
On 15 Apr 2003 19:07:55 -0500, Jacob Perkins said:
> Am I correct in assuming that gpg should have no problem doing multiple
> key generation or import operations in different processes?
It should all be properly protected by lock files. If you use the
--lock-once option you may encounter deadlocks. If you use the
--lock-never option, you will encounter data corruption ;-)
> What about multiple key editing operations on the same key?
The last save command wins.
> Would the answers be different if it were multiple gpgme contexts
> instead of gpg processes?
No.
--
Nonviolence is the greatest force at the disposal of
mankind. It is mightier than the mightiest weapon of
destruction devised by the ingenuity of man. -Gandhi
More information about the Gnupg-devel
mailing list