On Sun, 8 Jan 2017 18:47, ijack...@chiark.greenend.org.uk said: > follow, but I am still stumped as to get debugging output from > gpg-agent. I tried making a stunt shell script to pass --debug-all
The best way to debug the system is to --8<---------------cut here---------------start------------->8--- log-file socket:// verbose debug ipc --8<---------------cut here---------------end--------------->8--- into the respective configure files. For gpg-agent.conf you way also add "debug-pinentry". Which debug flags you nee depends on what you want to debug. ipc is a good start the other debug flags are listed in the man pages or use $ gpg-agent --debug help gpg-agent[7724]: reading options from '/home/wk/.gnupg/gpg-agent.conf' gpg-agent[7724]: available debug flags: gpg-agent[7724]: 2 mpi gpg-agent[7724]: 4 crypto gpg-agent[7724]: 32 memory gpg-agent[7724]: 64 cache gpg-agent[7724]: 128 memstat gpg-agent[7724]: 512 hashing gpg-agent[7724]: 1024 ipc gpg-agent[7724]: gpg-agent running and available to get a list of supported debug flags. They slightly differ between tools and you most likely don't want "hashing" becuase that creates a file per hash context. The best way to view or collect the debug output is to start watchgnupg --force --time-only $(gpgconf --list-dirs socketdir)/S.log in another xterm See also the watchnug man page. The use of gpgconf to figure out the log socket and the abbreviated "socket://" log-file is currently missing From that man page. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
pgpqNCxqNkQIl.pgp
Description: PGP signature