Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:
edgeos



Nmap Development: Re: Nmap 4.23RC3 & SSL Tunnels

Re: Nmap 4.23RC3 & SSL Tunnels

From: Kris Katterjohn <katterjohn_at_gmail.com>
Date: Fri, 07 Dec 2007 12:23:05 -0600

Thomas Buchanan wrote:
>> Kris Katterjohn writes:
>> > What about something general like this:
>> >
>> > <linkedwith>
>> > <library name="openssl" version="[version]" />
>> > <library name="libpcap" version="[version]" />
>> > <library name="libpcre" version="[version]" />
>> > <!-- etc -->
>> > </linkedwith>
>>
>> Fine by me.
>>
>> Lionel
>>
>
> How does the attached patch (against SVN r6441) look? It prints the
> library versions for libpcap, libpcre, liblua (if included) and openssl
> (if included).
>
> Some questions that I had:
>
> 1. Where should the output go in the XML file? I put it right after
> the verbosity / debugging information.
>

That seems fine to me, because there's not really a great place for it
to go :)

> 2. What level of verbosity / debugging should be required to include
> this information? The patch reflects my opinion that it should be
> included at debugging >=1.
>

AFAIK, in general, things are printed in the XML output independent of
whether verbosity/debugging is enabled (unlike normal output which is
completely controlled by this).

>
> Thomas

Thanks,
Kris Katterjohn

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

[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
edgeos