Every time I go to your download page, I get a 404!!! On Wed, Dec 11, 2019 at 4:09 PM Wireshark announcements < wireshark-annou...@wireshark.org> wrote:
> I'm proud to announce the release of Wireshark 3.2.0rc2. > > > This is the second release candidate for Wireshark 3.2. > > 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 > > This is the last release branch with official support for Windows 7 > and Windows Server 2008 R2. > > Many improvements have been made. See the “New and Updated Features” > section below for more details. > > New and Updated Features > > The following features are new (or have been significantly updated) > since version 3.2.0rc1: > > • Nothing of note. > > The following features are new (or have been significantly updated) > since version 3.1.1: > > • Miscellaneous UI fixes and updates. > > • The macOS installer now ships with Qt 5.12.6. It previously > shipped with Qt 5.12.5. > > The following features are new (or have been significantly updated) > since version 3.1.0: > > • Automatic updates are supported on macOS. > > • You can now select multiple packets in the packet list at the > same time > > • They can be exported as Text by “Ctrl+C” or “Cmd+C” and the > corresponding menu in “Edit › Copy › As …” > > • They can be marked/unmarked or ignored/unignored at the same time > > • They can be exported and printed using the corresponding menu > entries “File › Export Specified Packets”, “File › Export Packet > Dissections” and “File › Print” > > You can now follow HTTP/2 and QUIC streams. > > You can once again mark and unmark packets using the middle mouse > button. This feature went missing around 2009 or so. > > The Windows packages are now built using Microsoft Visual Studio > 2019. > > IOGraph automatically adds a graph for the selected display filter if > no previous graph exists > > Action buttons for the display filter bar may be aligned left via the > context menu > > • The "Expression…" toolbar entry has been moved to "Analyze › > Display filter Expression …" as well as to the context menu of > the display filter toolbar > > Allow extcaps to be loaded from the personal configuration directory > > The Wireshark 3.1.0 Windows installers ship with Qt 5.12.6. Previous > installers shipped with Qt 5.12.4. > > The following features are new (or have been significantly updated) > since version 3.0.0: > > • You can drag and drop a field to a column header to create a > column for that field, or to the display filter input to create a > display filter. If a display filter is applied, the new filter > can be added using the same rules as “Apply Filter” > > • You can drag and drop a column entry to the display filter to > create a filter for it. > > • You can import profiles from a .zip archive or an existing > directory. > > • Dark mode support on macOS and dark theme support on other > platforms has been improved. > > • Brotli decompression support in HTTP/HTTP2 (requires the brotli > library). > > • The build system now checks for a SpeexDSP system library > installation. The bundled Speex resampler code is still provided > as a fallback. > > • WireGuard decryption can now be enabled through keys embedded in > a pcapng in addition to the existing key log preference (Bug > 15571[1]). > > • A new tap for extracting credentials from the capture file has > been added. It can be accessed through the -z credentials option > in tshark or from the “Tools › Credentials” menu in Wireshark. > > • Editcap can now split files on floating point intervals. > > • Windows .msi packages are now signed using SHA-2[2]. .exe > installers are still dual-signed using SHA-1 and SHA-2. > > • The “Enabled Protocols” Dialog now only enables, disables and > inverts protocols based on the set filter selection. The protocol > type (standard or heuristic) may also be choosen as a filter > value. > > • Save RTP stream to .au supports any codec with 8000 Hz rate > supported by Wireshark (shown in RTP player). If save of audio is > not possible (unsupported codec or rate), silence of same length > is saved and warning is shown. > > • The “Analyze › Apply as Filter” and “Analyze › Prepare a Filter” > packet list and detail popup menus now show a preview of their > respective filters. > > • Protobuf files (*.proto) can now be configured to enable more > precise parsing of serialized Protobuf data (such as gRPC). > > • HTTP2 support streaming mode reassembly. To use this feature, > subdissectors can register itself to "streaming_content_type" > dissector table and return pinfo→desegment_len and > pinfo→desegment_offset to tell HTTP2 when to start and how many > additional bytes requires when next called. > > • The message of stream gRPC method can now be parsed with > supporting of HTTP2 streaming mode reassembly feature. > > • The Wireshark 3.1.0 Windows installers ship with Qt 5.12.4. > Previous installers shipped with Qt 5.12.1. > > New Protocol Support > > 3GPP BICC MST (BICC-MST), 3GPP log packet (LOG3GPP), 3GPP/GSM Cell > Broadcast Service Protocol (cbsp), Asynchronous Management Protocol > (AMP), Bluetooth Mesh Beacon, Bluetooth Mesh PB-ADV, Bluetooth Mesh > Provisioning PDU, Bluetooth Mesh Proxy, CableLabs Layer-3 Protocol > IEEE EtherType 0xb4e3 (CL3), DCOM IProvideClassInfo, DCOM ITypeInfo, > Diagnostic Log and Trace (DLT), Distributed Replicated Block Device > (DRBD), Dual Channel Wi-Fi (CL3DCW), EBHSCR Protocol (EBHSCR), EERO > Protocol (EERO), evolved Common Public Radio Interface (eCPRI), File > Server Remote VSS Protocol (FSRVP), FTDI FT USB Bridging Devices > (FTDI FT), Graylog Extended Log Format over UDP (GELF), GSM/3GPP CBSP > (Cell Broadcast Service Protocol), ITS message - CAMv1, ITS message - > DENMv1, Linux net_dm (network drop monitor) protocol, MIDI System > Exclusive DigiTech (SYSEX DigiTech), Network Controller Sideband > Interface (NCSI), NR Positioning Protocol A (NRPPa) TS 38.455, NVM > Express over Fabrics for TCP (nvme-tcp), OsmoTRX Protocol (GSM > Transceiver control and data), Scalable service-Oriented MiddlewarE > over IP (SOME/IP), USB 2.0 Link Layer (USBLL), and Wi-Fi Neighbour > Awareness Networking (NAN) > > Updated Protocol Support > > Too many protocols have been updated to list here. > > New and Updated Capture File Support > > 3gpp phone, Android Logcat Text, Ascend, Busmaster log file, Candump, > Endace ERF, NetScaler, pcapng, and Savvius *Peek > > Getting Wireshark > > Wireshark source code and installation packages are available from > https://www.wireshark.org/download.html[3]. > > 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[4] 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/[5] > > Community support is available on Wireshark’s Q&A site[6] 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[7]. > > Bugs and feature requests can be reported on the bug tracker[8]. > > Official Wireshark training and certification are available from > Wireshark University[9]. > > Frequently Asked Questions > > A complete FAQ is available on the Wireshark web site[10]. > > Last updated 2019-12-11 20:23:10 UTC > > References > > 1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15571 > 2. https://support.microsoft.com/en-us/help/4472027/2019-sha-2-code-s > igning-support-requirement-for-windows-and-wsus > 3. https://www.wireshark.org/download.html > 4. https://www.wireshark.org/download.html#thirdparty > 5. https://www.wireshark.org/docs/ > 6. https://ask.wireshark.org/ > 7. https://www.wireshark.org/lists/ > 8. https://bugs.wireshark.org/ > 9. https://www.wiresharktraining.com/ > 10. https://www.wireshark.org/faq.html > > > Digests > > wireshark-3.2.0rc2.tar.xz: 31454312 bytes > > SHA256(wireshark-3.2.0rc2.tar.xz)=fc9f39da16a5708dff76bd0df78b244699f4a1f4a13ceb75777000e87ee57e46 > > RIPEMD160(wireshark-3.2.0rc2.tar.xz)=cba58cfb02de7abb7d2b6067a83a590e1431b7f0 > SHA1(wireshark-3.2.0rc2.tar.xz)=cfd217336c613ef3376588da412ecc6acfca164e > > Wireshark-win64-3.2.0rc2.exe: 69031872 bytes > > SHA256(Wireshark-win64-3.2.0rc2.exe)=cf41ea689f9cbb9cf66166e5a2287aafef56d0161be642834f44620365ed085e > > RIPEMD160(Wireshark-win64-3.2.0rc2.exe)=7498d1115e1a8a08559f8d7d6f0d623a932fc1bb > SHA1(Wireshark-win64-3.2.0rc2.exe)=5eced01a12390b58bfb8bf85203f4629bab6be36 > > Wireshark-win32-3.2.0rc2.exe: 63814144 bytes > > SHA256(Wireshark-win32-3.2.0rc2.exe)=7f979ce1f05823e1068bfd7ccc7deba9b65ad46b774a875b0e7f25b3a19c0169 > > RIPEMD160(Wireshark-win32-3.2.0rc2.exe)=006de7e13a3a3e534eda51965a851b50785e0ca4 > SHA1(Wireshark-win32-3.2.0rc2.exe)=871c2e68d3df493a160cc1d1b807b07c6cb32976 > > Wireshark-win64-3.2.0rc2.msi: 48218112 bytes > > SHA256(Wireshark-win64-3.2.0rc2.msi)=dd35ad5470ef9fb233e9fefb5d9ea55e366052f9a0a7c8a8668183f1a2184a63 > > RIPEMD160(Wireshark-win64-3.2.0rc2.msi)=31743d6db25058c09bd1fd4ae4726d417cea0396 > SHA1(Wireshark-win64-3.2.0rc2.msi)=b72870a936935c70fe7558cf7abeaec09ce21ba1 > > Wireshark-win32-3.2.0rc2.msi: 42913792 bytes > > SHA256(Wireshark-win32-3.2.0rc2.msi)=87395c9aa1e16d45ec3af7e2f8e98f5ec91ce834f0d489a66f6656f0b4783a2f > > RIPEMD160(Wireshark-win32-3.2.0rc2.msi)=d37f21ee7d4e26112885ba5522921f2a3b4d12c8 > SHA1(Wireshark-win32-3.2.0rc2.msi)=99999020c98b619ada0a10f77dfbac18a23ebc64 > > WiresharkPortable_3.2.0rc2.paf.exe: 36514584 bytes > > SHA256(WiresharkPortable_3.2.0rc2.paf.exe)=682432a14b3630a08516a3c9a2363dd605355324003247cfe71f859365797b64 > > RIPEMD160(WiresharkPortable_3.2.0rc2.paf.exe)=4bf7bfc8150cc3168a5a4d37ba10e34b4faa7328 > > SHA1(WiresharkPortable_3.2.0rc2.paf.exe)=c1946d592ddb6af2ec86f321ff3a834d5d538eea > > Wireshark 3.2.0rc2 Intel 64.dmg: 96363813 bytes > SHA256(Wireshark 3.2.0rc2 Intel > 64.dmg)=f3aa6aea51b85a73f0c240a6cc5eeb542038b09b24a8c7dad6b8a2b419190985 > RIPEMD160(Wireshark 3.2.0rc2 Intel > 64.dmg)=c664eccdef2c9185e4857bb55e24431559859775 > SHA1(Wireshark 3.2.0rc2 Intel > 64.dmg)=edab72aba192df513bfcfa8db616ba779fdf3621 > > 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 Intel 64.dmg" > Other: openssl sha256 wireshark-x.y.z.tar.xz > > ___________________________________________________________________________ > Sent via: Wireshark-announce mailing list < > wireshark-annou...@wireshark.org> > Archives: https://www.wireshark.org/lists/wireshark-announce > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-announce > mailto:wireshark-announce-requ...@wireshark.org > ?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-users Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe
