[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] RPC (port 111) attacks on CobaltRaq3
- Subject: [cobalt-users] RPC (port 111) attacks on CobaltRaq3
- From: "Zarrir Junior" <zarrir@xxxxxxxxxxxx>
- Date: Tue May 8 17:01:58 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Of all the "visits" Portsentry detects everyday on my server, 90% are
directed to port 111. I´m pretty sure i have RPC disabled at inetd. Does the
bellow boot message confirm this or not?
May 8 15:46:48 ns kernel: portmap: RPC call returned error 111
May 8 15:46:48 ns kernel: RPC: task of released request still queued!
May 8 15:46:48 ns kernel: RPC: (task is on xprt_pending)
May 8 15:46:53 ns kernel: portmap: RPC call returned error 111
May 8 15:46:53 ns kernel: RPC: task of released request still queued!
May 8 15:46:53 ns kernel: RPC: (task is on xprt_pending)
May 8 15:46:53 ns kernel: lockd_up: makesock failed, error=-111
May 8 15:46:58 ns kernel: portmap: RPC call returned error 111
May 8 15:46:58 ns kernel: RPC: task of released request still queued!
May 8 15:46:58 ns kernel: RPC: (task is on xprt_pending)
If it does, may i set Portsentry not to listen to port 111 anymore
(my hosts.deny list is becoming huge)? If it does not, what happened to 111?
Regards,
Zarrir