Date: Fri, 6 Oct 2000 17:00:34 +0300 From: Peter Pentchev <roam@orbitel.bg> To: Drew Derbyshire <software@kew.com> Cc: security@FreeBSD.ORG Subject: Re: sockstat (was Re: cvs commit: src/etc inetd.conf) Message-ID: <20001006170034.D232@ringwraith.office1.bg> In-Reply-To: <002101c02f99$a04b6010$94cba8c0@hh.kew.com>; from software@kew.com on Fri, Oct 06, 2000 at 09:30:43AM -0400 References: <39D93044.8B0C4E69@ursine.com> <Pine.BSF.4.21.0010030332190.15413-100000@surreal.nl> <20001006153343.B232@ringwraith.office1.bg> <002101c02f99$a04b6010$94cba8c0@hh.kew.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 06, 2000 at 09:30:43AM -0400, Drew Derbyshire wrote: > > And to paraphrase an earlier comment by DES, > > "Funny way to say sockstat | fgrep '*.*'" :) > > Urp! > > sockstat seems to truncate port numbers on the FOREIGN ADDRESS under 4.1 > release ... Almost true - sockstat trims *both* local and foreign addresses to 20 chars each. However, in the case discussed, the issue was listening ports, which are in most cases bound to '*.portno' locally and always show '*.*' as foreign address. [3 minutes of source browsing] Uhm.. correction :) sockstat trims local and foreign addresses to 20 chars each, but netstat (which sockstat invokes), when invoked with -Aan (which is how sockstat invokes it), trims local and foreign addresses to 18 chars each to fit all the info on one line :( So the problem is with netstat, or rather with sockstat's usage of -A to get the socket control block address, to link it with fstat's output later. G'luck, Peter -- .siht ekil ti gnidaer eb d'uoy ,werbeH ni erew ecnetnes siht fI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001006170034.D232>