Re: [Wireshark-dev] Decrypting SSL in dissector

So make a separate RSA key table within the amp protocol preferences? And then pass that along to SSL when the protocol goes encrypted? I assume the same issue impacts LDAP/TLS and XMPP? -Rob On Fri, Jan 10, 2014 at 11:51 AM, Jeff Morriss jeff.morriss...@gmail.comwrote: I think for that you

Re: [Wireshark-dev] Decrypting SSL in dissector

I'm missing? -Rob On Tue, Jan 7, 2014 at 3:23 PM, Rob Napier robnap...@gmail.com wrote: Kurt Knochner helpfully pointed me here versus my original ask.wireshark.org questionhttp://ask.wireshark.org/questions/28642/decrypting-ssl-in-dissector . I'm writing a new dissector for a protocol

Re: [Wireshark-dev] Decrypting SSL in dissector

of the protocol on the same port? -Rob On Thu, Jan 9, 2014 at 11:38 AM, Dirk Jagdmann d...@cubic.org wrote: do you have a new_register_dissector(amp, ...) in the proto_register_amp() function? Otherwise the SSL dissector can not match the amp string to a dissector handle/function

[Wireshark-dev] Decrypting SSL in dissector

, amp_handle); /* we are done */ return dissected_length; } I'm not certain where next to troubleshoot. Is there something else dissectors need to do in order to use SSL? I'm not getting warnings or errors. -Rob

[Wireshark-dev] Linux Compile

Hello, Perhaps I'm missing something, but I've read over a ton of mailing list entries and can't seem to find what I'm missing. I'm using Ubuntu 9.10 and I have everything loaded that I need to have loaded. In fact, when I run the ./autogen.sh, ./configure, and make, I don't have a problem at

[Wireshark-dev] Wireshark licence terms and dissectors

to give the source code for the dissector to our customers? Thanks in advance for any pointers. Rob Qasara Limited Harston Mill Campus, Harston Cambridge, CB22 7GG. www.qasara.com Company no. 06493679 E-mail: rob.mea

Re: [Wireshark-dev] Wireshark licence terms and dissectors

Hokay, so a dissector links with GPL code and must therefore be provided as source. Might be worth adding this as a note to the FAQ, whoever controls it, just to make it clear. Thanks! Rob -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun

Re: [Wireshark-dev] Wireshark licence terms and dissectors

) interpretation until a lawyer joins in and tells me otherwise (probably taking some weight off my wallet in the process). Rob -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Jaap Keuter Sent: 18 December 2008 16:36

Re: [Wireshark-dev] Wireshark licence terms and dissectors

in the FAQ. Rob -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Jaap Keuter Sent: 18 December 2008 17:11 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] Wireshark licence terms and dissectors Hi

Re: [Wireshark-dev] Working with pcap

is very standardized and outside Wireshark's control. This is more of a question relating to libpcap/winpcap or at least Wireshark-users. Good luck with your development, Rob MacKenzie Advanced Connectivity Developer -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED

Re: [Wireshark-dev] Interface

Run it as root. Alt-F2, then 'gksudo wireshark' Rob MacKenzie Advanced Connectivity Developer -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jacques Sent: June 2, 2008 3:29 PM To: wireshark-dev@wireshark.org Subject: [Wireshark-dev] Interface Good

[Wireshark-dev] Fwd: FW: [PATCH] New protocol dissector - Kingfisher

Re-sent from Google mail due to local mail server issues. -- Forwarded message -- From: Rob Casey [EMAIL PROTECTED] Date: Apr 19, 2007 9:02 AM Subject: FW: [PATCH] New protocol dissector - Kingfisher To: [EMAIL PROTECTED] -- *From:* Rob Casey