Re: [PATCH] gpg-agent storage - add support for /run based sockets V2

2017-05-03 Thread James McCoy
On Wed, May 03, 2017 at 11:03:42PM +0200, Lukas Jirkovsky wrote: > On 3 May 2017 at 22:35, Stefan Sperling wrote: > > On Wed, May 03, 2017 at 10:05:01PM +0200, Lukas Jirkovsky wrote: > >> New version. Instead of reimplementing the gpg-agent logic, "gpgconf > >> --list-dir

Re: [PATCH] gpg-agent storage - add support for /run based sockets V2

2017-05-03 Thread Lukas Jirkovsky
On 3 May 2017 at 22:35, Stefan Sperling wrote: > On Wed, May 03, 2017 at 10:05:01PM +0200, Lukas Jirkovsky wrote: >> New version. Instead of reimplementing the gpg-agent logic, "gpgconf >> --list-dir agent-socket" is used. If the gpgconf fails, the code falls >> back to the

Re: [PATCH] gpg-agent storage - add support for /run based sockets V2

2017-05-03 Thread Stefan Sperling
On Wed, May 03, 2017 at 10:05:01PM +0200, Lukas Jirkovsky wrote: > New version. Instead of reimplementing the gpg-agent logic, "gpgconf > --list-dir agent-socket" is used. If the gpgconf fails, the code falls > back to the original solution to stay compatible with old Gnupg > versions. Thanks

[PATCH] gpg-agent storage - add support for /run based sockets V2

2017-05-03 Thread Lukas Jirkovsky
New version. Instead of reimplementing the gpg-agent logic, "gpgconf --list-dir agent-socket" is used. If the gpgconf fails, the code falls back to the original solution to stay compatible with old Gnupg versions. [[[ Find gpg-agent socket using gpgconf if possible. This allows detection of

Re: wildcard authz docs question

2017-05-03 Thread Doug Robinson
Daniel: On Mon, May 1, 2017 at 2:05 PM, Daniel Shahaf wrote: > Doug Robinson wrote on Mon, May 01, 2017 at 14:20:16 +: > > On Mon, Apr 17, 2017 at 21:13 Daniel Shahaf > wrote: > > > Stefan Fuhrmann wrote on Mon, Apr 17, 2017 at 22:22:33

Umlauts on OS X

2017-05-03 Thread Thomas Singer
Hi all, There is the well-known umlaut bug on OS X in SVN since 2005 Are there any plans to finally solve this topic somehow in the near future (e.g. for 1.10) or are there too much concerns regarding upgrading existing repositories and