gpg --list-config should be able to run when $HOME is not writeable (or does not exist)
Daniel Kahn Gillmor
dkg at fifthhorseman.net
Thu Sep 1 21:38:13 CEST 2016
Hi Werner--
On Thu 2016-09-01 13:25:54 -0400, Werner Koch wrote:
> On Thu, 1 Sep 2016 00:19, dkg at fifthhorseman.net said:
>
>> some gnupg commands (like --list-config) seem to want to do a lot more
>> than they need to with the filesystem. They report errors when the
>> gnupg homedir is not writeable, and they fail outright when $HOME is not
>> writeable (or does not exist). but "gpg --version" works fine in those
>
>
> I just pushed a fix for master.
>
> --list-config
> --list-gcrypt-config
> --gpgconf-list
> --gpgconf-test
>
> won't anymore register a default keyring and thus create ~/.gnupg.
Thanks for this fix! If i upload another version of 2.1.15 into debian
i'll use it instead of the patch which shuffles the test suite
initialization.
Regards,
--dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 930 bytes
Desc: not available
URL: </pipermail/attachments/20160901/8d393601/attachment.sig>
More information about the Gnupg-devel
mailing list