In article <[EMAIL PROTECTED]>,
Eric G. Miller wrote:
>On Sun, Feb 18, 2001 at 08:11:23PM +0100, Roberto Diaz wrote:
>> > Interesting ports on localhost (127.0.0.1):
>> > PortState Protocol Service
>> > 22 opentcpssh
>> > 111 opentcp
> > Well is a corcern since bugs can be possible.. and you need the portmap in
> > order to run things like postgresql.. but it is wrapped as you very well
> PostgreSQL listens on 5432 (if you have tcp turned on). What would it
> need rpc for? I have portmap turned off here and never had a proble
On Sun, Feb 18, 2001 at 08:11:23PM +0100, Roberto Diaz wrote:
> > Interesting ports on localhost (127.0.0.1):
> > PortState Protocol Service
> > 22 opentcpssh
> > 111 opentcpsunrpc
> >
> > I K'd out S10portmap in the /etc/r
Just a quick note to thank everyone for the input on this matter. It has
*all* been very instructive - forced me to learn (or take another look
at) how the system starts and *what* it starts, and so on.
:-)
Glenn Becker
Online Producer, Community
SCIFI.COM
At 12:06pm on Sun, 18 Feb 2001, Osamu
Use ipchains ASAP.
Going after all services are impossible when experimenting
unless you use this approach.
I block all ports 1-1023 except ones I use for my connection to
cable modem by using ipchains on gateway machine. (See atached
script for details. This is "ipmasq -l" output. You can get
> > And is it all right to keep 22 open like that? Apologies for the
> > rushed questions, I just want a box secure enough to allow me to
> > continue to experiment without worry. I can look into better
> > solutions later, like ipchains/firewalls.
> If you need to access your machine from several
> Interesting ports on localhost (127.0.0.1):
> PortState Protocol Service
> 22 opentcpssh
> 111 opentcpsunrpc
>
> I K'd out S10portmap in the /etc/rc0.d/ directory, but port 111 is still
> open. I can remove portmap from /
Hi:
I am down to this with nmap:
Interesting ports on localhost (127.0.0.1):
PortState Protocol Service
22 opentcpssh
111 opentcpsunrpc
I K'd out S10portmap in the /etc/rc0.d/ directory, but port 111 is still
open. I can
also sprach Roberto Diaz (on Sun, 18 Feb 2001 07:51:14PM +0100):
> Roberto Diaz <[EMAIL PROTECTED]>
> http://vivaldi.dtts.net
> Powered by ddt dynamic DNS
you really mean to change this to ddts.net. or else your "powered by"
clause may cast a shadow upon ddt since "dtts.net" doesn't exist...
mar
> What is exactly cadlock at port 770? I know is has something to do with
> sun rpc's.. what exactly is?
Ok I see is rpc.statd..
Regards
Roberto
Roberto Diaz <[EMAIL PROTECTED]>
http://vivaldi.dtts.net
Powered by ddt dyn
What is exactly cadlock at port 770? I know is has something to do with
sun rpc's.. what exactly is?
Regards
Roberto
Roberto Diaz <[EMAIL PROTECTED]>
http://vivaldi.dtts.net
Powered by ddt dynamic DNS
Powered by GNU runni
Dave,
Wow. As a matter of fact, I *am* running portsentry.
I take it then that running portsentry is not in itself a risk ...
Thanks for helping me avert my own coronary. ":-)
Glenn Becker
Online Producer, Community
SCIFI.COM
At 10:45am on Sun, 18 Feb 2001, Dave Sherohman wrote:
> On Sun, Fe
On Sun, Feb 18, 2001 at 10:32:58AM -0500, Glenn Becker wrote:
> What the hell *are* these things and how did they suddenly blast open
> after I had shut down all but three? I have changed nothing - and when I
> check inetd.conf and the other directories I edited, they are still the
> same. Ex: I co
All,
Not long after my last message to the list last night re: open ports, I
was chatting on IRC and got an email message from logcheck re: a system
attack. It appeared from the message that the attack had been
repelled; however, now when I run nmap, I get this:
Interesting ports on localhost (1
14 matches
Mail list logo
