Re: [Wireshark-dev] File rename impacts Gitlab history

On Feb 26, 2021, at 8:48 AM, chuck c wrote: > https://gitlab.com/wireshark/wireshark/-/commit/50dbe4df7fd7a5e4e1a27fd5046981486d350994 > Rename packet-ssl* to packet-tls* > > Looking through history of > https://gitlab.com/wireshark/wireshark/-/commits/master/epan/dissectors/packet-tls.c > >

Re: [Wireshark-dev] File rename impacts Gitlab history

Thanks! It's always an education poking around in the Gitlab gui file history/commits but this is much quicker. admin1@MSEDGEWIN10:/mnt/c/Development/wireshark$ git log -p --follow epan/dissectors/packet-tls.c | grep -e "11129" -e "commit" commit 17170ea1fe6fe8758897611a4375e57a4ee851cb commit

Re: [Wireshark-dev] OID not implemented

https://datatracker.ietf.org/doc/rfc6962/?include_text=1 Internet Engineering Task Force (IETF) B. Laurie Request for Comments: 6962A. Langley Category: Experimental E. Kasper ISSN: 2070-1721

Re: [Wireshark-dev] 90GB pcap file get last frame time stamp

The pcapng file format supports "backwards" reading. -Original Message- From: Wireshark-dev On Behalf Of Richard Sharpe Sent: den 26 februari 2021 18:39 To: Developer support list for Wireshark Subject: Re: [Wireshark-dev] 90GB pcap file get last frame time stamp On Fri, Feb 26, 2021

Re: [Wireshark-dev] 90GB pcap file get last frame time stamp

I tried to respond, but used the wrong email somehow. Here's the text of it The tricky part of it is how the PCAP headers are structured. If you look at the packet header format, there's nothing that by default says that it's a packet header. So to make sure we can return the timestamp of the

Re: [Wireshark-dev] 90GB pcap file get last frame time stamp

On Fri, Feb 26, 2021 at 9:10 AM Raj sekar wrote: > > Hi Everyone! > > Need a help. Is there any library or method to get large pcap file's( offline > ) last timestamp. > > I know capinfos can get this. But i want faster than capinfos. > > Any suggestion? Because each captured frame can be a

Re: [Wireshark-dev] OID not implemented

On Fri, 26 Feb 2021 at 17:30, chuck c wrote: > You were not wrong. > > https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers > 11129 > Google, Inc. > Ben Laurie > benl > > 1.3.6.1.4.1 is Private.Enterprise and the next branch (11129) is the > Enterprise ID. > > Which

Re: [Wireshark-dev] OID not implemented

32622 CACE Technologies Gerald Combs info Is this now the Enterprise ID for Wireshark? On Fri, Feb 26, 2021 at 11:29 AM chuck c wrote: > You were not wrong. > > https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers > 11129 > Google, Inc. > Ben Laurie >

Re: [Wireshark-dev] OID not implemented

You were not wrong. https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers 11129 Google, Inc. Ben Laurie benl 1.3.6.1.4.1 is Private.Enterprise and the next branch (11129) is the Enterprise ID. On Fri, Feb 26, 2021 at 11:20 AM Graham Bloice wrote: > Well now I'm

Re: [Wireshark-dev] OID not implemented

Well now I'm embarrassed, I'd fat fingered the OID into the lookup site and wandered down a rabbit hole from there. Odd that the OID info site returns Google for 1.3.6.1.4.1.11129 which led me astray. Sorry for the noise. On Fri, 26 Feb 2021 at 17:04, chuck c wrote: > What version of

Re: [Wireshark-dev] File rename impacts Gitlab history

On 26/02/21 16:48, chuck c wrote: https://gitlab.com/wireshark/wireshark/-/commit/50dbe4df7fd7a5e4e1a27fd5046981486d350994 Rename packet-ssl* to packet-tls* Looking through history of

[Wireshark-dev] 90GB pcap file get last frame time stamp

Hi Everyone! Need a help. Is there any library or method to get large pcap file's( offline ) last timestamp. I know capinfos can get this. But i want faster than capinfos. Any suggestion? Thanks Best Regards Raj ___ Sent

Re: [Wireshark-dev] OID not implemented

What version of Wireshark? Supported added here: https://gitlab.com/wireshark/wireshark/-/commit/c529e9110a211bc445a94c2ed68acc14fe108384 TLS: add Signed Certificate Timestamp support (RFC 6962) Feb 14, 2017 5:09pm CST /* Certificate Transparency extensions: 2 (Certificate), 5 (OCSP Response)

Re: [Wireshark-dev] OID not implemented

It appears to be an unregistered OID, On Fri, 26 Feb 2021 at 16:23, Petersen Sean wrote: > Hi, > > > > Could you give me some more context on what the below means: > > > > > > Is this just a wireshark error or is this an indication of something > unhealthy with the communication? > > This

[Wireshark-dev] File rename impacts Gitlab history

https://gitlab.com/wireshark/wireshark/-/commit/50dbe4df7fd7a5e4e1a27fd5046981486d350994 Rename packet-ssl* to packet-tls* Looking through history of https://gitlab.com/wireshark/wireshark/-/commits/master/epan/dissectors/packet-tls.c

[Wireshark-dev] OID not implemented

Hi, Could you give me some more context on what the below means: [cid:image001.png@01D70C59.51FA2690] Is this just a wireshark error or is this an indication of something unhealthy with the communication? Thanks, Sean Petersen | Systems Engineer, New Zealand Mobile +64 21-417-7388