Wireshark

  • Riverbed Technology
  • WinPcap
the world's foremost network protocol analyzer
  • Wireshark
    • About
    • Download
    • Blog
  • Get Help
    • Ask a Question
    • FAQs
    • Documentation
    • Mailing Lists
    • Online Tools
    • Wiki
    • Bug Tracker
  • Develop
    • Get Involved
    • Developer's Guide
    • Browse the Code
    • Latest Builds

Wireshark-dev: Re: [Wireshark-dev] Use of EXTERNALt

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next


From: Stig Bjørlykke <stig.bjorlykke@xxxxxxxxx>
Date: Wed, 7 Nov 2007 21:34:33 +0100

On 7. nov.. 2007, at 11.00, Kukosa, Tomas wrote:

my idea when I introduced external structure into asn1_ctx_t and when I implemented dissect_per_external_type() was followng: - dissect_per/ber_external_type() dissects internal structure of EXTERNAL type and fills in all actx->external structure - dissect_per/ber_external_type() does not make any decision how to dissec embedded data (they can be decoded in BER, PER or any other non ASN.1 encoding) - dissect_per/ber_external_type() calls calback function and dissectors decides what to to based on actx->external structure and its local context and any other conditions



Ah, ok. And this functionality is not implemented in packet-ber yet, right?


--
Stig Bjørlykke



  • References:
    • [Wireshark-dev] Use of EXTERNALt
      • From: Anders Broman
    • Re: [Wireshark-dev] Use of EXTERNALt
      • From: Stig Bjørlykke
    • Re: [Wireshark-dev] Use of EXTERNALt
      • From: Kukosa, Tomas
  • Prev by Date: [Wireshark-dev] New WTAP_FILE_TYPE
  • Next by Date: Re: [Wireshark-dev] 0.99.7 release?
  • Previous by thread: Re: [Wireshark-dev] Use of EXTERNALt
  • Next by thread: Re: [Wireshark-dev] Use of EXTERNALt
  • Index(es):
    • Date
    • Thread

Wireshark and the "fin" logo are registered trademarks of the Wireshark Foundation