Date: Tue, 23 May 2000 22:49:31 -0700 From: Doug Barton <DougB@gorean.org> To: Oscar Ricardo Silva <oscars@mail.utexas.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Port 722 ? Message-ID: <392B6D6B.F429C4AE@gorean.org> References: <Pine.BSF.4.21.0005231624110.29966-100000@web2.sea.nwserv.com> <4.2.2.20000523180523.00a8f680@mail.utexas.edu> <Pine.BSF.4.21.0005231624110.29966-100000@web2.sea.nwserv.com> <4.2.2.20000523190214.00a976c0@mail.utexas.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Oscar Ricardo Silva wrote:
>
> Thanks to Dave Kirchner and Alan Clegg for the incredibly fast and
> completely useful responses. Using both methods, I found out this:
>
> amanda# /usr/local/sbin/lsof -i TCP:722
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> sshd1 143 root 3u IPv6 0xcb8e7940 0t0 TCP *:722
> sshd1 143 root 5u IPv4 0xcb8e7720 0t0 TCP *:722 (LISTEN)
>
> Now the question is, where the hell did this come from? I hadn't seen this
> before and I thought I'd checked my machine.
Unfortunately, it's included in the sshd_config file. I never saw a
satisfactory explanation as to why they did it, but the latest version
of the port has a patch that comments it out. In more recent versions of
freebsd you can do the steps outlined by previous posters all in one by
using sockstat, FYI.
Another way to solve this problem is to use openssh & openssl that are
included in 4.0. It's good stuff. :)
Good luck,
Doug
--
"Live free or die"
- State motto of my ancestral homeland, New Hampshire
Do YOU Yahoo!?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?392B6D6B.F429C4AE>