Andrew: Thanks for that info. I've to admit I've always overlooked this. Eventually, this creates a new situation.
Do you think we should support NUL natively (I mean without escaping it, e.g. in <000> as your syslogd does currently)? Rainer > -----Original Message----- > From: Andrew Ross [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 24, 2005 11:04 PM > To: Rainer Gerhards; [EMAIL PROTECTED] > Subject: Null character > > > Rainer, > > FWIIW, I've seen Netscreen, NetGear and some LinkSys devices > send a Null > character at the end of each message. Not all versions of the > firmware would > include the Null at the end which leads me to believe it may > be a bug in > some releases of the firmware. > > When sending syslog over TCP, Netscreen firewalls will > delimit each message > with LF NULL. > > This probably won't have any impact on the 'CLR' since it is > the very last > character in the message, but I thought I would raise the > issue with you as > a real-life case of a Null character being used. > > Cheers > > Andrew > > > > _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog
