Wireshark · Wireshark-users: [Wireshark-users] Wireshark 4.4.9 is now available

Wireshark-users: [Wireshark-users] Wireshark 4.4.9 is now available

From: Gerald Combs <gerald@xxxxxxxxxxxxx>

Date: Thu, 28 Aug 2025 16:00:34 -0700

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

What is Wireshark?

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

Wireshark is hosted by the Wireshark Foundation, a nonprofit which
promotes protocol analysis education. Wireshark and the foundation
depend on your contributions in order to do their work! If you or your
organization would like to contribute or become a sponsor, please
visit wiresharkfoundation.org[1].

What’s New

Bug Fixes

The following bugs have been fixed:

• RDM Product Detail List ID Disect incorrect. Issue 20612[2].

• SCCP LUDT segmentation decoding fails. Issue 20647[3].

• Ciscodump fails to start capture on Cisco IOS. Issue 20655[4].

• [BACnet] WritePropertyMultiple closing context tag 1 not showing.
Issue 20665[5].

• Bug in LZ77 decoder; reads a 16-bit length when it should read a
32-bit length. Issue 20671[6].

New and Updated Features

New Protocol Support

There are no new protocols in this release.

Updated Protocol Support

BACapp, LIN, MySQL, RDM, SABP, SCCP, sFlow, and SSH

New and Updated Capture File Support

There is no new or updated capture file support in this release.

Updated File Format Decoding Support

There is no updated file format support in this release.

Prior Versions

Wireshark 4.4.8 included the following changes. See the release
notes[7] for details:

• Renegotiated DTLS session is not being decrypted. Issue 20362[8].

• Wireshark is completely stuck in initialization because
androiddump recv() is blocked. Issue 20526[9].

• Fuzz job UTF-8 encoding issue: fuzz-2025-06-20-7318.pcap. Issue
20585[10].

• Crash when showing packet in new window after reloading Lua
plugins with a certain gui.column.format preference. Issue
20588[11].

• Bug in UDS dissector with Service ReadDataByPeriodicIdentifier
Response. Issue 20589[12].

• Packet diagram doesn’t show non-standard field value
representations. Issue 20590[13].

• Packet diagram shows representation twice when field type is
FT_NONE. Issue 20601[14].

• application/x-www-form-urlencoded key parsed incorrectly following
a name-value byte sequence with no '=' Issue 20615[15].

• DNP3 time stamp was unable to work after epoch time(year 2038)
Issue 20618[16].

Wireshark 4.4.7 included the following changes. See the release
notes[17] for details:

• wnpa-sec-2025-02[18] Dissection engine crash. Issue 20509[19].
CVE-2025-5601[20].

• Wireshark does not correctly decode LIN "go to sleep" in TECMP and
CMP. Issue 20463[21].

• Dissector bug, Protocol CIGI. Issue 20496[22].

• Green power packets are not dissected when proto_version ==
ZBEE_VERSION_GREEN_POWER. Issue 20497[23].

• Packet diagrams misalign or drop bitfields. Issue 20507[24].

• Corruption when setting heuristic dissector table UI name from
Lua. Issue 20523[25].

• LDAP dissector incorrectly displays filters with singleton "&"
Issue 20527[26].

• WebSocket per-message compression extentions: fail to decompress
server messages (from the 2nd) due to parameter handling. Issue
20531[27].

• The LL_PERIODIC_SYNC_WR_IND packet is not properly dissected
(packet-btle.c) Issue 20554[28].

Wireshark 4.4.6 included the following changes. See the release
notes[29] for details:

• Bug in EtherCAT dissector with ECS order. Issue 13718[30].

• Conversation dialog columns return to default width on each new
packet in live capture. Issue 15978[31].

• Tests fail in LTO-enabled builds in Ubuntu/Debian. Issue
18216[32].

• Incorrect conditions in BFCP dissector. Issue 18717[33].

• Static build fails on Ubuntu 24.04 because the c-ares library
isn’t found. Issue 20343[34].

• Flutter’s Image Picker Generated JPEG Files Detected as Malformed
Packet. Issue 20355[35].

• QUIC dissector breaks when src and dst change. Issue 20371[36].

• s390x: build fail on Ubuntu PPA nighty build. Issue 20372[37].

• Trailing octet after IPv4 packet end is not detected or displayed
in raw bytes. Issue 20423[38].

• [packet-ax25-nol3.c] Only call APRS dissector on UI Frames. Issue
20429[39].

• Wireshark hangs when refreshing interfaces with the debug console
preference set to "always" and a file open (Windows) Issue
20434[40].

• BGP EVPN - Type-8 route not correctly read after addition of Max.
Response Time field. Issue 20459[41].

• Wireshark does not correctly decode LIN "go to sleep" in TECMP and
CMP. Issue 20463[42].

• MQTT-SN: WILLTOPIC message not decoded correctly (missing some
flags) Issue 20476[43].

Wireshark 4.4.5 included the following changes. See the release
notes[44] for details:

• GRPC: protobuf_json only displays the truncated string value.
Issue 20392[45].

• Wireshark crashes when clicking on a column title/header. Issue
20403[46].

Wireshark 4.4.4 included the following changes. See the release
notes[47] for details:

• wnpa-sec-2025-01[48] Bundle Protocol and CBOR dissector
{crash,infinite loop,memory leak}. Issue 20373[49].

• Crash when sorting columns during capture with display filter
active. Issue 20263[50].

• OSS-Fuzz 384757274: Invalid-bool-value in dissect_tcp. Issue
20300[51].

• Test failure in 4.4.2/4.4.3: test_sharkd_req_follow_http2. Issue
20330[52].

• Regression in extcap interface toolbar. Issue 20354[53].

• Clicking outside columns in TCP tab of Statistics → Conversations
window causes crash. Issue 20357[54].

• FTBFS with Ubuntu development (25.04) release. Issue 20359[55].

• DNS enable_qname_stats crash Wireshark when QDCOUNT == 0. Issue
20367[56].

• Windows: Android extcap plugin fails with "Broken socket
connection" if there are no new packets for 2sec. Issue 20386[57].

• TECMP: Calculation of lifecycle start in Status message is wrong.
Issue 20387[58].

• MQTT v5.0 properties total length presentation is incorrect. Issue
20389[59].

• TShark doesn’t resolve addresses in custom "hosts" files. Issue
20391[60].

• Incorrect JA4 fingerprint with empty ciphers. Issue 20394[61].

Wireshark 4.4.3 included the following changes. See the release
notes[62] for details:

• Potential mis-match in GSM MAP dissector for uncertainty radius
and its filter key. Issue 20247[63].

• Macro eNodeB ID and Extended Macro eNodeB ID not decoded by User
Location Information. Issue 20276[64].

• The NFSv2 Dissector appears to be swapping Character Special File
and Directory in mode decoding. Issue 20290[65].

• CMake discovers Strawberry Perl’s zlib DLL when it shouldn’t.
Issue 20304[66].

• VOIP Calls call flow displaying hours. Issue 20311[67].

• Fuzz job issue: fuzz-2024-12-26-7898.pcap. Issue 20313[68].

• sFlow: Incorrect length passed to header sample dissector. Issue
20320[69].

• wsutil: Should link against -lm due to missing fabs() when built
with -fno-builtin. Issue 20326[70].

Wireshark 4.4.2 included the following changes. See the release
notes[71] for details:

• wnpa-sec-2024-14[72] FiveCo RAP dissector infinite loop. Issue
20176[73].

• wnpa-sec-2024-15[74] ECMP dissector crash. Issue 20214[75].

• CIP I/O is not detected by "enip" filter anymore. Issue 19517[76].

• Fuzz job issue: fuzz-2024-09-03-7550.pcap. Issue 20041[77].

• OSS-Fuzz 71476: wireshark:fuzzshark_ip_proto-udp:
Index-out-of-bounds in DOFObjectID_Create_Unmarshal. Issue
20065[78].

• JA4_c hashes an empty field to e3b0c44298fc when it should be
000000000000. Issue 20066[79].

• Opening Wireshark 4.4.0 on macOS 15.0 disconnects iPhone
Mirroring. Issue 20082[80].

• PTP analysis loses track of message associations in case of
sequence number resets. Issue 20099[81].

• USB CCID: response packet in case SetParameters command is
unsupported is flagged as malformed. Issue 20107[82].

• dumpcap crashes when run from TShark with a capture filter. Issue
20108[83].

• SRT dissector: The StreamID (SID) in the handshake extension is
displayed without regarding the control characters and with NUL as
terminating. Issue 20113[84].

• Ghost error message on POP3 packets. Issue 20124[85].

• Building against c-ares 1.34 fails. Issue 20125[86].

• D-Bus is not optional anymore. Issue 20126[87].

• macOS Intel DMGs aren’t fully notarized. Issue 20129[88].

• Incorrect name for MLD Capabilities and Operations Present flag in
dissection of MLD Capabilities for MLO wifi-7 capture. Issue
20134[89].

• CQL Malformed Packet v4 S → C Type RESULT: Prepared[Malformed
Packet] Issue 20142[90].

• Wi-Fi: 256 Block Ack (BA) is not parsed properly. Issue 20156[91].

• BACnet ReadPropertyMultiple request Maximum allowed recursion
depth reached. Issue 20159[92].

• Statistics→I/O Graph crashes when using simple moving average.
Issue 20163[93].

• HTTP2 body decompression fails on DATA with a single padded frame.
Issue 20167[94].

• Compiler warning for ui/tap-rtp-common.c (ignoring return value)
Issue 20169[95].

• SIP dissector bug due to "be-route" param in VIA header. Issue
20173[96].

• Coredump after trying to open 'Follow TCP stream' Issue 20174[97].

• Protobuf JSON mapping error. Issue 20182[98].

• Display filter "!stp.pvst.origvlan in { vlan.id }" causes a crash
(Version 4.4.1) Issue 20183[99].

• Extcap plugins shipped with Wireshark Portable are not found in
version 4.4.1. Issue 20184[100].

• IEEE 802.11be: Wrong regulatory info in HE Operation IE in Beacon
frame. Issue 20187[101].

• Wireshark 4.4.1 does not decode RTCP packets. Issue 20188[102].

• Qt: Display filter sub-menu can only be opened on the triangle,
not the full name. Issue 20190[103].

• Qt: Changing the display filter does not update the Conversations
or Endpoints dialogs. Issue 20191[104].

• MODBUS Dissector bug. Issue 20192[105].

• Modbus dissector bug - Field Occurence and Layer Operator
modbus.bitval field. Issue 20193[106].

• Wireshark crashes when a field is dragged from packet details
towards the find input. Issue 20204[107].

• Lua DissectorTable("") : set ("10,11") unexpected behavior in
locales with comma as decimal separator. Issue 20216[108].

The TCP dissector no longer falls back to using the client port as a
criterion for selecting a payload dissector when the server port does
not select a payload dissector (except for port 20, active FTP). This
behavior can be changed using the "Client port dissectors" preference.

Display filters now correctly handle floating point conversion errors.

The Lua API now has better support for comma-separated ranges in
different locales.

Wireshark 4.4.1 included the following changes. See the release
notes[109] for details:

• wnpa-sec-2024-12[110] ITS dissector crash. Issue 20026[111].

• wnpa-sec-2024-13[112] AppleTalk and RELOAD Framing dissector
crashes. Issue 20114[113].

• Refresh interface during live-capture leads to corrupt interface
handling. Issue 11176[114].

• Media type "application/octet-stream" registered for both Thread
and UASIP. Issue 14729[115].

• Extcap toolbar stops working when new interface is added. Issue
19854[116].

• Decoding error ITS CPM version 2.1.1. Issue 19886[117].

• Build error in 4.3.0: sync_pipe_run_command_actual error: argument
2 is null but the corresponding size argument 3 value is 512004
[-Werror=nonnull] Issue 19930[118].

• html2text.py doesn’t handle the `<sup>` tag. Issue 20020[119].

• Incorrect NetFlow v8 TOS AS aggregation dissection. Issue
20021[120].

• The Windows packages don’t ship with the IP address plugin. Issue
20030[121].

• O_PATH is Linux-and-FreeBSD-specific. Issue 20031[122].

• Wireshark 4.4.0 doesn’t install USBcap USBcapCMD.exe in the
correct directory. Issue 20040[123].

• OER dissector is not considering the preamble if ASN.1 SEQUENCE
definition includes extension marker but no OPTIONAL items. Issue
20044[124].

• Bluetooth classic L2CAP incorrect dissection with connectionless
reception channel. Issue 20047[125].

• Profile auto switch filters : Grayed Display Filter Expression
dialog box when opened from Configuration Profiles dialog box.
Issue 20049[126].

• Wireshark 4.4.0 / macOS 14.6.1 wifi if monitor mode. Issue
20051[127].

• TECMP Data Type passes too much data to sub dissectors. Issue
20052[128].

• Wireshark and tshark 4.4.0 ignore extcap options specified on the
command line. Issue 20054[129].

• Cannot open release notes due to incorrect path with duplicated
directory components. Issue 20055[130].

• Unable to open "Release Notes" from the "Help" menu. Issue
20056[131].

• No capture interfaces if Wireshark is started from command line
with certain paths. Issue 20057[132].

• Wireshark 4.4.0 extcap path change breaks third party extcap
installers. Issue 20069[133].

• Fuzz job UTF-8 encoding issue: fuzz-2024-09-10-7618.pcap. Issue
20071[134].

• Unable to create larger files than 99 size units. Issue
20079[135].

• Opening Wireshark 4.4.0 on macOS 15.0 disconnects iPhone
Mirroring. Issue 20082[136].

• PRP trailer not shown for L2 IEC 61850 GOOSE packets in 4.4.0 (was
working in 4.2.7) Issue 20088[137].

• GUI lags because NetworkManager keeps turning 802.11 monitor mode
off. Issue 20090[138].

• Error while getting Bluetooth application process id by <shell:ps
-A | grep com.*android.bluetooth> Issue 20100[139].

• Fuzz job assertion: randpkt-2024-10-05-7200.pcap. Issue
20110[140].

Wireshark 4.4.0 included the following changes. See the release
notes[141] for details:

Many improvements and fixes to the graphing dialogs, including I/O
Graphs, Flow Graph / VoIP Calls, and TCP Stream Graphs.

Wireshark now supports automatic profile switching. You can associate
a display filter with a configuration profile, and when you open a
capture file that matches the filter, Wireshark will automatically
switch to that profile.

Support for Lua 5.3 and 5.4 has been added, and support for Lua 5.1
and 5.2 has been removed. The Windows and macOS installers now ship
with Lua 5.4.6.

Improved display filter support for value strings (optional string
representations for numeric fields).

Display filter functions can be implemented as plugins, similar to
protocol dissectors and file parsers.

Display filters can be translated to pcap filters using "Edit › Copy ›
Display filter as pcap filter" if each display filter field has a
corresponding pcap filter equivalent.

Custom columns can be defined using any valid field expression, such
as display filter functions, packet slices, arithmetic calculations,
logical tests, raw byte addressing, and protocol layer modifiers.

Custom output fields for `tshark -e` can also be defined using any
valid field expression.

Wireshark can be built with the zlib-ng instead of zlib for compressed
file support. Zlib-ng is substantially faster than zlib. The official
Windows and macOS packages include this feature.

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[142] 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 "Help › About
Wireshark › Folders" or `tshark -G 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&A site[143] and on the
wireshark-users mailing list. Subscription information and archives
for all of Wireshark’s mailing lists can be found on the mailing list
site[144].

Bugs and feature requests can be reported on the issue tracker[145].

You can learn protocol analysis and meet Wireshark’s developers at
SharkFest[146].

Getting Certified

You can become a Wireshark Certified Analyst! Learn more at
https://www.wireshark.org/certifications

How You Can Help

The Wireshark Foundation helps as many people as possible understand
their networks as much as possible. You can find out more and donate
at wiresharkfoundation.org[147].

Frequently Asked Questions

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

References

1. https://wiresharkfoundation.org
2. https://gitlab.com/wireshark/wireshark/-/issues/20612
3. https://gitlab.com/wireshark/wireshark/-/issues/20647
4. https://gitlab.com/wireshark/wireshark/-/issues/20655
5. https://gitlab.com/wireshark/wireshark/-/issues/20665
6. https://gitlab.com/wireshark/wireshark/-/issues/20671
7. https://www.wireshark.org/docs/relnotes/wireshark-4.4.8.html
8. https://gitlab.com/wireshark/wireshark/-/issues/20362
9. https://gitlab.com/wireshark/wireshark/-/issues/20526
10. https://gitlab.com/wireshark/wireshark/-/issues/20585
11. https://gitlab.com/wireshark/wireshark/-/issues/20588
12. https://gitlab.com/wireshark/wireshark/-/issues/20589
13. https://gitlab.com/wireshark/wireshark/-/issues/20590
14. https://gitlab.com/wireshark/wireshark/-/issues/20601
15. https://gitlab.com/wireshark/wireshark/-/issues/20615
16. https://gitlab.com/wireshark/wireshark/-/issues/20618
17. https://www.wireshark.org/docs/relnotes/wireshark-4.4.7.html
18. https://www.wireshark.org/security/wnpa-sec-2025-02
19. https://gitlab.com/wireshark/wireshark/-/issues/20509
20. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-5601
21. https://gitlab.com/wireshark/wireshark/-/issues/20463
22. https://gitlab.com/wireshark/wireshark/-/issues/20496
23. https://gitlab.com/wireshark/wireshark/-/issues/20497
24. https://gitlab.com/wireshark/wireshark/-/issues/20507
25. https://gitlab.com/wireshark/wireshark/-/issues/20523
26. https://gitlab.com/wireshark/wireshark/-/issues/20527
27. https://gitlab.com/wireshark/wireshark/-/issues/20531
28. https://gitlab.com/wireshark/wireshark/-/issues/20554
29. https://www.wireshark.org/docs/relnotes/wireshark-4.4.6.html
30. https://gitlab.com/wireshark/wireshark/-/issues/13718
31. https://gitlab.com/wireshark/wireshark/-/issues/15978
32. https://gitlab.com/wireshark/wireshark/-/issues/18216
33. https://gitlab.com/wireshark/wireshark/-/issues/18717
34. https://gitlab.com/wireshark/wireshark/-/issues/20343
35. https://gitlab.com/wireshark/wireshark/-/issues/20355
36. https://gitlab.com/wireshark/wireshark/-/issues/20371
37. https://gitlab.com/wireshark/wireshark/-/issues/20372
38. https://gitlab.com/wireshark/wireshark/-/issues/20423
39. https://gitlab.com/wireshark/wireshark/-/issues/20429
40. https://gitlab.com/wireshark/wireshark/-/issues/20434
41. https://gitlab.com/wireshark/wireshark/-/issues/20459
42. https://gitlab.com/wireshark/wireshark/-/issues/20463
43. https://gitlab.com/wireshark/wireshark/-/issues/20476
44. https://www.wireshark.org/docs/relnotes/wireshark-4.4.5.html
45. https://gitlab.com/wireshark/wireshark/-/issues/20392
46. https://gitlab.com/wireshark/wireshark/-/issues/20403
47. https://www.wireshark.org/docs/relnotes/wireshark-4.4.4.html
48. https://www.wireshark.org/security/wnpa-sec-2025-01
49. https://gitlab.com/wireshark/wireshark/-/issues/20373
50. https://gitlab.com/wireshark/wireshark/-/issues/20263
51. https://gitlab.com/wireshark/wireshark/-/issues/20300
52. https://gitlab.com/wireshark/wireshark/-/issues/20330
53. https://gitlab.com/wireshark/wireshark/-/issues/20354
54. https://gitlab.com/wireshark/wireshark/-/issues/20357
55. https://gitlab.com/wireshark/wireshark/-/issues/20359
56. https://gitlab.com/wireshark/wireshark/-/issues/20367
57. https://gitlab.com/wireshark/wireshark/-/issues/20386
58. https://gitlab.com/wireshark/wireshark/-/issues/20387
59. https://gitlab.com/wireshark/wireshark/-/issues/20389
60. https://gitlab.com/wireshark/wireshark/-/issues/20391
61. https://gitlab.com/wireshark/wireshark/-/issues/20394
62. https://www.wireshark.org/docs/relnotes/wireshark-4.4.3.html
63. https://gitlab.com/wireshark/wireshark/-/issues/20247
64. https://gitlab.com/wireshark/wireshark/-/issues/20276
65. https://gitlab.com/wireshark/wireshark/-/issues/20290
66. https://gitlab.com/wireshark/wireshark/-/issues/20304
67. https://gitlab.com/wireshark/wireshark/-/issues/20311
68. https://gitlab.com/wireshark/wireshark/-/issues/20313
69. https://gitlab.com/wireshark/wireshark/-/issues/20320
70. https://gitlab.com/wireshark/wireshark/-/issues/20326
71. https://www.wireshark.org/docs/relnotes/wireshark-4.4.2.html
72. https://www.wireshark.org/security/wnpa-sec-2024-14
73. https://gitlab.com/wireshark/wireshark/-/issues/20176
74. https://www.wireshark.org/security/wnpa-sec-2024-15
75. https://gitlab.com/wireshark/wireshark/-/issues/20214
76. https://gitlab.com/wireshark/wireshark/-/issues/19517
77. https://gitlab.com/wireshark/wireshark/-/issues/20041
78. https://gitlab.com/wireshark/wireshark/-/issues/20065
79. https://gitlab.com/wireshark/wireshark/-/issues/20066
80. https://gitlab.com/wireshark/wireshark/-/issues/20082
81. https://gitlab.com/wireshark/wireshark/-/issues/20099
82. https://gitlab.com/wireshark/wireshark/-/issues/20107
83. https://gitlab.com/wireshark/wireshark/-/issues/20108
84. https://gitlab.com/wireshark/wireshark/-/issues/20113
85. https://gitlab.com/wireshark/wireshark/-/issues/20124
86. https://gitlab.com/wireshark/wireshark/-/issues/20125
87. https://gitlab.com/wireshark/wireshark/-/issues/20126
88. https://gitlab.com/wireshark/wireshark/-/issues/20129
89. https://gitlab.com/wireshark/wireshark/-/issues/20134
90. https://gitlab.com/wireshark/wireshark/-/issues/20142
91. https://gitlab.com/wireshark/wireshark/-/issues/20156
92. https://gitlab.com/wireshark/wireshark/-/issues/20159
93. https://gitlab.com/wireshark/wireshark/-/issues/20163
94. https://gitlab.com/wireshark/wireshark/-/issues/20167
95. https://gitlab.com/wireshark/wireshark/-/issues/20169
96. https://gitlab.com/wireshark/wireshark/-/issues/20173
97. https://gitlab.com/wireshark/wireshark/-/issues/20174
98. https://gitlab.com/wireshark/wireshark/-/issues/20182
99. https://gitlab.com/wireshark/wireshark/-/issues/20183
100. https://gitlab.com/wireshark/wireshark/-/issues/20184
101. https://gitlab.com/wireshark/wireshark/-/issues/20187
102. https://gitlab.com/wireshark/wireshark/-/issues/20188
103. https://gitlab.com/wireshark/wireshark/-/issues/20190
104. https://gitlab.com/wireshark/wireshark/-/issues/20191
105. https://gitlab.com/wireshark/wireshark/-/issues/20192
106. https://gitlab.com/wireshark/wireshark/-/issues/20193
107. https://gitlab.com/wireshark/wireshark/-/issues/20204
108. https://gitlab.com/wireshark/wireshark/-/issues/20216
109. https://www.wireshark.org/docs/relnotes/wireshark-4.4.1.html
110. https://www.wireshark.org/security/wnpa-sec-2024-12
111. https://gitlab.com/wireshark/wireshark/-/issues/20026
112. https://www.wireshark.org/security/wnpa-sec-2024-13
113. https://gitlab.com/wireshark/wireshark/-/issues/20114
114. https://gitlab.com/wireshark/wireshark/-/issues/11176
115. https://gitlab.com/wireshark/wireshark/-/issues/14729
116. https://gitlab.com/wireshark/wireshark/-/issues/19854
117. https://gitlab.com/wireshark/wireshark/-/issues/19886
118. https://gitlab.com/wireshark/wireshark/-/issues/19930
119. https://gitlab.com/wireshark/wireshark/-/issues/20020
120. https://gitlab.com/wireshark/wireshark/-/issues/20021
121. https://gitlab.com/wireshark/wireshark/-/issues/20030
122. https://gitlab.com/wireshark/wireshark/-/issues/20031
123. https://gitlab.com/wireshark/wireshark/-/issues/20040
124. https://gitlab.com/wireshark/wireshark/-/issues/20044
125. https://gitlab.com/wireshark/wireshark/-/issues/20047
126. https://gitlab.com/wireshark/wireshark/-/issues/20049
127. https://gitlab.com/wireshark/wireshark/-/issues/20051
128. https://gitlab.com/wireshark/wireshark/-/issues/20052
129. https://gitlab.com/wireshark/wireshark/-/issues/20054
130. https://gitlab.com/wireshark/wireshark/-/issues/20055
131. https://gitlab.com/wireshark/wireshark/-/issues/20056
132. https://gitlab.com/wireshark/wireshark/-/issues/20057
133. https://gitlab.com/wireshark/wireshark/-/issues/20069
134. https://gitlab.com/wireshark/wireshark/-/issues/20071
135. https://gitlab.com/wireshark/wireshark/-/issues/20079
136. https://gitlab.com/wireshark/wireshark/-/issues/20082
137. https://gitlab.com/wireshark/wireshark/-/issues/20088
138. https://gitlab.com/wireshark/wireshark/-/issues/20090
139. https://gitlab.com/wireshark/wireshark/-/issues/20100
140. https://gitlab.com/wireshark/wireshark/-/issues/20110
141. https://www.wireshark.org/docs/relnotes/wireshark-4.4.0.html
142. https://www.wireshark.org/download.html
143. https://ask.wireshark.org/
144. https://lists.wireshark.org/lists/
145. https://gitlab.com/wireshark/wireshark/-/issues
146. https://sharkfest.wireshark.org
147. https://wiresharkfoundation.org
148. https://www.wireshark.org/faq.html

Digests

wireshark-4.4.9.tar.xz: 46830008 bytes
SHA256(wireshark-4.4.9.tar.xz)=60551dc787f41e87aeaa1e9c33304f9008037e3baf9fa11aef9c2d584cc0b54b
SHA1(wireshark-4.4.9.tar.xz)=dc91c68b03b389645fa6dade92960863d74bca1d

Wireshark-4.4.9-x64.exe: 87419640 bytes
SHA256(Wireshark-4.4.9-x64.exe)=66a42718a940af6cce058ddbb2c529c65d5157b889e9a17ad9d9a89814de080e
SHA1(Wireshark-4.4.9-x64.exe)=5483188b2b1f1d968a1ec447083d68ebe13cc7b4

Wireshark-4.4.9-arm64.exe: 68891560 bytes
SHA256(Wireshark-4.4.9-arm64.exe)=559a09b22f47afad45898369b0c21c73921f9b855bcc0fea9c6e06f63b1245eb
SHA1(Wireshark-4.4.9-arm64.exe)=71ff558727de461c21a5e7dd4c381878a7f4c015

Wireshark-4.4.9-x64.msi: 63983616 bytes
SHA256(Wireshark-4.4.9-x64.msi)=02c3064187e443b79308cea88ca649c70d9cb85adfdd34e5250933763e2d8b29
SHA1(Wireshark-4.4.9-x64.msi)=eff6262d8586872979b9a531b6c1022aae223207

WiresharkPortable64_4.4.9.paf.exe: 64519728 bytes
SHA256(WiresharkPortable64_4.4.9.paf.exe)=8825a080a5337cecebba2127dc894662bd265bc47ba1c4841b0253126707abf1
SHA1(WiresharkPortable64_4.4.9.paf.exe)=547ff1c83f865a337e5ea573adc1d1cd2076e5a0

Wireshark 4.4.9 Arm 64.dmg: 65835059 bytes
SHA256(Wireshark 4.4.9 Arm 64.dmg)=6623f789646c6a64735d2179fd9333a05606f83f7946d897448eea2074e8654b
SHA1(Wireshark 4.4.9 Arm 64.dmg)=35ad205e3fce102933da9e6bab20431761fccf98

Wireshark 4.4.9 Intel 64.dmg: 69571463 bytes
SHA256(Wireshark 4.4.9 Intel 64.dmg)=f7e742a6cd42f13c81ad63a99764262c7e15bd66c8b48eb9bf879803150d5b7d
SHA1(Wireshark 4.4.9 Intel 64.dmg)=8e65c34ae28bcf1a39b805444e983ddadb220432

You can validate these hashes using the following commands (among others):

Windows: certutil -hashfile Wireshark-win64-x.y.z.exe SHA256
Linux (GNU Coreutils): sha256sum wireshark-x.y.z.tar.xz
macOS: shasum -a 256 "Wireshark x.y.z Arm 64.dmg"
Other: openssl sha256 wireshark-x.y.z.tar.xz

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Prev by Date: [Wireshark-users] Re: [IANA #1427305] Invalid ip address used.
Previous by thread: [Wireshark-users] srtp is missing.
Index(es):
- Date
- Thread