Random_seed File Locking on NFS File System Across Networks/Domains Hangs
csalemi at hotmail.com
Mon Apr 26 03:12:14 CEST 2021
The 100+ servers only read the key. Each user ID has a sub-directory under a generic location so there are no warnings printed by gpg when using the key to decrypt files. Any operation that encrypts files imports the global key locally or uses User IDs that have the same key locally and uses it for the encrypting.
Again, the concern using the global keystore on the NAS is that it doesn’t cause issues if multiple servers are decrypting different files at the same time using the same key without using the random_seed file. Using the —no-random-seed-file would eliminate the file locking issue, I believe.
From: Gnupg-users <gnupg-users-bounces at gnupg.org> on behalf of Ángel <angel at pgp.16bits.net>
Sent: Sunday, April 25, 2021 7:51 PM
To: gnupg-users at gnupg.org
Subject: Re: Random_seed File Locking on NFS File System Across Networks/Domains Hangs
On 2021-04-25 at 13:11 +0000, Charlie Salemi via Gnupg-users wrote:
> Would ignoring the file locking on the random_seed file with the --
> no-random-seed-file option cause issues with independent processes
> accessing the same keystore at the same time on different servers?
> If so, what are those issues, and can they be avoided/worked around?
No. Not using the random seed files means just, not using that file. It
isn't used for synchronization.
Although, you could face the same issue when they try to lock other
files. How are you handling the changes to that keystore? Are those 100
servers only reading the keys, or are they also *modifying* it (e.g.
importing new keys) ?
Gnupg-users mailing list
Gnupg-users at gnupg.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gnupg-users