Re: [Wireshark-dev] dissect_per_constrained_integer() with

t-Type: text/plain; charset="utf-8" Hi Pavel, 2016-12-21 15:37 GMT+01:00 Pavel Strnad <strn...@tiscali.cz>: > Hello, > > I am trying to understand the difference in usage of NO_BOUND or > UINT_MAX in the place of max parameter in > dissect_per_constrained_integer() funct

[Wireshark-dev] dissect_per_constrained_integer() with no_bound (MAX in ASN.1)

Hello, I am trying to understand the difference in usage of NO_BOUND or UINT_MAX in the place of max parameter in dissect_per_constrained_integer() function. In my case aligned PER variant. >From packet-per.h: #define NO_BOUND -1 guint32 dissect_per_constrained_integer(tvbuff_t *tvb,

Re: [Wireshark-dev] cmake build on windows without libpcap

>> Does anyone currently build without libpcap? >> Intention is to build Wireshakr for windows without capturing options as >> analyzer only. >> >> I have found an option for cmake -DENABLE_PCAP=OFF but doing so results in >> errors below (related to caputils and qtui): > >Probably no comfort to

[Wireshark-dev] cmake build on windows without libpcap

Hi list, Does anyone currently build without libpcap? Intention is to build Wireshakr for windows without capturing options as analyzer only. I have found an option for cmake -DENABLE_PCAP=OFF but doing so results in errors below (related to caputils and qtui):

Re: [Wireshark-dev] cmake build on windows without libpcap

c9...@alum.mit.edu> >Content-Type: text/plain; charset=us-ascii > >On May 12, 2017, at 1:38 AM, Pavel Strnad <strn...@tiscali.cz> wrote: > >> I am using latest build from master branch. > >What is the last commit to the ma

Re: [Wireshark-dev] Wireshark-dev Digest, Vol 132, Issue 16

reshark-dev] cmake build on windows without libpcap >Message-ID: <f98d8215-d877-479e-ab1d-e0d2129e1...@alum.mit.edu> >Content-Type: text/plain; charset=us-ascii > >On May 12, 2017, at 7:19 AM, Pavel Strnad <strn...@tiscali.cz> wrote: > >> Do You have any build op

[Wireshark-dev] tshark: export to pdml improvements

Hi list, I am proposing following pdml export improvements: 1) fix for bug introduced in 2.4 in SHA-1:b8ead953758304 where level incrementing was missed in the fake protocol wrapper and due to that level is getting negative for LUA cases 2) improve indentation for Close off fake wrapper protocol

Re: [Wireshark-dev] tshark: export to pdml improvements

for Wireshark Subject: Re: [Wireshark-dev] tshark: export to pdml improvements Hi Pavel, Le 2 déc. 2017 16:45, "Pavel Strnad" <strn...@tiscali.cz> a écrit : Hi list, I am proposing following pdml export improvements: 1) fix for bug introduced in 2.4 in SHA-1:b8ead953758304 where le

Re: [Wireshark-dev] asn2wrs: autodetection for 64 bits X constrained integers

] asn2wrs: autodetection for 64 bits X constrained integers Hi Pavel, 2017-10-25 8:34 GMT+02:00 Pavel Strnad <strn...@tiscali.cz>: Hi list, can we improve auto detection for 64b variant of constrained integers? In the master branch we handle the cases of integers over/under +/- 2^32 bu

[Wireshark-dev] asn2wrs: autodetection for 64 bits X constrained integers

Hi list, can we improve auto detection for 64b variant of constrained integers? In the master branch we handle the cases of integers over/under +/- 2^32 but what about MIX.. and ..MAX constants? There are such dissectors in our current source tree: h245, t125, x509,.. that should use 64b instead