Date: Sun, 13 Apr 2003 20:41:51 -0500 (CDT) From: Mike Silbersack <silby@silby.com> To: Barney Wolff <barney@pit.databus.com> Cc: net@freebsd.org Subject: Re: connect(2) behavior with unreacheable hosts Message-ID: <20030413203958.I93049@odysseus.silby.com> In-Reply-To: <20030414011530.GA80964@pit.databus.com> References: <109.225ca595.2bc723f2@aol.com> <20030412.204912.76964336.imp@bsdimp.com> <20030412.212059.42399637.imp@bsdimp.com> <20030414011530.GA80964@pit.databus.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 13 Apr 2003, Barney Wolff wrote: > Mike, I don't think this is a security issue - the client gets an instant > SIGPIPE if it tries to write on the socket. I think telnet gets this. > > I did try traceroute, since it depends on time-exceeded. Worked fine. > Barney > > -- > Barney Wolff http://www.databus.com/bwresume.pdf Ok, so any properly written application will handle the case without issue, that's what I was curious about. I'll _try_ to get to committing the patch, but it'll be a few days at the minimum. Mike "Silby" Silbersack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030413203958.I93049>