Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 18671

Summary:	syslogd accepts arbitrary timestamps on messages
Product:	[Retired] Red Hat Linux	Reporter:	Tim <tim_r>
Component:	sysklogd	Assignee:	Jason Vas Dias <jvdias>
Status:	CLOSED CURRENTRELEASE	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	abartlet, dr
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-08-30 21:35:44 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 .