On Thu, 2005-11-24 at 10:24 +0100, Rainer Gerhards wrote: > > On Thu, 2005-11-24 at 09:36 +0100, Rainer Gerhards wrote: > > > Anton: > For simplicity, let me strip the rest and just look at that part > > \u0000 > > I think the sender of the sample message should not encode it as > > NUL (0x00) > > but instead as > > 0x5c-0x75-0x30-0x30-0x30-0x30 (\-u-0-0-0-0) > > Encoding it as NUL in an otherwise human-readable message makes no sense > to me. > > I am questioning if there is any legitimate case where an actual NUL > needs to be part of MSG. >
Now I understand, and we perfectly agree. I don't see a reason to include 0x00 octet. In fact syslog-ng filters everything below 32, to avoid nasty tricks with escape sequences in the log files viewed. Though this could be opened up a bit if needed. -- Bazsi _______________________________________________ Syslog mailing list Syslog@lists.ietf.org https://www1.ietf.org/mailman/listinfo/syslog
