Re: Port Scan for UDP

2001-10-20 Thread Jeff Coppock
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

Re: Port Scan for UDP

2001-10-20 Thread Ben Staffin
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

Re: Port Scan for UDP

2001-10-20 Thread tony mancill
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

Re: Port Scan for UDP

2001-10-20 Thread Marc Wilson
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

Re: Port Scan for UDP

2001-10-20 Thread Volker Dormeyer
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

Re: Port Scan for UDP

2001-10-20 Thread Jeff Coppock
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

Port Scan for UDP

2001-10-20 Thread Jeff Coppock
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

Re: Port Scan for UDP

2001-10-20 Thread Ben Staffin
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

Re: Port Scan for UDP

2001-10-20 Thread tony mancill
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

Re: Port Scan for UDP

2001-10-20 Thread Marc Wilson
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

Port Scan for UDP

2001-10-20 Thread Jeff Coppock
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