Logging to a socket

Werner Koch wk at gnupg.org
Tue Dec 16 13:09:45 CET 2003


It is a bit difficult to follow the actual action of Aegypten's crypto
modules because all modules write to their own log file.  For folks
loving GUIs, this is not the optimal approach.  To attack this problem
I added a feature to gpgsm, gpg-agent, scdaemon and dirmngr to allow
logging to a socket:

The name given to the option --log-file may now be of the format:


which will write all log output to the socket "/home/foo/gnupglog.S".
If the socket does not exists or the server bound to that socket dies,
logging will continue to stderr as long as the server is not

Note that this feature does only work on *BSD and GNU systems.  Bug
reports as usual to this list please.

A example program to listen on the socket is available in the gnupg
CVS as tools/watchgnupg.c.  We now need a GUI program (either
cannibalizing watchgnupg.org or using it in a pipe) to display and
color the log files.


Werner Koch                                      <wk at gnupg.org>
The GnuPG Experts                                http://g10code.com
Free Software Foundation Europe                  http://fsfeurope.org

More information about the Gpa-dev mailing list