When entering
tcp://1.2.3.4:10001
as value for a log-file in Kleopatra's config dialog, it ends up as
tcp:\\1.2.3.4:10001
in , say, gpg-agent.conf. The result is that tcp logging (watchgnupg --tcp 10001) does not work.
Description
Description
Revisions and Commits
Revisions and Commits
| rM GPGME | |||
| rMd04d7b174fb7 qt: Write path values with Unix directory separators | |||
Event Timeline
Comment Actions
I guess you are the only person who does it. But yeah. I agree that it should be fixed.
Comment Actions
Looks like Kleopatra is writing the filename with the system's preferred directory separator. If GnuPG on Windows works if filenames are written with Unix directory separators, e.g. c:/foo/bla or //server/foo/bla, to the config files, then we can certainly change this in Kleopatra.
Comment Actions
Windows accepts forward slashes in all API calls. Users are sometimes confused by this but this is a documented feature for ages in the API.
Comment Actions
Fixed.
Not so fun fact: If you enter tcp://1.2.3.4:10001 (literally) as value for gpg-agent's log file, then on save gpgconf calls
gpg-connect-agent --homedir /home/ingo/dev/g10/.gnupghomes/utf16 --no-autostart RELOADAGENT
which hangs (probably trying to connect to the not existing IP address or to the blocked port). This also makes Kleopatra hang.
Don't blame Kleopatra for this!