On Mon, Mar 12, 2001 at 11:27:46AM -0800, Marc Wilson wrote:
> Try this in your firewall script:
>
> # anything NFS-like should not be accessible from outside
> NFSPORTS=`rpcinfo -p | awk '/tcp/||/udp/ {print $4}' | sort | uniq`
> for PORT_NUM in $NFSPORTS
> do $IPCHAINS -A input -i $extint -
5:20 AM
To: Debian-User List
Subject: Re: rpc.statd hacking but firewalled
<< File: ATT00568.dat >> On Mon, Mar 12, 2001 at 01:38:53AM -0700, Curtis
Hogg wrote:
> i don't recall what port rpc.statd binds to, but what it is is a part of
> the NFS system, so disabling rpc.st
On Mon, Mar 12, 2001 at 01:38:53AM -0700, Curtis Hogg wrote:
> i don't recall what port rpc.statd binds to, but what it is is a part of
> the NFS system, so disabling rpc.statd, i think, will also break NFS
> mounting on your side. you can still mount remote systems i think.
statd is bound to a ra
i don't recall what port rpc.statd binds to, but what it is is a part of
the NFS system, so disabling rpc.statd, i think, will also break NFS
mounting on your side. you can still mount remote systems i think.
And, yes, it is a hack attempt.. by some scriptkiddie trying to use a
common buffer overf
The following showed up in my syslog the other day Is this possbile
hacking?
What port is rpc.statd on?
What does it do?
What will break if it is turned off? and how to turn it off?
Only a few, selected ports, are listened on. The last rule in my
firewall script is ipchains -l -A input -i eth
5 matches
Mail list logo
