Nmap Development mailing list archives

Re: Exp Branch for OpenSSL on Windows


From: Kris Katterjohn <katterjohn () gmail com>
Date: Mon, 19 May 2008 20:15:45 -0500

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

jah wrote:
On 15/05/2008 17:01, Kris Katterjohn wrote:
Hey guys,

Has anybody tested this at all?  Just let me know if you have/had any
problems.

As I said before, you shouldn't have to change anything in your build
procedure; it should just work.
It built just fine with no changes
.

Great, thanks for testing.

I had a play with version detection against some ssl websites and
noticed that if nmap couldn't get a version match from "Server Hello"
messages and had to go as far as handling "change cipher spec" and
"encrypted handshake" messages, the cpu cycles went through the roof.
I thought I'd see if building OpenSSL on this machine would make any
difference.  This was straightforward too, due to the great
upgrade-guide (I was thrown slightly by "Compilation failed" messages
when I ran do_ms.bat and thought it might be worth updating the guide to
mention that these can be safely ignored).

Good idea.

I rebuilt nmap with openssl, but it didn't have any appreciable effect
and I note that in the minute that it took to successfully complete
version detection, one of my dual cores was at full-pelt for around 45
seconds.  I'll look into this more deeply, but I wonder if anyone else
noticed similar?


I haven't noticed anything like this happening, but I'll try against
some more hosts.  Have you been able to look into it any more?

regards,
jah


Thanks a lot,
Kris Katterjohn

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIVAwUBSDImP/9K37xXYl36AQLKyBAAg/Gqb6Fk9r5v+uCQEuJhtZZiKkQYXqIM
jLliPhUkzbH8AqKVUQsymFoOkeukjh/qPTL8mv8B8DWcVQXHm/CHBV8d8PkC9fl4
JXEFe4HJQm4KQdj5+FUVTsx2sscUfannCdpJdiFrFzRz4HbT0T77E01oZSWoSvaO
tt77nH+RKCiikZR011w3hUhWo/V5pZKmzR5ZyeQutnxYsp+QuM74NC67f74L9sQk
XswepPZ8vGxmMiVK2wTOCG9IUgutZtDiH+Zh8e7Ki39ONeJQzA3ue2FMnLNlLY5S
3hcS0MtGz075CiNSYSCRbPOuggOdIXY706kSfJ6GG4ctWVZiFxKGiGvFR1V9zOdq
IHOy4DltNgU6EkqLmof69Oz+oMFna6BFXVgdQleIM7VouFdJWwRYvr2AMhjzHUbW
kEcrOnQWiGMUy1exbqJ0auOLt8FG9WaMsSfWThMgIxZq0hxiyQxT7cSE6CzhhT6s
dFpVwZ5CWXPPGFUMySzQ6dVNxVBbO/7VpDbPHYditDXOl1DD/ziUTbrIhuwR+25Q
3Aor77dtY0j/c6lb3LuNuQw1KmVqHzh53g1Pdw9PJaVTkjx7mExP7ZFXFpZ6nGj5
4SHsFLU1y4dLIWlfZlPdZXOSBumWBVEqx2TCd43MsLITMHd9MX0r9uKfXM8AOfkC
RE0NhA+jAXc=
=q0pQ
-----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: