Bug 574 - Default syslogd behavior of not binding udp/514 isn't true
Default syslogd behavior of not binding udp/514 isn't true
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: sysklogd (Show other bugs)
5.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1998-12-23 12:27 EST by beldridg
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-01-12 18:42:18 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description beldridg 1998-12-23 12:27:28 EST
According to the man page for syslogd,

"The default behavior is that syslogd won't listen to the
network."

Yet, check this out:

[root@gateway init.d]# uname -a
Linux gateway.home.com 2.0.36 #6 Mon Nov 23 13:16:03 PST
1998 i586 unknown
[root@gateway init.d]# cat /etc/issue

Red Hat Linux release 5.0 (Hurricane)
Kernel 2.0.36 on an i586

[root@gateway init.d]# lsof -i -P |grep 514
[root@gateway init.d]# syslogd -v
syslogd 1.3-3
[root@gateway init.d]# rpm -qf `which syslogd`
sysklogd-1.3-25                        (Note: upgraded to
latest RPM)
[root@gateway init.d]# syslogd         (Note: no -r flag
given)
[root@gateway init.d]# lsof -i -P |grep 514
syslogd 4880 root    1u  inet 0x010de810        0t0   UDP
*:514
[root@gateway init.d]# ./syslog stop
Shutting down system loggers: syslogd
[root@gateway init.d]# lsof -i -P |grep 514
[root@gateway init.d]#


Looks like a bug. What do you think?
Comment 1 David Lawrence 1999-01-12 18:42:59 EST
This is not a bug. Syslogd opens the port when it first starts but it
is not listening to the port. Therefore it is not a security concern.

syslogd   231 root    1u  inet 0x03636810        0t0  UDP *:514

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