Re: [Wireshark-dev] Feature: option to open windows as tabs

2018-05-05 Thread Guy Harris
On May 5, 2018, at 9:02 AM, Michał Łabędzki wrote: > This change is also the first step for Support Multiple Capture Files > (like web browsers - one* tab is one capture file / packet list). Presumably "one window or tab is one capture file / packet list", for those of us who *don't* like tabs

Re: [Wireshark-dev] Feature: option to open windows as tabs

2018-05-05 Thread Guy Harris
On May 5, 2018, at 10:04 AM, Peter Wu wrote: > Memory usage will probably suck due to exact copies of the process, On most if not all UN*Xes, the executable image's code and read-only data, and libwireshark's/libwiretap's/libwsutil's code and read-only data, should be shared between all of the

Re: [Wireshark-dev] Feature: option to open windows as tabs

2018-05-05 Thread Peter Wu
Hi Michael, On Sat, May 05, 2018 at 06:02:00PM +0200, Michał Łabędzki wrote: > I have a nice feature: option to open windows as tabs. Please see > review: https://code.wireshark.org/review/#/c/27363/ > > Peter asked me to start the discussion about that because there is a > plan to have a dockabl

[Wireshark-dev] Feature: option to open windows as tabs

2018-05-05 Thread Michał Łabędzki
Hello, I have a nice feature: option to open windows as tabs. Please see review: https://code.wireshark.org/review/#/c/27363/ Peter asked me to start the discussion about that because there is a plan to have a dockable windows feature. I do not know more about "Dockable Windows" feature but as I

Re: [Wireshark-dev] Embed SSL keylog file in pcap-ng

2018-05-05 Thread Guy Harris
On May 5, 2018, at 2:07 AM, Ahmad Fatoum wrote: >> On 5May 2018, at 10:47, Guy Harris wrote: >> >> That doesn't require "some authority that allocates protocol identifiers", >> because it doesn't require protocol identifiers; all that needs to be done >> is to allocate pcapng block types to t

Re: [Wireshark-dev] Embed SSL keylog file in pcap-ng

2018-05-05 Thread Ahmad Fatoum
> On 5May 2018, at 10:47, Guy Harris wrote: > > That doesn't require "some authority that allocates protocol identifiers", > because it doesn't require protocol identifiers; all that needs to be done is > to allocate pcapng block types to those protocols that require some > additional inform

Re: [Wireshark-dev] Embed SSL keylog file in pcap-ng

2018-05-05 Thread Guy Harris
On May 5, 2018, at 1:40 AM, Ahmad Fatoum wrote: >> On 5May 2018, at 09:31, Guy Harris wrote: >> >> "Support multiple protocols in a capture" in what sense? > > multiple protocols with a key block each, e.g. TLS and Tibia interleaved in > the same capture file. That doesn't require "some auth

Re: [Wireshark-dev] Embed SSL keylog file in pcap-ng

2018-05-05 Thread Ahmad Fatoum
Hi, > On 5May 2018, at 09:31, Guy Harris wrote: > > "Support multiple protocols in a capture" in what sense? multiple protocols with a key block each, e.g. TLS and Tibia interleaved in the same capture file. > On 4May 2018, at 09:21, Paul Zander wrote: > > Via fields in this block we can de

Re: [Wireshark-dev] Embed SSL keylog file in pcap-ng

2018-05-05 Thread Guy Harris
On May 4, 2018, at 2:32 PM, Ahmad Fatoum wrote: >> On 4May 2018, at 19:10, Guy Harris wrote: >> >> That might *also* be useful, but the advantage of blocks that *aren't* tied >> to Wireshark is that *other* programs can use the data without having to >> track Wireshark. > > I see, but to sup