From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Nielsen To: 9fans@cse.psu.edu Subject: Re: [9fans] IMAP clients and plan9 imap server Message-ID: <20031005195431.GI834@cassie.foobarbaz.net> References: <200310051756.h95HuUj18681@augusta.math.psu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200310051756.h95HuUj18681@augusta.math.psu.edu> User-Agent: Mutt/1.5.3i Date: Sun, 5 Oct 2003 12:54:31 -0700 Topicbox-Message-UUID: 608e7a4e-eacc-11e9-9e20-41e7f4b1d025 On Sun, Oct 05, 2003 at 01:56:30PM -0400, Dan Cross wrote: > David Presotto writes: > > > > nmap does an incredibly bad job identifying whats behind plan 9 ports > > because we're not worth their time to know about. At least it finds > > the open ports, even though we often have different services there > > than others do. > > I don't know about that; if Matthias's list was complete, nmap missed > about four open ports I have running pure Plan 9 services (rexexec, > cpu, etc). However, he did show me that I had a pop3 running that I > didn't want (which I've now turned off. Thanks, Matthias!). Then > again, I don't suppose nmap scans every possible port i in Z_65536. nmap, by default, doesn't check all ports; just most of the well-known ports. you can set a command line switch to have it check specific ranges. -- Christopher Nielsen "They who can give up essential liberty for temporary safety, deserve neither liberty nor safety." --Benjamin Franklin