Re: fingerd bug isn't

2014-11-20 Thread Stuart Henderson 
On 2014/11/19 22:32, Ted Unangst wrote:
 I don't think this qualifies as a bug. Using the wrong client is user
 error. fingerd should not be responsible for filtering anything you
 shouldn't send it.

That makes much more sense than adding the same text to smtpd, httpd, bgpd, 
etc. :-)
OK.

Re: fingerd bug isn't

2014-11-20 Thread Todd C. Miller 
On Wed, 19 Nov 2014 22:32:59 -0500, Ted Unangst wrote:

 I don't think this qualifies as a bug. Using the wrong client is user
 error. fingerd should not be responsible for filtering anything you
 shouldn't send it.

OK millert@ (who wonders how many people even know what a TIP is these days)

 - todd

Re: fingerd bug isn't

2014-11-19 Thread Theo de Raadt 
 I don't think this qualifies as a bug. Using the wrong client is user
 error. fingerd should not be responsible for filtering anything you
 shouldn't send it.

Completely agree.  1990 was a tough time with these issues.


 Index: fingerd.8
 ===
 RCS file: /cvs/src/libexec/fingerd/fingerd.8,v
 retrieving revision 1.19
 diff -u -p -r1.19 fingerd.8
 --- fingerd.8 14 Nov 2013 08:50:04 -  1.19
 +++ fingerd.8 20 Nov 2014 03:31:21 -
 @@ -166,18 +166,3 @@ The
  .Nm
  command appeared in
  .Bx 4.3 .
 -.Sh BUGS
 -Connecting directly to the server from a
 -.Tn TIP
 -or an equally narrow-minded
 -.Tn TELNET Ns -protocol
 -user program can result
 -in meaningless attempts at option negotiation being sent to the
 -server, which will foul up the command line interpretation.
 -.Nm
 -should be taught to filter out
 -.Tn IAC Ns 's
 -and perhaps even respond
 -negatively
 -.Pq Tn IAC WON'T
 -to all option commands received.