Re: [Wireshark-dev] [tcpdump-workers] New RFCs for 1) pcap file format and 2) rpcapd protocol?

2020-03-22 Thread Francois-Xavier Le Bail
On 22/03/2020 18:29, Guy Harris via tcpdump-workers wrote: > 5) Treat rpcap as "remote procedure call for libpcap" and put it under the > the-tcpdump-group team, and put pcap under the pcapng team as per the same > reason as 4). Ok.

Re: [Wireshark-dev] [tcpdump-workers] New RFCs for 1) pcap file format and 2) rpcapd protocol?

2020-03-22 Thread Guy Harris
On Mar 21, 2020, at 2:38 PM, Guy Harris via tcpdump-workers wrote: > On Mar 21, 2020, at 2:14 PM, Guy Harris via tcpdump-workers > wrote: > >> The options I see are: > > 4) add a new team for rpcap, as it's a protocol rather than a file format, > and thus only indirectly tied to

Re: [Wireshark-dev] [tcpdump-workers] New RFCs for 1) pcap file format and 2) rpcapd protocol?

2020-03-22 Thread Guy Harris
On Mar 22, 2020, at 9:49 AM, Michael Tuexen wrote: > I would support this. However, last time I tried this, I was not successful. > There were not very interested in defining a file format... They've done so in the past: https://tools.ietf.org/html/rfc1761 (and

Re: [Wireshark-dev] Build failure (kerberos)

2020-03-22 Thread Dario Lombardo
Ok, thanks. On Sun, Mar 22, 2020 at 9:48 AM Martin Mathieson < martin.r.mathie...@googlemail.com> wrote: > >>> ./asn1/kerberos/packet-kerberos-template.c: In function >>> ‘dissect_krb5_PAC_CREDENTIAL_INFO’: >>> ./asn1/kerberos/packet-kerberos-template.c:2187:2: error: implicit >>> declaration of

Re: [Wireshark-dev] [tcpdump-workers] New RFCs for 1) pcap file format and 2) rpcapd protocol?

2020-03-22 Thread Michael Tuexen
> On 21. Mar 2020, at 23:10, Michael Richardson wrote: > > > Guy Harris via tcpdump-workers wrote: >> Currently, on GitHub, there's a "pcapng" team: >> https://github.com/pcapng > >> with one repository containing the pcapng specification, and a >> "the-tcpdump-group" team: > >>

Re: [Wireshark-dev] [tcpdump-workers] New RFCs for 1) pcap file format and 2) rpcapd protocol?

2020-03-22 Thread Michael Richardson
Guy Harris via tcpdump-workers wrote: > Currently, on GitHub, there's a "pcapng" team: > https://github.com/pcapng > with one repository containing the pcapng specification, and a "the-tcpdump-group" team: > https://github.com/the-tcpdump-group > with repositories for

Re: [Wireshark-dev] [tcpdump-workers] New RFCs for 1) pcap file format and 2) rpcapd protocol?

2020-03-22 Thread Francois-Xavier Le Bail
On 21/03/2020 22:14, Guy Harris via tcpdump-workers wrote: > 1) has the slight disadvantage that the name for the team suggests it's for > pcapng only; it appears that teams can be renamed: > > >

Re: [Wireshark-dev] [tcpdump-workers] New RFCs for 1) pcap file format and 2) rpcapd protocol?

2020-03-22 Thread Mario Rugiero
El sáb., 21 mar. 2020 18:15, Guy Harris via tcpdump-workers < tcpdump-work...@lists.tcpdump.org> escribió: > 1) has the slight disadvantage that the name for the team suggests it's > for pcapng only; it appears that teams can be renamed: > > >

Re: [Wireshark-dev] New RFCs for 1) pcap file format and 2) rpcapd protocol?

2020-03-22 Thread Eliot Lear
This very much depends on how stable you wish the spec to be.  If you want to to be entirely osified, I recommend actual RFCs.  Otherwise, perhaps a renamed team like "pcap-format" (or whatever the people on the team want to call it)? Eliot On 21.03.20 22:15, Guy Harris wrote: > There should

Re: [Wireshark-dev] Build failure (kerberos)

2020-03-22 Thread Martin Mathieson via Wireshark-dev
Hi Dario, KERBEROS is listed among OPTIONAL packages not found (at the end of cmake output). I will also attach CMakeCache.txt. -- The following OPTIONAL packages have been found: * Git * GMODULE2 * PCAP * ZLIB * LZ4 , LZ4 is lossless compression algorithm used in some protocol (CQL...) ,