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

From: Kaul <mykaul@xxxxxxxxx>
Date: Sun, 28 Mar 2010 21:18:23 +0300


On Fri, Mar 26, 2010 at 11:49 PM, Anders Broman <anders.broman@xxxxxxxxxxxx> wrote:
 


From: wireshark-dev-bounces@xxxxxxxxxxxxx [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Kaul
Sent: den 24 mars 2010 07:51

To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] How do I call the pkcs1 dissection from another dissector?

On Thu, Mar 18, 2010 at 10:39 AM, Anders Broman <anders.broman@xxxxxxxxxxxx> wrote:


-----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
 > 

 > I have a blob within my protocol that I is a PKCS#1  (v2.0, EME-OAEP format) that I'd be happy to dissect.
 > Y. 
Well what sort of ASN1 structures are included there? The pkcs1 dissector can dissect

RSAPublicKey


The above - RSA public key (128bytes, I believe).
TIA,
Y.
 

RSAPrivateKey

:
etc the reference in the heaser is RFC 2313
/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
___________________________________________________________________________
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


___________________________________________________________________________
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