From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.16-22 i586; en-US; rv:0.9)
Description of problem:
The identd daemon supplied in the pidentd package provides a response which
appears to be properly accepted and parsed by most requesters. However, a
non-required space breaks some simplistic parsers (particularly undernet
IRC daemons) interpretation of the reply.
Steps to Reproduce:
1. Query the identd daemon about a valid connection,
e.g. "1204, 2302\n"
2. Observerve response of "1204 , 2302 : USERID : OTHER :xxxxxx\r\n"
3. Note extra space -----------^
Expected Results: A string acceptable to IRC servers including undenet
"1204, 2302 : USERID : OTHER :xxxxxx\r\n"
The format without the space ahead of the comma is returned by the other
identd daemons I have been able to test, including Virc and Mirc
identd responders. Both formats meet the RFC1413 description - however,
the space is NOT given itn the RFC examples, and it is suggested that
extraneous white space be eliminated in replies. It is also easier to read
- i.e. by the rev 1.0 human eyeball, as well as by simplistic parsers.
Fixed in pidentd-3.0.12-9. Thanks for your report.