On Tue, Dec 02, 2014 at 04:21:33PM -0500, Jeff King wrote:
> I'm not sure if the most expedient path is trying to convince gpg
> developers that it's a bug, or if there is some workaround (like
> "--passphrase-file /dev/null" or something).
>
> I've been using the patch below to test, and am temp
On Tue, Dec 02, 2014 at 01:55:31PM +0100, Michael J Gruber wrote:
> That private-keys directory is from the first run of gpg2.1 on a pre-2.1
> GPGHOME. It converts the old secring db to that new dir of entries and
> uses that instead.
Thanks for untangling this. As I mentioned elsewhere in the th
Jeff King schrieb am 28.11.2014 um 17:50:
> [updated subject, as this is not specific to the v2.2.0 release at all]
>
> On Fri, Nov 28, 2014 at 10:48:51AM +0100, Michael J Gruber wrote:
>
>> Are you running gnome_keyring_deamon by any chance? It think it runs by
>> default in Gnome, claims to off
[updated subject, as this is not specific to the v2.2.0 release at all]
On Fri, Nov 28, 2014 at 10:48:51AM +0100, Michael J Gruber wrote:
> Are you running gnome_keyring_deamon by any chance? It think it runs by
> default in Gnome, claims to offer gpg_agent functionality but does not
> seem to do
4 matches
Mail list logo