Bug 18671 - syslogd accepts arbitrary timestamps on messages
Summary: syslogd accepts arbitrary timestamps on messages
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sysklogd
Version: 6.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-10-09 03:33 UTC by Tim
Modified: 2007-04-18 16:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-08-30 21:35:44 UTC
Embargoed:


Attachments (Terms of Use)

Description Tim 2000-10-09 03:33:47 UTC
syslogd accepts arbitrary timestamps on messages read from /dev/log. If 
the message matches the pattern "??? ?? ??:??:?? " then it will be treated 
as a timestamp. syslogd should always prefix the message with the local 
machine's timestamp, and for backwards compatability, remove anything that 
looks like a timestamp from the start of the message to avoid the 
timestamp appearing twice. This is similar to bug id 10222.

Comment 1 Jason Vas Dias 2004-08-30 21:35:44 UTC
Just clearing out old bugs here. This one was fixed ages ago!
Current version of sysklogd is 1.41-22 .


Note You need to log in before you can comment on or make changes to this bug.