Re: [Wireshark-dev] Editor config and code formatting

2022-03-02 Thread Graham Bloice
mailing list > >> Archives:https://www.wireshark.org/lists/wireshark-dev > >> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > >> mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe > > > ___ &

Re: [Wireshark-dev] MSVC gives warnings "qt_ui_utils.cpp(208, 25): warning C4996: 'QProcess::startDetached'"

2022-02-11 Thread Graham Bloice
ark.org > ?subject=unsubscribe > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-d

Re: [Wireshark-dev] Visual Studio 2022

2022-01-15 Thread Graham Bloice
ild\vcvars64.bat > > > You can specify the workloads as arguments to the > The first line of `cl.exe /?` returns > > > Microsoft (R) C/C++ Optimizing Compiler Version 19.30.30706 for x64 > > > The MSVC version numbering is somewhat exotic, the table given by Wikip

Re: [Wireshark-dev] Including sharkd in the installation downloads

2022-01-07 Thread Graham Bloice
reshark > that doesn't include sharkd, how will you get permission to install > Wireshark that does include it? > > >> Best regards...Paul >> >> -- >> >> Paul Offord >> > > > -- > Graham Bloice > > > -- Graham Bloice ___

Re: [Wireshark-dev] Including sharkd in the installation downloads

2022-01-06 Thread Graham Bloice
installers? > I don't see any issue in doing so if the application is adequately documented. However, if it's difficult to get permission to install Wireshark that doesn't include sharkd, how will you get permission to install Wireshark that does include it? > Best regards...Paul &g

Re: [Wireshark-dev] Are Capture Filters Implemented in Software or the Network Card?

2021-11-21 Thread Graham Bloice
m (taking some CPU) and must be > filtered (taking some CPU), but, if the packet doesn't pass the filter, no > *further* work has to be done on the packet, saving the CPU effort required > for that. I think there are also specialized capture cards that can filter in hardware, e.g. Endace

Re: [Wireshark-dev] Wireshark 3.4.8 build from source tarball fails generating build files

2021-08-27 Thread Graham Bloice
; Thank you again for your timely assistance. > > Michael Lum > > -- > *From:* Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] *On > Behalf Of *Graham Bloice > *Sent:* August-27-21 12:43 AM > *To:* Developer support list for Wireshark > *Su

Re: [Wireshark-dev] Merge blocked: the source branch must be rebased onto the target branch.

2021-08-27 Thread Graham Bloice
y am I getting this merge blocked? > > > > Thanks, > > > > --Jorge > > > -- Graham Bloice ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Un

Re: [Wireshark-dev] Wireshark 3.4.8 build from source tarball fails generating build files

2021-08-27 Thread Graham Bloice
...@starsolutions.com) | *STAR* *SOLUTIONS* > <http://www.starsolutions.com/> | Principal Software Engineer > 4600 Jacombs Road, Richmond BC, Canada V6V 3B1 | +1.604.303.2315 > > ___ > Sent via:Wiresha

Re: [Wireshark-dev] Can no longer file bugs at https://bugs.wireshark.org/bugzilla/

2021-07-30 Thread Graham Bloice
often, but the last time a > did, I few years ago, this was no problem. > > Is there anything I should do to fix this? > > Yes, go to our GitLab instance and file an issue: https://gitlab.com/wireshark/wireshark/-/issues The bugzilla ins

Re: [Wireshark-dev] Missing User Guide

2021-07-15 Thread Graham Bloice
te then the *.pdf ! > > It's gone, see https://gitlab.com/wireshark/wireshark/-/merge_requests/3213 I also miss the chm. > Thank you > > Kind regards > > Walter > > > > -- Graham Bloice __

Re: [Wireshark-dev] warning LNK4291: module may contain '__except' but was not compiled with /guard:ehcont

2021-07-02 Thread Graham Bloice
> c:\development\wireshark\epan\wslua\init_wslua.c : fatal error > C1001: Internal compiler error. [C:\Development\wsbuild64\epan\epan.vcxproj] > LINK : fatal error LNK1000: Internal error during > IMAGE::BuildImage [C:\Development\wsbuild64\epan\epan.vcxproj] >

Re: [Wireshark-dev] warning LNK4291: module may contain '__except' but was not compiled with /guard:ehcont

2021-07-02 Thread Graham Bloice
On Fri, 2 Jul 2021 at 17:28, Graham Bloice wrote: > > > On Fri, 2 Jul 2021 at 17:21, Maynard, Christopher via Wireshark-dev < > wireshark-dev@wireshark.org> wrote: > >> > From: Wireshark-dev On Behalf Of >> Graham Bloice >> > Sent: Friday, July 2,

Re: [Wireshark-dev] warning LNK4291: module may contain '__except' but was not compiled with /guard:ehcont

2021-07-02 Thread Graham Bloice
On Fri, 2 Jul 2021 at 17:21, Maynard, Christopher via Wireshark-dev < wireshark-dev@wireshark.org> wrote: > > From: Wireshark-dev On Behalf Of > Graham Bloice > > Sent: Friday, July 2, 2021 11:53 AM > > To: Developer support list for Wireshark > > Subject: Re

Re: [Wireshark-dev] warning LNK4291: module may contain '__except' but was not compiled with /guard:ehcont

2021-07-02 Thread Graham Bloice
xproj] > > - Chris > > > I'd be interested to know if you see link errors on subsequent rebuilds as noted by Martin M and myself in emails discussions today. -- Graham Bloice ___ Sent via:Wireshark-d

Re: [Wireshark-dev] Struggling to build NSIS installation

2021-06-22 Thread Graham Bloice
ill be \lib\asciidoctorj\tools\asciidoctorj-x.x.x\bin\asciidoctorj.bat) sets JVM options for memory. I've never come across this before, and can't remember it being reported elsewhere. Best regards, > Martin > -- Graham Bloice _

Re: [Wireshark-dev] Struggling to setup Windows command-line build

2021-06-22 Thread Graham Bloice
age: image.png] > > Is the prompt set up for building x64? What's the value of the platform env var? > I am able to build Wireshark from inside the VS IDE. > > Apologies for not digging deeper into this myself, I use linux and only > create occasional internal Windows release

Re: [Wireshark-dev] Calling a dissector: Type for data parameter

2021-05-30 Thread Graham Bloice
g/lists/wireshark-dev >> Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev >> mailto:wireshark-dev-requ...@wireshark.org >> ?subject=unsubscribe >> > _______ > Sent via:

Re: [Wireshark-dev] wslua: checkNSTime / pushNSTime undefined

2021-05-28 Thread Graham Bloice
W:\Development\wireshark\epan\wslua\wslua_tree.c(111,31): error >> C2220: ^ >> [W:\Development\wsbuild\epan\wslua\wslua.vcxproj] >> W:\Development\wireshark\epan\wslua\wslua_frame_info.c(112,32): >> error C2220: the following warning is tre

Re: [Wireshark-dev] Windows HTML Help

2021-05-26 Thread Graham Bloice
t; Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe > -- Graham Bloice ___

Re: [Wireshark-dev] Question / nit / ocd trigger

2021-05-24 Thread Graham Bloice
the correct implementation at the start or maybe a Neuralyzer ( https://meninblack.fandom.com/wiki/Neuralyzer) -- Graham Bloice ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev

Re: [Wireshark-dev] my purpose [for building with support for Lua in Linux (Ubuntu 20.04)]

2021-05-23 Thread Graham Bloice
On Sat, 22 May 2021 at 21:22, Vincent Randal wrote: > Graham, thank you for helping. I've replied in red below with a couple of > follow questions if you don't mind. > Thanks, Vincent Randal. > > On Sat, May 22, 2021 at 3:25 AM Graham Bloice > wrote: > >> Some answe

Re: [Wireshark-dev] my purpose [for building with support for Lua in Linux (Ubuntu 20.04)]

2021-05-22 Thread Graham Bloice
Schmalzel, currently with > Rowan University) from 30 years suggested it to me. > > Also, Richard Sharpe has been tremendously helpful as I've struggled to > learn enough about ASN.1 to get my dissectors generated and working.

Re: [Wireshark-dev] Wireshark 3.4.5 is now available

2021-04-25 Thread Graham Bloice
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists

Re: [Wireshark-dev] Status label for issues

2021-04-23 Thread Graham Bloice
On Fri, 23 Apr 2021 at 15:43, Pascal Quantin wrote: > Hi Graham, > > 23 avr. 2021 16:39:16 Graham Bloice : > > > How will issues that aren't bugs be handled, e.g. enhancement requests? > > We already have an enhancement label. > Ah, I thought this was some different

Re: [Wireshark-dev] Status label for issues

2021-04-23 Thread Graham Bloice
eshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe -- Graham Bloice ___

Re: [Wireshark-dev] Rough consensus and quiet humming

2021-04-22 Thread Graham Bloice
In a covid pandemic, working from home world, no one can hear you hum. On Thu, 22 Apr 2021 at 08:43, Guy Harris wrote: > > https://twitter.com/MeghanEMorris/status/1382109954224521216/photo/1 > -- Graham Bloice ___

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

2021-04-16 Thread Graham Bloice
s lacking about adding and generating asn1 based dissectors, any help you can provide there would be gratefully received. > > Thank you, > Vincent Randal > > On Tue, Apr 13, 2021 at 9:46 AM Graham Bloice > wrote: > >> Just to reset what I think are some misconceptions h

Re: [Wireshark-dev] (1) building Wireshark in build.wireshark fails, (2) how to get dissector details without packet

2021-04-15 Thread Graham Bloice
On Thu, 15 Apr 2021 at 21:23, Guy Harris wrote: > On Apr 15, 2021, at 2:03 AM, Graham Bloice > wrote: > > > Wireshark is a complicated project to build. You can follow the tested > way, as shown in the Developers Guide, which is essentially what our > Continuous Integra

Re: [Wireshark-dev] (1) building Wireshark in build.wireshark fails, (2) how to get dissector details without packet

2021-04-15 Thread Graham Bloice
nsubscribe > > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshar

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

2021-04-13 Thread Graham Bloice
Keyboard and brain got a little misconnected there. The first 2 sentences of item 3, which are missing some things I meant to fill in, can be replaced with the text from item 5. On Tue, 13 Apr 2021 at 16:45, Graham Bloice wrote: > Just to reset what I think are some misconceptions h

Re: [Wireshark-dev] How to build the simple ASN.1 UDP-based dissector example (foo)

2021-04-13 Thread Graham Bloice
ly, I need help building the generate_dissector-*proto* target >>> (Step #6 below). I'm certainly missing something here. >>> >>> >>> >>> >>> >>> (c) I created directory "foo" by extracting the attachment (foo.tgz) in

Re: [Wireshark-dev] general inquiry on building dissectors for wireshark-3.4.4

2021-04-07 Thread Graham Bloice
reading my question won't > understand what I'm after. > > I've watched numerous YouTube videos by Graham Bloice and Richard Sharpe > that describe 3 primary methods for Wireshark dissector development: > 1. Text based > 2. Scripting Language based > 3. C based > > In the me

Re: [Wireshark-dev] [Season of Docs] Congratulations on successfully completing your project

2021-03-31 Thread Graham Bloice
; > On Mon, Mar 15, 2021 at 07:03:12PM +0100, Alex Nik wrote: > > Thanks Graham. > > > > I actually have a topic to present now! <3 > > > > And I forgot to share some topic related art I was inspired by Wireshark > :D > > > > > > Regards,

Re: [Wireshark-dev] [Season of Docs] Congratulations on successfully completing your project

2021-03-15 Thread Graham Bloice
of Docs, > by writing a blog post or article. There are some useful logos and other > assets on the promotions and press page > <https://developers.google.com/season-of-docs/docs/2020/press>. > > If you have any questions about the program, please email

Re: [Wireshark-dev] Time to update to Npcap 1.20

2021-03-12 Thread Graham Bloice
s, sometimes the fixes for bugs have introduced even worse issues. As we've just released maintenance versions we do have a 6 week or so soak period. -- Graham Bloice ___ Sent via:Wireshark-dev mailing list Archive

[Wireshark-dev] MSVC build errors

2021-03-09 Thread Graham Bloice
compiler intrinsics though, so I'm not sure what's going on. -- Graham Bloice ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman

Re: [Wireshark-dev] OID not implemented

2021-02-26 Thread Graham Bloice
> Enterprise ID. > > Which then further mystifies me as to why the ITU has .2.4.2 and .2.4.5 allocated as children of 29. > On Fri, Feb 26, 2021 at 11:20 AM Graham Bloice < > graham.blo...@trihedral.com> wrote: > >> Well now I'm embarrassed, I'd fat fingered t

Re: [Wireshark-dev] OID not implemented

2021-02-26 Thread Graham Bloice
), 5 (OCSP > Response) */ > register_ber_oid_dissector("1.3.6.1.4.1.11129.2.4.2", > dissect_tls_sct_ber, proto_ssl, "SignedCertificateTimestampList"); > register_ber_oid_dissector("1.3.6.1.4.1.11129.2.4.5", > dissect_tls_sct_ber, proto_ssl, "SignedCertifi

Re: [Wireshark-dev] OID not implemented

2021-02-26 Thread Graham Bloice
vel 4 | AMP Tower | 29 Customs Street West | Auckland > CBD I Auckland 1010 I New Zealand > > www.kapsch.net/au/en | www.kapsch.net > NZBN 9429033760506 I Registered office Auckland > > > > *Please consider the environment before printing this e-mail.* > > > --

Re: [Wireshark-dev] Adding personal repository remote

2021-02-07 Thread Graham Bloice
y take some time depending on the speed of your internet > connection. You can adjust this using git remote: git remote rename origin upstream > Thanks and regards...Paul > > -- > > Paul Offord > -- Graham Bloice

[Wireshark-dev] Missing Wiki page on Gitlab

2021-02-03 Thread Graham Bloice
No idea if it got transferred and has subsequently been deleted or failed to transfer but the old wiki page on ExpertInfo ( https://wiki.wireshark.org/Development/ExpertInfo) doesn't seem to be present in the Gitlab version. -- Graham Bloice

Re: [Wireshark-dev] Documentation : 9.6. How to produce protocol stats merge request

2020-12-24 Thread Graham Bloice
dentifiers. The build system > has to take care of this, the Windows one is especially finicky about the > details. > > > 6) __declspec(dllexport) void plugin_register_tap_listener(void) is never > called > Solution ? : > - remove it > - call directly register_foo_stat_trees();

Re: [Wireshark-dev] How to properly finalize capture in a Wireshark extcap plugin?

2020-11-24 Thread Graham Bloice
pcapng specification, this can be done either via the > "epb_dropcount" option in the Enhanced Packet Block or via the "isb_ifdrop" > or " isb_osdrop" options in the Interface Statistics bl

Re: [Wireshark-dev] wireshark capture/filtering question

2020-11-20 Thread Graham Bloice
s some source files to > study, that would be helpful too. I've only implemented a few packet > dissector plugins for various avionics protocols, not gone this deep into > the internals. > > > > Thanks, > > John D. > > > Hi John, To clarif

Re: [Wireshark-dev] Windows update on development version

2020-11-20 Thread Graham Bloice
tice is taken if it's a custom build or a regular release. The check can be disabled with the gui.update.enabled setting if you wish and the reference version can be set to development with gui.update.channel. -- Graham Bloice ___ Sen

Re: [Wireshark-dev] Tshark closing unexpectedly due to failure reading from file

2020-11-19 Thread Graham Bloice
cess B's read should see it, as long as the read is done after the write. >> >> flush() just means "do a write to the underlying file immediately"; it >> doesn't imply anything more than write() on UN*X or _write() on Windows >> (which, in t

Re: [Wireshark-dev] question regarding merge request workflow

2020-11-11 Thread Graham Bloice
> https://gitlab.com/wireshark/wireshark/-/wikis/Development/SubmittingPatches#the-review-process > -- > Security Engineer/wireshark maintainer, SUSE Software Solutions Germany > GmbH, Maxfeldstr. 5, 90409 Nürnberg, GF: Felix Imendörffer (HRB 36809, > AG Nürnberg) > > -- Graham Bloice

Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on Windows

2020-11-02 Thread Graham Bloice
On Mon, 2 Nov 2020 at 16:34, John Dill wrote: > > >Message: 2 > >Date: Mon, 2 Nov 2020 16:04:21 + > >From: Graham Bloice > >To: Developer support list for Wireshark > >Subject: Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on

Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on Windows

2020-11-02 Thread Graham Bloice
On Mon, 2 Nov 2020 at 15:06, Maynard, Chris via Wireshark-dev < wireshark-dev@wireshark.org> wrote: > > -Original Message- > > From: Wireshark-dev On Behalf Of > > Gerald Combs > > Sent: Sunday, November 1, 2020 8:36 PM > > To: Developer support li

Re: [Wireshark-dev] Building Wireshark 3.4.0 documentation on Windows

2020-11-01 Thread Graham Bloice
CMake generation step could check minimum requirements. > - Chris > [1]: *https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html* > <https://www.wireshark.org/docs/wsdg_html_chunked/ChSetupWin32.html> > > > -- Graham Bloice

Re: [Wireshark-dev] Trouble uploading Wireshark enhancement

2020-10-23 Thread Graham Bloice
anges added to commit > [fhew@localhost wireshark-working]$ git push downstream HEAD > fatal: 'downstream' does not appear to be a git repository > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > an

Re: [Wireshark-dev] lua decoder accessing info from layers above

2020-10-16 Thread Graham Bloice
ccordingly, > and it's shorter, cleaner, and more obvious. > > - > > Now the next question is: > Can I submit this Lua based dissector for inclusion in the Wireshark > project, or > should I rewrite it as a 'C' based dissector, and submit that? > > Currently we do

Re: [Wireshark-dev] Possible bug (Wireshark blocking VPN traffic)

2020-10-05 Thread Graham Bloice
as this, by its nature, is installed into the network stack could possibly have odd effects. To progress the problem you should raise an issue at the npcap github issues tracker (https://github.com/nmap/npcap/issues), I think there have been previous reports of VPN issues so check the list before

Re: [Wireshark-dev] Joint project with Git for outreachy

2020-09-21 Thread Graham Bloice
elp. > > > There's also the Wireshark Developers Guide ( https://www.wireshark.org/docs/wsdg_html_chunked/) and for those that are sleep deprived there are a selection of talks on dissectors from previous SharkFest conferences, e.g. Writing a Wireshark dissector: https://www.youtube.com/watch

Re: [Wireshark-dev] Gitlab doesn't show all epan/dissectors/ files.

2020-09-11 Thread Graham Bloice
that won't fix the issue. > On Wed, 9 Sep 2020 at 23:50, chuck c wrote: > >> It's not all bad. I've gotten much better at navigating the code using >> VSCode since the migration. >> :-) >> >> >> On Wed, Sep 9, 2020 at 4:27 PM Graham Bloice >> wrote:

Re: [Wireshark-dev] Gitlab doesn't show all epan/dissectors/ files.

2020-09-09 Thread Graham Bloice
same directory I get a message: Sorry, we had to truncate this directory to 1,000 files. 933 entries were omitted from the list. I guess this is an issue where others host for us, they are limiting resource intensive ops, such as the Gitlab diff restriction. -- Graham Bloice __

Re: [Wireshark-dev] Winflexbison update in choco

2020-09-02 Thread Graham Bloice
ds by setting LEX_ and YACC_EXECUTABLE in cmake, but I > don't know whether this is the correct fix or not. > Dario. > > Either delete CMakeCache.txt (to discover all required libs etc. again), or edit it to remove the invalid path references and then CMake will search and find

Re: [Wireshark-dev] wireshark-bugs for gitlab issues ?

2020-08-26 Thread Graham Bloice
bscribe/Unsubscribe/Options > Local archives (no longer provided after December 31, 2016) > MARC archives > The Mail Archive > > GitLab has options for notifications under your profile: https://gitlab.com/profile/notifications Setting a custom notification

Re: [Wireshark-dev] Cherry-picking, gitlab permissions

2020-08-26 Thread Graham Bloice
ter" level of permission seems to include >> only things that previously people could get by registering for Bugzilla, >> and some other features that people used to be able to do seem at the >> "Developer" level (though that also includes some higher level permissions &g

Re: [Wireshark-dev] Gitlab wiki search

2020-08-23 Thread Graham Bloice
:20 AM, chuck c wrote: > > > https://stackoverflow.com/questions/55827354/github-repository-not-listing-in-google-search-no-way-to-submit-url > > > > > https://search.google.com/search-console/about > > > > Is there is a "wiki-master" to do the Google se

Re: [Wireshark-dev] Gitlab wiki search

2020-08-22 Thread Graham Bloice
; and a bunch of links to things other than what I'm looking for. On Sat, 22 Aug 2020 at 16:46, Jaap Keuter wrote: > Indeed it’s a bit coarse. It seems improvements are planned, see > https://docs.gitlab.com/ee/user/project/wiki/#customizing-sidebar, not > sure what that will bring. > &

[Wireshark-dev] Gitlab wiki search

2020-08-22 Thread Graham Bloice
to click the "bubble" for Wikis to see the 12 results all of which show diffs of the markdown but does actually have the page I want. IMHO not really a wiki. -- Graham Bloice ___ Sent via:Wireshark-dev ma

Re: [Wireshark-dev] TDS : TLS Exchange

2020-08-14 Thread Graham Bloice
t; Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ..

Re: [Wireshark-dev] Filtering on a field when there is more than one such field in a Wi-Fi packet

2020-08-14 Thread Graham Bloice
___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wire

Re: [Wireshark-dev] GitLab update and migration timeline

2020-08-01 Thread Graham Bloice
ing > purposes. > > * August 23. Migrate the main repository bugs/issues, aka The Big Switch. > > * Unscheduled. Release and fuzz builder migration. > > The main repository + bug/issue migration will require a fair amount of > downtime, so I scheduled it for a Sun

Re: [Wireshark-dev] Why tvb_get_bits() assumes Big Endian?

2020-07-30 Thread Graham Bloice
I forgot to add: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4478 On Thu, 30 Jul 2020 at 09:22, Graham Bloice wrote: > Personally, I would argue that when the bits aren't in order then they > aren't bits in an octet array, instead they are bits in words, or longs or > l

Re: [Wireshark-dev] Why tvb_get_bits() assumes Big Endian?

2020-07-30 Thread Graham Bloice
> > That would be my reasoning against it > > Having the function take quite important parameter (encoding) and not > using it at all is pretty bad. When someone tries to use > tvb_get_bits() with ENC_LITTLE_ENDIAN

Re: [Wireshark-dev] Code Coverage Measurement of Wireshark - Outdated Instruction

2020-07-29 Thread Graham Bloice
or your help. > > > Best regards, > > Jannis Peimann > > > _______ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https

Re: [Wireshark-dev] Version of Qt required?

2020-07-07 Thread Graham Bloice
appears to be 5.6.2. >> >> Looking at CMakeLists.txt, there are various checks for Qt5Widgets, but >> the earliest supported version looks like 5.3? >> >> I think https://doc.qt.io/qt-5/qtglobal.html#qAsConst was introduced >> in 5.7. >> Do we want

Re: [Wireshark-dev] Intermittent Builder Windows Petri Dish x64 failed (failed ctest) failures seriously annoying.

2020-07-02 Thread Graham Bloice
e host to see if it's suffering. > > On Thu, Jul 2, 2020 at 4:51 PM Graham Bloice > wrote: > >> The decryption test might need a bigger timeout, currently at 600 seconds: >> >> 9/34 Test #3: suite_decryption ...***Timeout 630.47 sec >> >&g

Re: [Wireshark-dev] Intermittent Builder Windows Petri Dish x64 failed (failed ctest) failures seriously annoying.

2020-07-02 Thread Graham Bloice
ent false petri dish failures. Can someone with insight > into the tests have a look? > > Best regards > > Anders > > Example Builder Windows Petri Dish x64 failed (failed ctest) - > http://buildbot.wireshark.org/petri-dish/builders/Windows%20Petri%20Dish%

Re: [Wireshark-dev] First patch submission (extcap install flags for silent mode)

2020-05-12 Thread Graham Bloice
her resource for general info about submissions can be found on the Wiki: https://wiki.wireshark.org/Development/SubmittingPatches And answers to your questions: 1. Go ahead. 2. Seems a good idea. 3. Yep, separate change. -- Graham Bloice ___

Re: [Wireshark-dev] Issue Report - Latest Version

2020-04-28 Thread Graham Bloice
1. Uninstall npcap and then install the older (and unsupported) WinPcap that Wireshark is still able to use 2. Work with the npcap support folks to report and hopefully fix the issue: https://github.com/nmap/nmap/issues/ -- Graham Bloice __

Re: [Wireshark-dev] macOS build broken

2020-04-24 Thread Graham Bloice
On Fri, 24 Apr 2020 at 17:22, Lori Jakab wrote: > On Fri, Apr 24, 2020 at 6:06 PM Graham Bloice > wrote: > >> The macOS build slave is coping, according to the CMake output it's using: >> >> -- The C compiler identification is AppleClang 11.0.0.1133 >> -

Re: [Wireshark-dev] macOS build broken

2020-04-24 Thread Graham Bloice
null' if the pointer should never be null >>> fpos_t (* _Nullable)(void *, fpos_t, int), >>>^ >>> _Nonnull >>> /Library/Developer/CommandLineTools/SDKs/Ma

[Wireshark-dev] LUA API docs missing?

2020-04-09 Thread Graham Bloice
The LUA API seems to have gone missing from the on-line Developers Guide. Links to it such as found at https://wiki.wireshark.org/LuaAPI i.e. https://www.wireshark.org/docs/wsdg_html_chunked/wsluarm_modules.html are retunring a 404. -- Graham Bloice

Re: [Wireshark-dev] Wireshark col_append_sep_str function

2020-04-03 Thread Graham Bloice
is writing again PDU Protocol. > > Do you guys know what I’m missing? > > > > Thanks for your help. > > > > > > Mit freundlichen Grüßen/Best regards, > > > > *Jannis Peimann* > > > Look for col_set_fence in README.dissector -- Graham Bloice __

Re: [Wireshark-dev] ask.wireshark.org RSS feed

2020-04-02 Thread Graham Bloice
On Thu, 2 Apr 2020 at 09:54, Graham Bloice wrote: > > > On Wed, 1 Apr 2020 at 23:38, Jeff Morriss > wrote: > >> >> >> On Wed, Apr 1, 2020 at 5:57 PM Maynard, Chris via Wireshark-dev < >> wireshark-dev@wireshark.org> wrote: >> >>> I d

Re: [Wireshark-dev] ask.wireshark.org RSS feed

2020-04-02 Thread Graham Bloice
On Wed, 1 Apr 2020 at 23:38, Jeff Morriss wrote: > > > On Wed, Apr 1, 2020 at 5:57 PM Maynard, Chris via Wireshark-dev < > wireshark-dev@wireshark.org> wrote: > >> I don’t seem to be receiving any messages for ask.wireshark.org via the >> RSS feed anymore. Am I the only one who seems affected

Re: [Wireshark-dev] Problem in 'packet-f5ethtrailer.c'

2020-03-19 Thread Graham Bloice
As a counterpoint, I compiled today with the latest VS2019, no issue at all. From vswhere, the version is VisualStudio.16.Release/16.5.0+29911.84, so slightly newer than your version. I do only build x64 though, not x86. -- Graham Bloice _

Re: [Wireshark-dev] Problem in 'packet-f5ethtrailer.c'

2020-03-19 Thread Graham Bloice
ex.php/GitFaq#Why_isn.27t_Git_preserving_modification_time_on_files.3F -- Graham Bloice ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshar

Re: [Wireshark-dev] Cmake on windows

2020-03-06 Thread Graham Bloice
s/wireshark-dev >>> mailto:wireshark-dev-requ...@wireshark.org >>> ?subject=unsubscribe >> >> >> >> -- >> >> Naima is online. >> >> >> ___

Re: [Wireshark-dev] Wireshark 3.2.2 Windows Installer 64-bit - Invalid Signature

2020-03-06 Thread Graham Bloice
staller, select "Properties", and make sure it's signed by > "Wireshark Foundation, Inc.". You can also do this on the command line > using `signtool verify` if it's available. > > Or use the PowerShell cmdlet "Get-AuthenticodeSignature", passing the path to the file

Re: [Wireshark-dev] Lua dissector question

2020-02-13 Thread Graham Bloice
("Device Status", > "status.device_status", ftypes.UINT32) > ... > tree:add(device_status, tvbuf:range(4,4)) > > How can I fix this? > > Regards, > Juanjo Martin > > The endianess is set w

Re: [Wireshark-dev] Unable to detect custom protocol dissector

2020-02-13 Thread Graham Bloice
t; How can I get wireshark to detect the GeoNetworking protocol from my > custom Lua script? > > Thanks in advance. > > > -- Graham Bloice ___ Sent via:Wireshark-dev mailing list Archives:https://

Re: [Wireshark-dev] Qt availability changes

2020-01-28 Thread Graham Bloice
t;suitable" version for a while and then periodically, e.g. major releases, updating to the current latest. It's too much work to track latest with the potential for introducing new bugs. In summary this will have the opposite effect to that which Qt expects. -- Graham Bloice _

Re: [Wireshark-dev] Qt availability changes

2020-01-27 Thread Graham Bloice
CURRENT release is going to make things better. As folks noted in the thread you linked to, how will CI systems handle this? -- Graham Bloice ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/l

Re: [Wireshark-dev] Support Opus in WireShark

2020-01-19 Thread Graham Bloice
know how to realize it. > > > It is my first time to participate in a open source project. And I want to > make a contribution. I don't know whether it is a good way to plugin Opus > into WireShark or not. If not , is there a better way? I want to know and > try it! > > >

Re: [Wireshark-dev] Standard defined field names in Wireshark dissectors

2020-01-05 Thread Graham Bloice
ń > While I think it is helpful to try to follow specification names, sometimes they are too awkward. However, I'm cautious about renaming fields "just because" as this will likely break any scripts\workflows folks have that

Re: [Wireshark-dev] Updating to the latest version of python with choco causes a failure

2019-12-11 Thread Graham Bloice
I did with Python 3.8.0? > Python 3.8 installed via choco works for me. Did you fix up or delete your CMakeCache.txt file from a previous python version? -- Graham Bloice ___ Sent via:Wireshark-dev mailing

Re: [Wireshark-dev] First experience with Visual Studio 2019

2019-12-07 Thread Graham Bloice
from your > system. Any unauthorized reading, distribution, copying, or other use of > this message or its attachments is strictly prohibited. > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https:/

Re: [Wireshark-dev] Visual studio 2019 from choco

2019-11-26 Thread Graham Bloice
On Tue, 26 Nov 2019 at 16:48, Graham Bloice wrote: > > > On Tue, 26 Nov 2019 at 15:42, Dario Lombardo wrote: > >> >> >> On Tue, Nov 26, 2019 at 3:50 PM Graham Bloice < >> graham.blo...@trihedral.com> wrote: >> >>> >>> >

Re: [Wireshark-dev] Visual studio 2019 from choco

2019-11-26 Thread Graham Bloice
On Tue, 26 Nov 2019 at 15:42, Dario Lombardo wrote: > > > On Tue, Nov 26, 2019 at 3:50 PM Graham Bloice > wrote: > >> >> >> On Tue, 26 Nov 2019 at 14:29, Dario Lombardo wrote: >> >>> I'm chatting with choco maintainers right now. They say it

Re: [Wireshark-dev] Visual studio 2019 from choco

2019-11-26 Thread Graham Bloice
Windows 7 SP1 > > 1607 being the anniversary edition > " > > I'm trying to make my system up2date and then install dotnet. if I > succeed, I'll drop a line in the documentation about installing on an > updated windows version, or a more detailed description of the issue. > >

Re: [Wireshark-dev] Visual studio 2019 from choco

2019-11-26 Thread Graham Bloice
/install/on-windows-10 The choco package "dotnetfx" will install this: https://chocolatey.org/packages/dotnetfx Arguably it should be a dependency for the VS choco packages, and it is listed for the VS 2019 community package.

Re: [Wireshark-dev] G729 Wiki page

2019-11-16 Thread Graham Bloice
ow. > When it will be accepted, the G.729 Wiki page will be obsolete by my > opinion. > > https://code.wireshark.org/review/35105 > > > Can you update the Wiki page when that occurs? -- Graham Bloice ___ Sent via:

[Wireshark-dev] G729 Wiki page

2019-11-14 Thread Graham Bloice
https://wiki.wireshark.org/HowToDecodeG729 Does this need an update, I think we have G729 built-in? -- Graham Bloice ___ Sent via:Wireshark-dev mailing list Archives:https://www.wireshark.org/lists/wireshark-dev

Re: [Wireshark-dev] Building on Windows

2019-11-13 Thread Graham Bloice
On Wed, 13 Nov 2019 at 17:36, Richard Sharpe wrote: > On Wed, Nov 13, 2019 at 9:30 AM Graham Bloice > wrote: > > Normally (as in the half dozen or so systems I have checked on) you > would have: > > > > 07/10/2019 10:1813 Microsoft.VCRedistVersion.def

Re: [Wireshark-dev] Building on Windows

2019-11-13 Thread Graham Bloice
On Wed, 13 Nov 2019 at 17:24, Richard Sharpe wrote: > On Wed, Nov 13, 2019 at 9:11 AM Graham Bloice > wrote: > > > > > > On Wed, 13 Nov 2019 at 16:52, Richard Sharpe < > realrichardsha...@gmail.com> wrote: > >> > >> On Wed, Nov 13, 2019 at 8:45

  1   2   3   4   5   6   7   8   9   10   >