Re: bin/49868: tftpd(8) doesn't play well with clients that return acknowledgements to the broadcast address

[christos%zoulas.com@localhost (Christos Zoulas)]

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

From: christos%zoulas.com@localhost (Christos Zoulas)
To: Brian Buhrow <buhrow%via.net@localhost>, gnats-bugs%NetBSD.org@localhost, 
	gnats-admin%NetBSD.org@localhost, netbsd-bugs%NetBSD.org@localhost
Cc: buhrow%nfbcal.org@localhost
Subject: Re: bin/49868: tftpd(8) doesn't play well with clients that return acknowledgements to the broadcast address
Date: Thu, 30 Apr 2015 17:47:22 -0400

 On Apr 30,  2:40pm, buhrow%via.net@localhost (Brian Buhrow) wrote:
 -- Subject: Re: bin/49868: tftpd(8) doesn't play well with clients that retur
 
 | 	Hello.  The only way to get the tftpd to return packets to the
 | broadcast address is if inetd can be tricked into initiating a connection
 | with a broadcast address.  In looking at the inetd(8) source code, it looks
 | like there are checks in there to assure that this doesn't happen.  The
 | change I'm making won't allow traffic to be redirected to a broadcast
 | address after the fact even if a reply comes from a broadcast address
 | in the midle of a session.  That's because tftpd(8) only sets the client's
 | source address from the socket passed to it by inetd(8).  Once that's done,
 | it doesn't change for the life of the session.
 | -thanks
 | -Brian
 
 Great!
 
 I'd still put a comment in the source where we turn broadcast on why this
 is done, and why it is ok (so people are not mystified in the future).
 
 christos