[Wireshark-dev] On MR 4428

2021-10-06 Thread Jaap Keuter 
Hi,

Looking at MR 4428 https://gitlab.com/wireshark/wireshark/-/merge_requests/4428 
(cherry picked from commit 96cfaf67) it introduces a new symbol in the wiretap 
11 library (wtap_uses_lua_filehandler). The debian symbols file contains the 
addition of "wtap_uses_lua_filehandler@Base 3.5.1", which refers to a later 
version (3.5.1) than this release is of (3.4.x). I could see this being a 
problem somewhere. Maybe we need to reconsider inclusion of the MR in 
release-3.4

Thanks,
Jaap___
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

Re: [Wireshark-dev] On MR 4428

2021-10-06 Thread Stig Bjørlykke 
On Wed, Oct 6, 2021 at 12:58 PM Jaap Keuter  wrote:

> Looking at MR 4428
>  (cherry
> picked from commit 96cfaf67
> )
> it introduces a new symbol in the wiretap 11 library
> (wtap_uses_lua_filehandler). The debian symbols file contains the addition
> of "wtap_uses_lua_filehandler@Base 3.5.1", which refers to a later
> version (3.5.1) than this release is of (3.4.x). I could see this being a
> problem somewhere. Maybe we need to reconsider inclusion of the MR in
> release-3.4
>

This issue is already fixed in MR . Maybe we should add a sanity check
to the Debian builder?


-- 
Stig Bjørlykke
___
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

Re: [Wireshark-dev] 3.6.0 release schedule

2021-10-06 Thread Jaap Keuter 
Hi,

Are those wmem / pinfo->pool changes completed? Would be nice if that was 
consistent before branching. Is dfilter stabilised already? These are the 
things that come to mind.

Thanks,
Jaap

> On 30 Sep 2021, at 23:29, Gerald Combs  wrote:
> 
> Hi all,
> 
> I have the 3.5.1 release scheduled for next Thursday, October 7, but I'm 
> wondering if we shouldn't create the 3.6 branch and release 3.6.0rc1 instead. 
> Unless anyone needs to delay the 3.6 branch I plan on doing the following:
> 
> Oct  6 : Release 3.4.9 & 3.2.17
> Oct  7 : Create the release-3.6 branch
> Oct  8 : Release 3.6.0rc1
> Oct 20 : Release 3.6.0 and wind down the 3.2 branch
> Nov 17 : Release 3.6.1 & 3.4.10

___
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

[Wireshark-dev] Wireshark 3.4.9 is now available

2021-10-06 Thread Gerald Combs 

I'm proud to announce the release of Wireshark 3.4.9.


 What is Wireshark?

  Wireshark is the world’s most popular network protocol analyzer. It is
  used for troubleshooting, analysis, development and education.

 What’s New

  Bug Fixes

   The following bugs have been fixed:

 • TShark PDML output embeds "proto" elements within other "proto"
   elements Issue 10588[1].

 • Filter expressions comparing against single-octet hex strings
   where the hex digit string equals a protocol name don’t work
   Issue 12810[2].

 • AMQP 0.9: dissector fails to handle Content-Body frame split
   across TCP packets Issue 14217[3].

 • IEEE 802.15.4: Missing check on "PAN ID Present" bit of the
   Multipurpose Frame Control field Issue 17496[4].

 • Wireshark ignored some character in filename when exporting SMB
   objects. Issue 17530[5].

 • tshark -z credentials: assertion failed: (allocator→in_scope)
   Issue 17576[6].

 • IS-IS Extended IP Reachability Prefix-SID not decoded properly
   Issue 17610[7].

 • Error when reloading lua plugins with a capture file loaded via a
   custom lua file handler Issue 17615[8].

 • Absolute time UTC field filters are constructed incorrectly,
   don’t match the packet Issue 17617[9].

 • GUI freezes when clicking on large (non-capture) file in File
   chooser Issue 17620[10].

 • Crash after selecting a different profile while capturing Issue
   17622[11].

 • BT-DHT reports malformed packets that are actually uTP on same
   connection Issue 17626[12].

  New and Updated Features

  New Protocol Support

   There are no new protocols in this release.

  Updated Protocol Support

   AMQP, Aruba IAP, BGP, BT-DHT, CoAP, DCERPC SPOOLSS, Diameter, EPL,
   GSM A-bis OML, GSM A-I/F COMMON, GSM SIM, IEEE 1905.1a, IEEE
   802.15.4, IMAP, InfiniBand, ISIS LSP, ISObus VT, JPEG, MP2T,
   NORDIC_BLE, QUIC, RTCP, SDP, SMB, TWAMP-Control, USB HID, and VSS
   Monitoring

  New and Updated Capture File Support

   CAM Inspector, Ixia IxVeriWave, pcapng, and USBDump

 Getting Wireshark

  Wireshark source code and installation packages are available from
  https://www.wireshark.org/download.html.

  Vendor-supplied Packages

   Most Linux and Unix vendors supply their own Wireshark packages. You
   can usually install or upgrade Wireshark using the package management
   system specific to that platform. A list of third-party packages can
   be found on the download page[13] on the Wireshark web site.

 File Locations

  Wireshark and TShark look in several different locations for
  preference files, plugins, SNMP MIBS, and RADIUS dictionaries. These
  locations vary from platform to platform. You can use About → Folders
  to find the default locations on your system.

 Getting Help

  The User’s Guide, manual pages and various other documentation can be
  found at https://www.wireshark.org/docs/

  Community support is available on Wireshark’s Q site[14] and on the
  wireshark-users mailing list. Subscription information and archives
  for all of Wireshark’s mailing lists can be found on the web site[15].

  Issues and feature requests can be reported on the issue tracker[16].

 Frequently Asked Questions

  A complete FAQ is available on the Wireshark web site[17].

  Last updated 2021-10-06 17:20:36 UTC

 References

   1. https://gitlab.com/wireshark/wireshark/-/issues/10588
   2. https://gitlab.com/wireshark/wireshark/-/issues/12810
   3. https://gitlab.com/wireshark/wireshark/-/issues/14217
   4. https://gitlab.com/wireshark/wireshark/-/issues/17496
   5. https://gitlab.com/wireshark/wireshark/-/issues/17530
   6. https://gitlab.com/wireshark/wireshark/-/issues/17576
   7. https://gitlab.com/wireshark/wireshark/-/issues/17610
   8. https://gitlab.com/wireshark/wireshark/-/issues/17615
   9. https://gitlab.com/wireshark/wireshark/-/issues/17617
  10. https://gitlab.com/wireshark/wireshark/-/issues/17620
  11. https://gitlab.com/wireshark/wireshark/-/issues/17622
  12. https://gitlab.com/wireshark/wireshark/-/issues/17626
  13. https://www.wireshark.org/download.html#thirdparty
  14. https://ask.wireshark.org/
  15. https://www.wireshark.org/lists/
  16. https://gitlab.com/wireshark/wireshark/-/issues
  17. https://www.wireshark.org/faq.html


Digests

wireshark-3.4.9.tar.xz: 32335284 bytes
SHA256(wireshark-3.4.9.tar.xz)=c6525e829bd24525ee699aa207ecd27c50646d64263a669671badfb71cd99620
RIPEMD160(wireshark-3.4.9.tar.xz)=7fd30ef3b906fa2301b6a77bd4623633d0b46f23
SHA1(wireshark-3.4.9.tar.xz)=0ed390387d9d6201cdd6364e782cb58c8ad4d9ce

Wireshark-win32-3.4.9.exe: 55411320 bytes
SHA256(Wireshark-win32-3.4.9.exe)=c48ccab1dd950582071d885d89881b201aac505163f190c253ab3b9ea2666118
RIPEMD160(Wireshark-win32-3.4.9.exe)=e625c52faa448a6bf0fbfac97371001a4bc2cf3b
SHA1(Wireshark-win32-3.4.9.exe)=1fe4a6091f89151079799185de3a25e575079796

Wireshark-win64-3.4.9.exe: 71374760 bytes

Re: [Wireshark-dev] 3.6.0 release schedule

2021-10-06 Thread Evan Huus 
On Wed., Oct. 6, 2021, 14:43 Jaap Keuter,  wrote:

> Hi,
>
> Are those wmem / pinfo->pool changes completed? Would be nice if that was
> consistent before branching.


I have three things left on my list:
- a few last changes in to_str macros - small and easy
- figure out what to do with valuestrings - hard and undefined
- convert remaining dissectors - trivial but large

The last two aren't worth waiting for as they will both require some
investment. The first one I'll try to get to soon, but should be
self-explanatory based on my recent merges if somebody else wants to grab
it today.

Evan

Is dfilter stabilised already? These are the things that come to mind.
>
> Thanks,
> Jaap
>
> > On 30 Sep 2021, at 23:29, Gerald Combs  wrote:
> >
> > Hi all,
> >
> > I have the 3.5.1 release scheduled for next Thursday, October 7, but I'm
> wondering if we shouldn't create the 3.6 branch and release 3.6.0rc1
> instead. Unless anyone needs to delay the 3.6 branch I plan on doing the
> following:
> >
> > Oct  6 : Release 3.4.9 & 3.2.17
> > Oct  7 : Create the release-3.6 branch
> > Oct  8 : Release 3.6.0rc1
> > Oct 20 : Release 3.6.0 and wind down the 3.2 branch
> > Nov 17 : Release 3.6.1 & 3.4.10
>
> ___
> 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
>
___
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

[Wireshark-dev] Does this apply to 3.2 too?

2021-10-06 Thread Jaap Keuter 
Hi,

When building release-3.2 I'm greeted by a stream of warnings from CMake first, 
like these:


-- Configuring done 

CMake Warning (dev) in CMakeLists.txt:  

Policy CMP0071 is not set: Let AUTOMOC and AUTOUIC process GENERATED files. 
  
Run "cmake --help-policy CMP0071" for policy details.  Use the cmake_policy 
  
command to set the policy and suppress this warning.
  

For compatibility, CMake is excluding the GENERATED source file(s): 
  

"/master-3.2/build/tshark-tap-register.c"   


from processing by AUTOMOC and AUTOUIC.



It seems that MR 3140 
https://gitlab.com/wireshark/wireshark/-/merge_requests/3140 was introduced for 
to quell that stream in release-3.4. What could be the reason this is not 
applicable to master-3.2 too? Minimum supported Qt version, or CMake version 
which cannot handle this? I'm not familiar enough with these subjects to know 
what constraints there are, so don't want to mess things up with a MR just yet.

Thanks,
Jaap___
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