Nmap Development mailing list archives

Re: pop3-capabilities error


From: Brandon Enright <bmenrigh () ucsd edu>
Date: Tue, 3 Feb 2009 01:32:35 +0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 03 Feb 2009 01:25:31 +0000
jah <jah () zadkiel plus com> wrote:

On 02/02/2009 23:52, Brandon Enright wrote:
I did run into this though:

SCRIPT ENGINE (506.424s): ./scripts/pop3-capabilities.nse against
a.b.1.47:995 ended with error: ./scripts/pop3-capabilities.nse:32:
bad argument #1 to 'pairs' (table expected, got string)
I've fixed this in r11947 - pop3.lua either couldn't connect, or
didn't get a response after connecting to a.b.1.47
and the library returned a string error message instead of the table
pop3-capabilities was expecting.

Regards,

jah


Thanks Jah, I pulled the script down after your commit and it seems to
be working now.

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)?

Brandon

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkmHnrkACgkQqaGPzAsl94LRngCgj2+r/bV3qZSNXXgPBmr+Muta
fysAmwez2gzmzuDTtgQwWCXnF2tisTGB
=Nsg6
-----END PGP SIGNATURE-----

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


Current thread: