Nmap Announce mailing list archives
Re: (local?) linux DoS using nmap
From: moses () pentagram nslug ns ca
Date: Sun, 6 Jun 1999 11:59:32 -0300 (ADT)
On Thu, 3 Jun 1999, cami wrote:
kernel:~$ nmap 127.0.[0-255].[0-255] -sT And what do u get? all services go bye-bye.
If you look through your logs you'll see entries like this: Jun 6 11:54:30 pentagram inetd[327]: ftp/tcp server failing (looping), service terminated man inetd says you can change this by appending a number after the wait/nowait entry in inetd.conf: The optional ``max'' suffix (separated from ``wait'' or ``nowait'' by a dot) specifies the maximum number of server instances that may be spawned from inetd within an interval of 60 seconds. When omitted, ``max'' defaults to 40. Just kill -1 inetd to reenable. I think ssh getting slow was just ssh getting slow (from all the daemons being forked).
Current thread:
- (local?) linux DoS using nmap cami (Jun 02)
- Re: (local?) linux DoS using nmap Mr. Man (Jun 02)
- Re: (local?) linux DoS using nmap Vidyut Luther (Jun 03)
- <Possible follow-ups>
- Re: (local?) linux DoS using nmap cami (Jun 03)
- Re: (local?) linux DoS using nmap Lamont Granquist (Jun 03)
- Re: (local?) linux DoS using nmap Ken Williams (Jun 05)
- Re: (local?) linux DoS using nmap moses (Jun 06)
- Re: (local?) linux DoS using nmap Mr. Man (Jun 02)