Re: Exp Branch for OpenSSL on Windows

[Kris Katterjohn <katterjohn () gmail com>]

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

Hey Thomas,

Thomas Buchanan wrote:
> Kris,
>
> I did check the branch out, and it compiled fine for me.  I had to make
> one slight change, unrelated to the SSL stuff (I have to prepend
> /cygdrive to all of the Cywin paths in mswin32/Makefile).
> Unfortunately, I really haven't had a chance to do any significant
> testing with it.

Thanks for testing what you could.

> Thanks for getting this out there where it's easy to test and review.

No problem.  You did the initial work of figuring everything out, so the
least I could do is get it integrated :) Thanks again for spending so
much time on it, it's great to have.

> If I get a little time in the next few weeks, I'd really like to get
> back to the OpenSSL bindings for NSE.  I have a couple of scripts
> sitting in my private SVN repo that require it, and they've proved
> really useful for some of the scans that I do regularly.  I also really
> like the idea that Brandon mentioned re: SSHD host fingerprints.  I'm
> not sure what OpenSSL functions would be required to get a script like
> that working, but it sounds like a fun challenge!  :)

That'd be great!  I don't know what Fyodor and Diman have in mind, but I
may be able to help you with the bindings (or probably an NSE SoC
student if not me).  If I'm helping, we can just keep everything in my
current branch since it's so well-named :)

And Brandon's idea is an interesting one.  Any functions required for
that will be most likely be useful for some future scripts as well, so
it's a good idea to get it going.

> Thomas

Thanks,
Kris Katterjohn


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

iQIVAwUBSCzMjv9K37xXYl36AQJwgQ/9EOCGI/oROHpo9eHH/4nefjtnUaa1F8EL
CE87jJsUiB7EEhU6f7V35eZqqyc3XQ/seKY61p+kUD0waB0a1srGIjzu5G7YT7Xt
87LpIXeTvf7N3C8j3YT7GMXVnJ9OYfktG+6QCM6uYM99urFuhCNTgBn3NWlFE4dL
MUR7df+4Kn1t9/nE2kFSmDsrT3SEQ2Y4HzUQ6IBEjkbC3gyr2dmm8zNkltfPQnmx
EX3XgeaJXOhkRQPrBOyuNi+KAUYyqM9UpctPfYLNTWfpSGib+U94eV8GYhK2dHj7
ANHHQsTPIPTeldTEoMeyNKNn29EEmOHooNDvrENCrDgEBXFqIlDx3IyUPbqOJ6MD
HKOVmL3arq0ulbQxIXoJMf3Ku6vsiFwKUN8VAhs8F1fqkmbI3c0lbbQUHHFokASH
eNf60tB9N79SCDeTjLkjUjJtxk9cE+AOy8pYQvNUBNs6jy4hzw6GKotgQQGWrrm9
UkKss4/390DIyjKvDURwSOTqZfcaccI+SXBP9yIeDOZbtF8o66kuFo5DqKvr5DBH
qMGd/KuVm6mBIFaNJ43HQJKGZtzSdV42dunleYsPoveZAI0N62Dk7sqmUFzEchXj
CdhSAtOYfNovR/3diZ8vBsFfrWzBzuOZQ0ISkxrgpPaB9JNyBC2Iy+vxGfyJlZO6
9ooccT+rhtE=
=4T4D
-----END PGP SIGNATURE-----

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