Re: [Wireshark-dev] Security issue being reported by the SecuniaPSI scanner.

() is not used by Wireshark So most probably this is a non issue. Regards Anders -Ursprungligt meddelande- Från: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] För Richard Brooks Skickat: den 7 januari 2010 06:37 Till: 'Developer support list for

Re: [Wireshark-dev] How does Wireshark do name resolution?

l Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Andrew Hood Sent: 07 January 2010 11:39 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] How does Wireshark do name resolution? Richard Brooks wrote: > Hello

Re: [Wireshark-dev] Security issue being reported by the Secunia PSI scanner.

22:47 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Security issue being reported by the Secunia PSI scanner. Stephen Fisher wrote: > On Jan 6, 2010, at 3:20 PM, Richard Brooks wrote: > >> Hello Bill, in my last email I neglected to add the Secunia report &g

Re: [Wireshark-dev] How does Wireshark do name resolution?

rk Subject: Re: [Wireshark-dev] How does Wireshark do name resolution? On Jan 6, 2010, at 12:55 PM, Richard Brooks wrote: > I think that Sky have more than one email server/mirror. Try doing an > nslookup on '74.125.127.208', on my PC it came back as > 'pz-inf208.1e100.net

Re: [Wireshark-dev] How does Wireshark do name resolution?

onal insight. Sorry I couldn't be of more help, Chris ____ From: wireshark-dev-boun...@wireshark.org on behalf of Richard Brooks Sent: Wed 1/6/2010 3:30 PM To: 'Developer support list for Wireshark' Subject: Re: [Wireshark-dev] How does Wireshark do name

[Wireshark-dev] Security issue being reported by the Secunia PSI scanner.

A security issue is being reported by the 'Secunia PSI' vulnerability scanner (free non-commercial download available at their website). The vulnerability is located in 'C:\Program Files\Wireshark\libgdk-win32-2.0-0.dll' which is part of GTK2+. Are there any plans to code this issue out of the W

Re: [Wireshark-dev] How does Wireshark do name resolution?

[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Richard Brooks Sent: Wednesday, January 06, 2010 3:18 AM To: wireshark-dev@wireshark.org Subject: [Wireshark-dev] How does Wireshark do name resolution? I am writing an interface to Snort's MySQL database. The interface currently uses nslook

Re: [Wireshark-dev] How does Wireshark do name resolution?

Developer support list for Wireshark Subject: Re: [Wireshark-dev] How does Wireshark do name resolution? On Jan 6, 2010, at 12:17 AM, Richard Brooks wrote: > I am writing an interface to Snort's MySQL database. The interface currently > uses nslookup to try and resolve ip addresses t

Re: [Wireshark-dev] How does Wireshark do name resolution?

-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Richard Brooks Sent: Wednesday, January 06, 2010 3:18 AM To: wireshark-dev@wireshark.org Subject: [Wireshark-dev] How does Wireshark do name resolution? I am writing an interface to Snort's MySQL database

[Wireshark-dev] How does Wireshark do name resolution?

I am writing an interface to Snort's MySQL database. The interface currently uses nslookup to try and resolve ip addresses to their human friendly names, but Wireshark is doing a much better job than nslookup. For example using nslookup ip address '216.239.59.208' resolves to 'gv-in-f208.1e100.net'