[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Portsentry works fine: port 111
- Subject: Re: [cobalt-users] Portsentry works fine: port 111
- From: "John Theriault" <cabal@xxxxxxxxxxx>
- Date: Fri Mar 30 06:28:03 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
----- Original Message -----
From: "John Theriault" <cabal@xxxxxxxxxxx>
To: <cobalt-users@xxxxxxxxxxxxxxx>
Sent: Friday, March 30, 2001 3:51 PM
Subject: Re: [cobalt-users] Portsentry works fine: port 111
> ----- Original Message -----
> From: "Marc Gear" <marcg@xxxxxxxxxxxxxx>
> To: <cobalt-users@xxxxxxxxxxxxxxx>
> Sent: Friday, March 30, 2001 6:30 AM
> Subject: Re: [cobalt-users] Portsentry works fine: port 111
>
>
> > > >> what's so special about port 111 (this sun remot procedure call)?
> >
> > As john said, its the sunrpc port and there are a while world of
exploits
> > availiable for it.arbiet rather outdated ones.
> >
> > > > looks like the anklebitters are hoping your raq will be an easy
> > > > target.
> >
> > it is more likley that they were not specifically hoping his raq was an
> easy
> > target, rather scanning a while range of ports with 111 open, probably a
> > couple of class B's Dont think you're being picked on, or special in
some
> > way cos you got scanned on this port :)
> >
> > --
> > /\/\ a R (
>
> Good point. =) I was trying to imply that the server was being
specifically
> targeted. I apologize if me message implied that.
>
Er... I wasn't trying to imply that... heh. Sorry. It's hard typing on a
keyboard while being bombarded with phone calls and other crap. =)
J.