Re: bin/44671: syslogd sends udp dgrams from port 65534

[Berczi Gabor <gabor%berczi.be@localhost>]

The following reply was made to PR bin/44671; it has been noted by GNATS.

From: Berczi Gabor <gabor%berczi.be@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: gnats-admin%netbsd.org@localhost,
 netbsd-bugs%netbsd.org@localhost
Subject: Re: bin/44671: syslogd sends udp dgrams from port 65534
Date: Thu, 3 Mar 2011 10:05:08 +0100

 On Mar 3, 2011, at 9:30 AM, Takahiro Kambe wrote:
 
 >>> Do you expect that syslogd send from syslog port?
 >> Yes.
 > Your expectation isn't correct.
 
 Actually it is.
 
 > It is RECOMMENDED that the source port also be 514 to indicate that =
 the message is from the syslog process of the sender
 
 I have no idea (yet) who and why decided that port 65534 is so sweet, =
 but it sure does remind me of the case of Rui Paolo =
 (http://gabucino.be/files/netbsd-paolo-sigfpe.html), and the =
 Wikipedia-certified division by zero in ping.
 
 Additionally, NetBSD syslogd is only bugged with the -s option. Do note =
 that for example FreeBSD's syslogd -s works as expected.
 
 > Both suggests using sender's port to UDP/514 but not mandated.  So,
 > you would need to change this PR to be:
 >=20
 > - withdrawed.
 > - changed to request adding a option to bind source port to UDP/514.
 
 You would need to change this PR to be:
 
 - fixed
 - changed to request a manual page fix to specifically document this =
 inexplicable behaviour of SecureMode
 
 Best regards.