When running 'gpg --refresh-keys', the second updated key results in: gpg: renaming `/home/max/.gnupg/pubring.gpg' to `/home/max/.gnupg/pubring.gpg~' failed: Permission denied gpg: error writing keyring `/home/max/.gnupg/pubring.gpg': file rename error gpg: key XXXXXXXX: "...." 28 new signatures gpg: error reading `[stream]': file rename error
Given that: * this happens for the *second* updated key * having another process running at the same time, rapidly moving away any new pubring.gpg~ files avoids the error * it is presumably Cygwin-specific it seems extremely likely that gnupg has a file descriptor leak, such that when the second key is processed, gnupg still has an open file descriptor on the file pubring.gpg~ when it attempts to overwrite it by renaming another file onto that name. Windows then objects. Max.
signature.asc
Description: OpenPGP digital signature