> Excuse your arrogance, but let me correct you in some points you made!
>
> First of all nmap does not scan only the services listed
in /etc/services, if
> you were to have bothered reading the manual before answering you
would have
> read, and I quote:
If you had actually read what I'd wri
> Excuse your arrogance, but let me correct you in some points you made!
>
> First of all nmap does not scan only the services listed
in /etc/services, if
> you were to have bothered reading the manual before answering you
would have
> read, and I quote:
If you had actually read what I'd wri
> Excuse your arrogance, but let me correct you in some points you made!
>
> First of all nmap does not scan only the services listed
in /etc/services, if
> you were to have bothered reading the manual before answering you
would have
> read, and I quote:
If you had actually read what I'd wr
> Excuse your arrogance, but let me correct you in some points you made!
>
> First of all nmap does not scan only the services listed
in /etc/services, if
> you were to have bothered reading the manual before answering you
would have
> read, and I quote:
If you had actually read what I'd wr
Staffin <[EMAIL PROTECTED]>
Date: Sat, 20 Oct 2001 23:27:09 -0500
Subject: Re: Port Scan for UDP
> On Sat, Oct 20, 2001 at 09:22:57PM -0700, tony mancill blathered
> thusly:
> > A good way to find out what process is listening on a port is to
> load the
> > lsof package
Staffin <[EMAIL PROTECTED]>
Date: Sat, 20 Oct 2001 23:27:09 -0500
Subject: Re: Port Scan for UDP
> On Sat, Oct 20, 2001 at 09:22:57PM -0700, tony mancill blathered
> thusly:
> > A good way to find out what process is listening on a port is to
> load the
> > lsof package
On Sun, Oct 21, 2001 at 09:49:02AM -0600, orly-fu wrote:
> First of all nmap does not scan only the services listed in /etc/services, if
> you were to have bothered reading the manual before answering you would have
> read, and I quote:
> "The default is to scan all ports between 1 and 1
Excuse your arrogance, but let me correct you in some points you made!
First of all nmap does not scan only the services listed in /etc/services, if
you were to have bothered reading the manual before answering you would have
read, and I quote:
"The default is to scan all ports between 1
On Sun, Oct 21, 2001 at 09:49:02AM -0600, orly-fu wrote:
> First of all nmap does not scan only the services listed in /etc/services, if
> you were to have bothered reading the manual before answering you would have
> read, and I quote:
> "The default is to scan all ports between 1 and
Excuse your arrogance, but let me correct you in some points you made!
First of all nmap does not scan only the services listed in /etc/services, if
you were to have bothered reading the manual before answering you would have
read, and I quote:
"The default is to scan all ports between 1
Wow! Craig...you are the MAN! This explains a number of other
questions I had too. Thank you very much!
jc
Craig McPherson, 2001-Oct-21 10:45 -0500:
> I can't believe nobody has answered this correctly yet. UDP is
> different than TCP in that it is a stateless protocol, and that means
> you
thanks for your explanation.
regards,
Volker
On Sun, Oct 21, 2001 at 10:45:28AM -0500,
Craig McPherson <[EMAIL PROTECTED]> wrote:
> I can't believe nobody has answered this correctly yet. UDP is
> different than TCP in that it is a stateless protocol, and that means
> you have to understand a
Wow! Craig...you are the MAN! This explains a number of other
questions I had too. Thank you very much!
jc
Craig McPherson, 2001-Oct-21 10:45 -0500:
> I can't believe nobody has answered this correctly yet. UDP is
> different than TCP in that it is a stateless protocol, and that means
> yo
I can't believe nobody has answered this correctly yet. UDP is
different than TCP in that it is a stateless protocol, and that means
you have to understand a few things to interpret UDP port scan results
correctly. With TCP scans, you get one of three results: OPEN
(meaning that the TCP hand
Hi,
On Sun, Oct 21, 2001 at 05:47:11PM +0200,
Petre Daniel <[EMAIL PROTECTED]> wrote:
>
> also netstat -n -p -t --listening | grep ":PORT"
sure, but it shows you only tcp connections.
regards,
Volker
> VD> You can also use "netstat -pan" to find out which process is listening on
> VD> which p
-BEGIN PGP SIGNED MESSAGE-
Hash: MD5
also netstat -n -p -t --listening | grep ":PORT"
VD> Hi,
VD> On Sat, Oct 20, 2001 at 09:22:57PM -0700,
VD> tony mancill <[EMAIL PROTECTED]> wrote:
>> On Sat, 20 Oct 2001, Marc Wilson wrote:
>>
>> > Adding or removing lines in /etc/services doesn't op
thanks for your explanation.
regards,
Volker
On Sun, Oct 21, 2001 at 10:45:28AM -0500,
Craig McPherson <[EMAIL PROTECTED]> wrote:
> I can't believe nobody has answered this correctly yet. UDP is
> different than TCP in that it is a stateless protocol, and that means
> you have to understand
I can't believe nobody has answered this correctly yet. UDP is
different than TCP in that it is a stateless protocol, and that means
you have to understand a few things to interpret UDP port scan results
correctly. With TCP scans, you get one of three results: OPEN
(meaning that the TCP han
Hi,
On Sun, Oct 21, 2001 at 05:47:11PM +0200,
Petre Daniel <[EMAIL PROTECTED]> wrote:
>
> also netstat -n -p -t --listening | grep ":PORT"
sure, but it shows you only tcp connections.
regards,
Volker
> VD> You can also use "netstat -pan" to find out which process is listening on
> VD> which
-BEGIN PGP SIGNED MESSAGE-
Hash: MD5
also netstat -n -p -t --listening | grep ":PORT"
VD> Hi,
VD> On Sat, Oct 20, 2001 at 09:22:57PM -0700,
VD> tony mancill <[EMAIL PROTECTED]> wrote:
>> On Sat, 20 Oct 2001, Marc Wilson wrote:
>>
>> > Adding or removing lines in /etc/services doesn't o
Hi!
Take a look at "/etc/inetd.conf". There are some services you
are looking for. Try to comment thoose services and make a restart of
the "inetd" daemon. (Something as `/etc/init.d/inetd stop` &
`/etc/init.d/inetd start')
Bye
--
-
Hi,
On Sat, Oct 20, 2001 at 09:22:57PM -0700,
tony mancill <[EMAIL PROTECTED]> wrote:
> On Sat, 20 Oct 2001, Marc Wilson wrote:
>
> > Adding or removing lines in /etc/services doesn't open or close ports...
> > this is a common misconception. Removing what's listening on a particular
> > port is
Hi!
Take a look at "/etc/inetd.conf". There are some services you
are looking for. Try to comment thoose services and make a restart of
the "inetd" daemon. (Something as `/etc/init.d/inetd stop` &
`/etc/init.d/inetd start')
Bye
--
tony mancill, 2001-Oct-20 21:22 -0700:
> On Sat, 20 Oct 2001, Marc Wilson wrote:
>
> > On Sat, Oct 20, 2001 at 07:18:25PM -0700, Jeff Coppock wrote:
> > > Just for grins, I removed every udp listing in
> > > /etc/services and restarted inetd and the scan came back the
> > > same. I figure this is
On Sat, Oct 20, 2001 at 09:22:57PM -0700, tony mancill blathered thusly:
> A good way to find out what process is listening on a port is to load the
> lsof package and use "lsof -i" (as root so that you'll see everything).
I find that fuser is more convenient at times - fuser -v -n udp
returns th
On Sat, 20 Oct 2001, Marc Wilson wrote:
> On Sat, Oct 20, 2001 at 07:18:25PM -0700, Jeff Coppock wrote:
> > Just for grins, I removed every udp listing in
> > /etc/services and restarted inetd and the scan came back the
> > same. I figure this is normal, but if someone can confirm this
> > behavi
On Sat, Oct 20, 2001 at 07:18:25PM -0700, Jeff Coppock wrote:
> Just for grins, I removed every udp listing in
> /etc/services and restarted inetd and the scan came back the
> same. I figure this is normal, but if someone can confirm this
> behaviour, I'd really appreciate it.
Adding or removing
Hi,
On Sat, Oct 20, 2001 at 09:22:57PM -0700,
tony mancill <[EMAIL PROTECTED]> wrote:
> On Sat, 20 Oct 2001, Marc Wilson wrote:
>
> > Adding or removing lines in /etc/services doesn't open or close ports...
> > this is a common misconception. Removing what's listening on a particular
> > port i
tony mancill, 2001-Oct-20 21:22 -0700:
> On Sat, 20 Oct 2001, Marc Wilson wrote:
>
> > On Sat, Oct 20, 2001 at 07:18:25PM -0700, Jeff Coppock wrote:
> > > Just for grins, I removed every udp listing in
> > > /etc/services and restarted inetd and the scan came back the
> > > same. I figure this i
I'm doing portscans on a system I'm working to learn more about
securing hosts and setting up iptables. My tcp portscan reported
what I expected, only www, ssh and smtp listening. The udp
portscan reported a huge list of 'open' ports. I really didn't
know what to expect for this scan, so I want
On Sat, Oct 20, 2001 at 09:22:57PM -0700, tony mancill blathered thusly:
> A good way to find out what process is listening on a port is to load the
> lsof package and use "lsof -i" (as root so that you'll see everything).
I find that fuser is more convenient at times - fuser -v -n udp
returns t
On Sat, 20 Oct 2001, Marc Wilson wrote:
> On Sat, Oct 20, 2001 at 07:18:25PM -0700, Jeff Coppock wrote:
> > Just for grins, I removed every udp listing in
> > /etc/services and restarted inetd and the scan came back the
> > same. I figure this is normal, but if someone can confirm this
> > behav
On Sat, Oct 20, 2001 at 07:18:25PM -0700, Jeff Coppock wrote:
> Just for grins, I removed every udp listing in
> /etc/services and restarted inetd and the scan came back the
> same. I figure this is normal, but if someone can confirm this
> behaviour, I'd really appreciate it.
Adding or removing
I'm doing portscans on a system I'm working to learn more about
securing hosts and setting up iptables. My tcp portscan reported
what I expected, only www, ssh and smtp listening. The udp
portscan reported a huge list of 'open' ports. I really didn't
know what to expect for this scan, so I want
34 matches
Mail list logo
