[Bug 100] New: Hostnames that start with 4+ digits mess up the time system
https://bugzilla.balabit.com/show_bug.cgi?id=100 Summary: Hostnames that start with 4+ digits mess up the time system Product: syslog-ng Version: 2.0.x Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: D.Ojalvo@f5.com Type of the Report: --- Estimated Hours: 0.0 Created an attachment (id=26) --> (https://bugzilla.balabit.com/attachment.cgi?id=26) My patch proposal If syslog is handling a message with an rfc 3164-type timestamp then a hostname that begins with 4 digits, the time parser will mess up because it thinks that it is dealing with a linksys-style timestamp that includes the year, when the rfc3164 timestamp does not. I wrote a patch that adds a strict rfc3164 parsing option to the syslog startup. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
Well to be fair, hostnames that start with a number are a violation of RFC 952. http://www.ietf.org/rfc/rfc952.txt "The first character must be an alpha character" -Patrick Sent: Tue Dec 07 2010 16:49:03 GMT-0700 (Mountain Standard Time) From: bugzilla@bugzilla.balabit.com To: syslog-ng@lists.balabit.hu Subject: [syslog-ng] [Bug 100] New: Hostnames that start with 4+ digits mess up the time system
https://bugzilla.balabit.com/show_bug.cgi?id=100
Summary: Hostnames that start with 4+ digits mess up the time system Product: syslog-ng Version: 2.0.x Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: D.Ojalvo@f5.com Type of the Report: --- Estimated Hours: 0.0
Created an attachment (id=26) --> (https://bugzilla.balabit.com/attachment.cgi?id=26) My patch proposal
If syslog is handling a message with an rfc 3164-type timestamp then a hostname that begins with 4 digits, the time parser will mess up because it thinks that it is dealing with a linksys-style timestamp that includes the year, when the rfc3164 timestamp does not. I wrote a patch that adds a strict rfc3164 parsing option to the syslog startup.
https://bugzilla.balabit.com/show_bug.cgi?id=100 Balazs Scheidler <bazsi@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution| |FIXED Status|NEW |RESOLVED --- Comment #1 from Balazs Scheidler <bazsi@balabit.hu> 2010-12-08 12:11:01 --- This is fixed in 3.0 already and I don't intend to maintain 2.0 anymore. Do you perhaps have an option to upgrade to a newer version? -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
participants (2)
-
bugzilla＠bugzilla.balabit.com
-
Patrick H.