Date: Tue, 19 Feb 2019 11:53:24 -0700 (MST) From: BBlister <bblister@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Cannot identify process of listening port 600/tcp6 Message-ID: <1550602404163-0.post@n6.nabble.com> In-Reply-To: <5b5f72fc-c054-ea43-6602-e7bdb742d657@sentex.net> References: <1550339000372-0.post@n6.nabble.com> <5b5f72fc-c054-ea43-6602-e7bdb742d657@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Yes you are right. If I kill rpc.lockd the two listening ports disappear. If I re-execute, then I can see two new unknown listening ports on other locations. For example, now I have 815/tcp4 and 874/tcp6 . So I believe I should ask the freebsd-hackers which rpc.lockd cannot be listed on the sockstat or lsof (which means that this could be a way for a malicious process to do exactly what lockd does and open ports without being identified). Thanks mdtancsa for your valuable tip. -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-questions-f3696945.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1550602404163-0.post>