On Fri 2016-10-14 15:11:39 -0400, Werner Koch wrote:
> On Fri, 14 Oct 2016 18:58, d...@fifthhorseman.net said:
>> instructions that say "if you're dealing with gpg secret key material in
>> a test suite, here's what we recommend you do".
>
> Which could be as simple as: Do what GnuPG does in its
On Fri, 14 Oct 2016 19:14, ijack...@chiark.greenend.org.uk said:
> 3. Concurrent access to the private key database by different
> agents is not safe. (gnupg2 design decison; I think gnupg1 uses
> locks)
It is safe. There are no locks for the private key files, last writer
wins.
On Fri, 14 Oct 2016 18:58, d...@fifthhorseman.net said:
> agreed, that's why i'm encouraging upstream to fix their inotify
> detection:
>
>https://bugs.gnupg.org/gnupg/issue2756
I'll look at this next week. I guess the problem is that we watch the
directory for inotify events of the socket
3 matches
Mail list logo
