Hi all, I would like to drag your attention to this yet undiscussed posting:
http://www.mail-archive.com/syslog-sec%40employees.org/msg01338.html It is regarding the syslog TAG. The format described was discussed in the context of syslog-sign-13 but now also applies to syslog-international-00. There is an unresolved compatibility issue regarding the use of COLON in the tag. This is a quick excerpt of the issue: #### So I think we need to make a tradeoff decision: we can either a) allow colons in the path name xor ;) b) allow TAG NOT to be terminated by SP Selecting a) will break compliance for older clients (how many?) b) will open up a can of (security?) bugs as I guess there are well enough implementors out there not caring about the restricted char #### I would appreciate any feedback to this topic. Many thanks, Rainer
