Re: pop3-capabilities error

[jah <jah () zadkiel plus com>]

On 03/02/2009 01:48, Brandon Enright wrote:
> On Tue, 03 Feb 2009 01:47:26 +0000
> jah <jah () zadkiel plus com> wrote:
>
> > On 03/02/2009 01:32, Brandon Enright wrote:
> > > I think the issue is that pop3.lua doesn't appear to try to use SSL
> > > to port 995 even though the service was fingerprinted as ssl/pop3.
> > > Shouldn't we be passing a protocol of 'ssl' or 'tcp' to the
> > > socket:connect routine rather than nothing (which defaults to TCP)?
> > We probably should.  Would you try the attached pop3.lua lib which
> > passes "ssl" if port.version.service_tunnel == "ssl"
>
> Sure, in a few minutes.  I noticed the SMTP commands script also times
> out on port 465 (SSL/SMTP).  That script passes in port.protocol to the
> socket connect.  Is the protocol for SSL wrapped ports still TCP?
I found some hosts I could test these mods on:

465/tcp open  ssl/smtp
|_ smtp-commands: EHLO <snip>, ENHANCEDSTATUSCODES, AUTH LOGIN PLAIN,
AUTH=LOGIN PLAIN, PIPELINING, 8BITMIME, SIZE 104857600
995/tcp open  ssl/pop3 Courier pop3d
|_ pop3-capabilities: USER IMPLEMENTATION(Courier Mail Server) UIDL
PIPELINING LOGIN-DELAY(10) TOP

so I've checked them in.

Regards,

jah

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org