Bug 185279

Summary:	Security enhancement, suggested
Product:	Red Hat Enterprise Linux 4	Reporter:	Kevin Verma <kevinverma>
Component:	sysklogd	Assignee:	Peter Vrabec <pvrabec>
Status:	CLOSED WONTFIX	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.0	Keywords:	FutureFeature
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-11-14 12:38:09 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 Kevin Verma 2006-03-13 07:32:11 UTC

Description of problem:
When sysklogd started to except logs from remost hosts, it blindly starts
expecting logs from any host and any network interface, it is desirable if that
can be contained to particular interfaces and hosts. An interim solution could
be a listen or interface directive/option.

Version-Release number of selected component (if applicable):
all

Comment 1 Kevin Verma 2006-10-29 07:13:02 UTC

s/except/accept
s/expecting/accepting

PS: I am not sure if I was my mind was wandering somewhere else while I filed 
this bug finally. Sorry for the pain you must have had gone through to
understand the exact enhancement I suggested and thanks for having this assigned.

Comment 2 Peter Vrabec 2006-11-14 12:38:09 UTC

I'm sorry, but "$man syslog" claims that you have to implement kernel 
firewalling to limit which hosts or networks have access to the 514/UDP 
socket.