[Wireshark-dev] Store selected Wireshark prefs in pcapng capture file ?
Would it make any sense to be able to store application specific information in a pcapng file ? E.g., selected Wireshark prefs so that Wireshark can act on same ? This would be useful when a capture file reqires specific dissector preferences to properly dissect the file. Would this fit (at all) within the design goals for pcapng ? Is there be a way to do this reasonably cleanly with the existing format ? How might one indicate the prefs which should to be stored ? Bill ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Store selected Wireshark prefs in pcapng capture file ?
Hi Bill, I don't know if the format's developers ever contemplated that use case - although they designed it to be fairly extensible, and I'm sure that someone could design a new type of block that stores serialised application preferences (in compressed XML, JSON, or some other format?), after requesting an type ID for it. I haven't thought too much about how you'd actually go about deciding upon the preferences to store - although adding a universal Save Current Preferences option to the file saving dialogue, and having an option in the corresponding file opening dialogue to temporarily import/set those preferences might work. I'm sure that others will come up with better ideas, though... Tyson. On 5 March 2012 18:26, Bill Meier wme...@newsguy.com wrote: Would it make any sense to be able to store application specific information in a pcapng file ? E.g., selected Wireshark prefs so that Wireshark can act on same ? This would be useful when a capture file reqires specific dissector preferences to properly dissect the file. Would this fit (at all) within the design goals for pcapng ? Is there be a way to do this reasonably cleanly with the existing format ? How might one indicate the prefs which should to be stored ? Bill ___ Sent via: Wireshark-dev mailing list wireshark-dev@wireshark.org Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe -- Fight Internet Censorship! http://www.eff.org http://vmlemon.wordpress.com | Twitter/FriendFeed/Skype: vmlemon | 00447934365844 ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Store selected Wireshark prefs in pcapng capture file ?
Hi, I think there is two paths that can be taken either add options and/or blocks as needed to the file format or encode the comment in some way, using the preferences simple format is one option. I'm leaning towards using the comments somehow. One could have Wireshark begin/end tags for other programs to skip that part of the comments. Regards Anders Tyson Key skrev 2012-03-05 19:39: Hi Bill, I don't know if the format's developers ever contemplated that use case - although they designed it to be fairly extensible, and I'm sure that someone could design a new type of block that stores serialised application preferences (in compressed XML, JSON, or some other format?), after requesting an type ID for it. I haven't thought too much about how you'd actually go about deciding upon the preferences to store - although adding a universal Save Current Preferences option to the file saving dialogue, and having an option in the corresponding file opening dialogue to temporarily import/set those preferences might work. I'm sure that others will come up with better ideas, though... Tyson. On 5 March 2012 18:26, Bill Meierwme...@newsguy.com wrote: Would it make any sense to be able to store application specific information in a pcapng file ? E.g., selected Wireshark prefs so that Wireshark can act on same ? This would be useful when a capture file reqires specific dissector preferences to properly dissect the file. Would this fit (at all) within the design goals for pcapng ? Is there be a way to do this reasonably cleanly with the existing format ? How might one indicate the prefs which should to be stored ? Bill ___ Sent via:Wireshark-dev mailing listwireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Store selected Wireshark prefs in pcapng capture file ?
Anders Broman skrev 2012-03-05 20:03: Hi, I think there is two paths that can be taken either add options and/or blocks as needed to the file format or encode the comment in some way, using the preferences simple format is one option. I'm leaning towards using the comments somehow. One could have Wireshark begin/end tags for other programs to skip that part of the comments. Regards Anders Rethinking :-) shb_ws_display_filterString multiple occuranse, coupled shb_ws_display_filter_comment shb_ws_capture_profileA complete profile which goes with the capture and gets loaded as the default profile when the capture is loaded if so configured. Could be useful additions that may not be to difficult to do something useful with. Tyson Key skrev 2012-03-05 19:39: Hi Bill, I don't know if the format's developers ever contemplated that use case - although they designed it to be fairly extensible, and I'm sure that someone could design a new type of block that stores serialised application preferences (in compressed XML, JSON, or some other format?), after requesting an type ID for it. I haven't thought too much about how you'd actually go about deciding upon the preferences to store - although adding a universal Save Current Preferences option to the file saving dialogue, and having an option in the corresponding file opening dialogue to temporarily import/set those preferences might work. I'm sure that others will come up with better ideas, though... Tyson. On 5 March 2012 18:26, Bill Meierwme...@newsguy.com wrote: Would it make any sense to be able to store application specific information in a pcapng file ? E.g., selected Wireshark prefs so that Wireshark can act on same ? This would be useful when a capture file reqires specific dissector preferences to properly dissect the file. Would this fit (at all) within the design goals for pcapng ? Is there be a way to do this reasonably cleanly with the existing format ? How might one indicate the prefs which should to be stored ? Bill ___ Sent via:Wireshark-dev mailing listwireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Store selected Wireshark prefs in pcapng capture file ?
On Mar 5, 2012, at 11:03 AM, Anders Broman wrote: I think there is two paths that can be taken either add options and/or blocks as needed to the file format or encode the comment in some way, using the preferences simple format is one option. I'm leaning towards using the comments somehow. One could have Wireshark begin/end tags for other programs to skip that part of the comments. I presume you don't mean store them in opt_comment options, as other apps should not have to know about special tags in comments to indicate that they're not really comments. I'd go for registering a wireshark preferences option and just have it store raw preferences-file text; we'd also want, I think, another option for UATs, with the name of the UAT and its contents. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Store selected Wireshark prefs in pcapng capture file ?
Bill Meier wrote: Would it make any sense to be able to store application specific information in a pcapng file ? E.g., selected Wireshark prefs so that Wireshark can act on same ? This would be useful when a capture file reqires specific dissector preferences to properly dissect the file. Would this fit (at all) within the design goals for pcapng ? Is there be a way to do this reasonably cleanly with the existing format ? How might one indicate the prefs which should to be stored ? First thought: Keep a list of protocols in the capture file. For each, store only the preferences (if any) for that protocol which don't have the default value. ___ Sent via:Wireshark-dev mailing list wireshark-dev@wireshark.org Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
