Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] How do I call the pkcs1 dissection from another dissector?

From: Anders Broman <anders.broman@xxxxxxxxxxxx>
Date: Thu, 18 Mar 2010 09:39:35 +0100
 

-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Jeff Morriss
Sent: den 17 mars 2010 18:00
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] How do I call the pkcs1 dissection from another dissector?

Kaul wrote:
>> 
>> 
>> On Fri, Mar 12, 2010 at 12:21 AM, Jeff Morriss <jeff.morriss.ws 
>> <http://jeff.morriss.ws>@gmail.com <http://gmail.com>> wrote:
>> 
>>     Kaul wrote:
>>      > find_dissector("pkcs-1") doesn't seem to be the correct way to do it.
>>      > How do I do it?
>>      > There's a PKCS1 blob I want the PKCS#1 dissector to dissect. How do I
>>      > call it? I can create a TVB for it, of course.
>> 
>>     You'd need that dissector to be registered by name (by calling
>>     register_dissector()) first.
>> 
>> 
>> Can you elaborate a bit? Who's 'that' ? my dissector or the PKCS#1? 
>> And how do I make the PKCS#1 register? It is one of the automatically 
>> created dissectors...
>
>Sorry, I meant the PKCS#1 dissector (i.e., you'd have to modify the dissector).  Looking briefly at that 
>dissector, I don't quite know how
>register_dissector() should be called (in fact I'm not even clear what the entry point to that dissector is!).

I think that "pkcs" is normaly called from other dissectors using OID's. If you try to explain more explicity what you are trying to do possibly with an example trace we may be able to help you.
Regards
Anders
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe