Page MenuHome GnuPG

2.1.* and no-use-standard-socket no more supported on Windows ??
Closed, ResolvedPublic

Description

Hello

I was using 2.0.25 with no-use-standard-socket set to gpg-agent.conf this was working fine and faster than sockets
under Windows

Trying the same setup on 2.1.0-beta751 with no-use-standard-socket set to gpg-agent.conf this time it works for signing
emails, but when I go to the Key Management page an error occurs in Enigmail

"Error - encryption command failed
X:\apps\gnupg-git\bin\gpg2.exe --charset utf-8 --display-charset utf-8 --emit-version --emit-version --emit-version --
emit-version --batch --no-tty --status-fd 2 --with-fingerprint --fixed-list-mode --with-colons --list-secret-keys
gpg: error running 'X:\apps\gnupg-git\bin\gpg-agent.exe': exit status 1
gpg-agent[7976]: Assuan processing failed: Broken pipe"

If I try use-standard-socket it works but is very slow and I don't like the idea of leaving a running deamon, there is
always the problem of dead fantomù deamon with this method, nor the socket number in the file is out of sync

I have attempted to compile 2.1.0-beta751 with --disable-standard-socket, nothing, it is still forced

How can I use 2.1.0-beta751 like I did with 2.0.25 with no-use-standard-socket ?

Details

Version
2.1.0-beta751

Event Timeline

class101 set Version to 2.1.0-beta751.
class101 removed a project: Feature Request.
class101 added a project: Bug Report.
class101 added a subscriber: class101.

Or let me know if it is no more possible then I will stick with 2.0.* versions

class101 renamed this task from 2.1.* and no-use-standard-socket no more working on Windows ?? to 2.1.* and no-use-standard-socket no more supported on Windows ??.Jul 10 2014, 2:33 PM

GnuPG-2x always uses Unix domain sockets or its emulation under Windows. There
is no way around it.