include::attributes.adoc[]
:stylesheet: ws.css
:linkcss:
:copycss: {css_dir}/{stylesheet}

= Stratoshark {stratoshark-version} Release Notes
// Asciidoctor Syntax Quick Reference:
// https://asciidoctor.org/docs/asciidoc-syntax-quick-reference/

This is an experimental release intended to test new features for Stratoshark 1.0.

== What is Stratoshark?

Stratoshark is a system call and log analyzer.
It combines the analysis and filtering features of Wireshark with the capture and data enrichment features of https://falco.org[Falco].
It can be used for troubleshooting, analysis, development and education.

Stratoshark is hosted by the Wireshark Foundation, a nonprofit which promotes protocol and system analysis education.
Stratoshark 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 https://wiresharkfoundation.org[wiresharkfoundation.org].

== What’s New

// Add a summary of **major** changes here.
// Add other changes to "New and Updated Features" below.

// Many other improvements have been made.
// See the “New and Updated Features” section below for more details.

The following changes have been made since version 0.10.0:

The Stratoshark Windows installer now includes a DLL that was required by the cloudtrail and gcpaudit plugins.

The following issues have been fixed:
* Wireshark appears in German where Systemlanguage is Dutch. wsbuglink:20347[].
* If you double-click an interface in the welcome screen interface list, and have typed nothing in the capture filter box, the system reports an invalid capture filter. wsbuglink:21303[].
* Qt: Appearance mode is stored per-profile while theme name is global — theme flips on profile switch. wsbuglink:21311[].
* Qt: 'Recent filters' arrow button gives no hover/pressed feedback. wsbuglink:21322[].
* Qt: Hidden interfaces (Welcome page right-click) not persisted across profile switch or restart. wsbuglink:21325[].
* Qt: Preferences dialog left category tree cannot be resized (labels truncated, only horizontal scrollbar) wsbuglink:21327[].
* Stratoshark: no-libpcap compilation broken (actionCaptureRestart) — fix from 554baf6294 never applied. wsbuglink:21328[].
* Qt: Make theme preview resemble a real Wireshark window (mini packet-list mockup) wsbuglink:21329[].
* stratoshark -D lists a bunch of *network* capture devices. wsbuglink:21332[].

The following changes have been made since version 0.9.3:

* Stratoshark can now read https://learn.microsoft.com/en-us/sysinternals/downloads/procmon[Process Monitor] (Procmon) files.

* Welcome Page Redesign
  The welcome page has been redesigned to be more informative and easier to navigate. It now highlights the learning sections better and includes a new sidebar with tips and tricks for using Wireshark effectively. The welcome page is now also more accessible, with improved keyboard navigation and screen reader support.

* Lua Debugger
  A built-in Lua script debugger has been added. It supports breakpoints, single-stepping, variable inspection, expression evaluation, and stack traces.

* Themes
  Stratoshark now uses the same theme system as Wireshark, driving the colors used throughout the GUI from a single theme instead of many individual color preferences. The renamed menu:Appearance[Theme and Font] preferences page lets you pick a theme, switch between Light, Dark, and System appearance, set the packet pane font, and preview the result. A built-in default theme ships with Stratoshark, and additional themes can be installed as JSONC (JSON with Comments) files. The previous per-color settings (marked and ignored packets, "Follow Stream" client and server text, display filter validity, and the selected packet) are now provided by the active theme.
  Personal themes can now be dropped as single `.jsonc` files into _$HOME/.local/lib/stratoshark/themes_ (Unix) or _%APPDATA%\Stratoshark\themes_ (Windows); the filename becomes the theme's name in the dropdown. The exact path is shown in the About dialog's _Folders_ tab.
  On first launch after the upgrade, Stratoshark checks the Default profile's preferences for customized values of the removed per-color settings. If any are found, a personal theme named _Personal (Migrated)_ is created automatically in the personal themes directory, the legacy keys are removed from the Default profile's preferences file, and the theme is activated so the original visual customizations are preserved. The migration runs once: the generated _personal.jsonc_ can be edited, renamed, or deleted by hand at any time.
  The welcome page section headers ("Open", "Capture", "Learn") and the filter validity tints have been restored to the historical Classic look (Tango sky_blue brand, saturated GTK-era dark green / dark red filter backgrounds).

// XXX This should just describe what changed.
// * The capture and display filter fields have a refreshed, consistent look and
//   feel. As you type, the field colors itself to show at a glance whether the
//   filter is valid, invalid, or uses deprecated syntax, and that feedback now
//   appears immediately in place. Each field carries the same set of in-line
//   buttons — a bookmark to save and manage your filters, a clear button, an
//   apply button, and a drop-down listing your recently used filters — and as you
//   type it suggests completions drawn from field names together with your recent
//   and saved filters. Recent display filters are now reached from that drop-down
//   rather than from a combo box. The colors follow the active theme and adapt to
//   the Light and Dark appearances. (When a capture filter names a host, the field
//   may pause briefly while the name is resolved.)

* Zooming (menu:View[Zoom In] / menu:View[Zoom Out]) now scales the whole window, including the capture and display filter fields and other window elements.
  Previously only the packet list and detail pane text size changed.
  The new behavior should be much more useful for demos and presentations.

* The keyboard shortcuts dialog (About Wireshark → Keyboard Shortcuts) has been moved out of of the About dialog to the menu View → Internals → Keyboard Shortcuts and now has a button to print the list of keyboard shortcuts to an HTML file.

* The application icon has been updated to support Liquid Glass on macOS Tahoe.

* Stratoshark and strato can now read plain Kubernetes Audit logs and Google Cloud Audit logs, and CloudTrail logs.

* The CloudTrail and Google Cloud Audit log plugins have been translated to Rust on macOS and Windows. wsbuglink:20869[]

The following changes have been made since version 0.9.2:

* The Windows installers now ship with Qt 6.8.3.
  They previously shipped with Qt 6.8.1.

* Stratoshark now ships with “strato”, a command line tool similar to tshark.

* The Windows and macOS packages now ship with the gcpaudit and k8saudit plugins.

* The Falco Events dissector now adds IP geolocation fields alongside IPv4 and IPv6 address fields.

The following changes have been made since version 0.9.1:

* A new “Plots” dialog has been added, which provides scatter plots in contrast to the “I/O Graphs” dialog, which provides histograms.
  The Plots dialog window supports multiple plots, markers, and automatic scrolling.

* The Falco Bridge dissector has been renamed to Falco Events.
  Filter fields now have a "falcoevents" protocol prefix, but a "falcobridge" protocol alias has been added for backward compatibility.
  wsbuglink:20397[]

* Stratoshark can now show field offsets for supported plugins.

* Cloudtrail log messages can now be viewed as formatted JSON data.

* The system call dissector now has a "falcoevents.fd.stream" field, which provides a unique number for each file descriptor.
  The "Follow File Descriptor Stream" feature now uses this field to track streams. wsbuglink:20538[]

* We now ship universal macOS installers instead of separate packages
for Arm64 and Intel. wsbuglink:17294[]

The following changes have been made since version 0.9.0:

* The application icons have been updated.

=== Bug Fixes

//The following bugs have been fixed:
//* wsbuglink:5000[]
//* wsbuglink:6000[Stratoshark bug]
//* cveidlink:2014-2486[]
//* Stratoshark grabs your ID at 3 am, goes to Waffle House, and insults people.

The following bugs have been fixed since version 0.9.3:

In order to work around wsbuglink:20869[issue 20869], the macOS package ships with the gcpaudit and k8saudit plugins disabled.
In order to enable them, you can rename them from *Stratoshark.app/Contents/PlugIns/stratoshark/falco/_plugin_.so.disabled* to *Stratoshark.app/Contents/PlugIns/stratoshark/falco/_plugin_.so*.

* Interfaces hidden from the welcome page are now remembered across profile switches and restarts. wsbuglink:21325[]

The following bugs have been fixed since version 0.9.2:

* .scap file extension wrongly associated with Wireshark. wsbuglink:20583[].
* sshdig should have a snaplen option. wsbuglink:20586[].

The following bugs have been fixed since version 0.9.1:

* Stratoshark help message has Wiresharkisms in it. wsbuglink:20229[].
* Stratoshark and editcap could write incorrect block types. https://gitlab.com/wireshark/wireshark/-/merge_requests/19238[Merge request 19238].
* Stratoshark says I can't capture on local interfaces. wsbuglink:20494[].
* Stratoshark: Crash While Sorting on evt.buflen column. wsbuglink:20571[].

The following bugs have been fixed since version 0.9.0:

* Falco Bridge: Empty frame.protocols field. wsbuglink:20248[].
* Sysdig event and Falco bridge dissection mismatch due to unsupported pcapng block types. wsbuglink:20358[].


=== New and Updated Features

Stratoshark can capture system calls locally on Linux and a variety of log sources on Windows, macOS, and Linux.

The following features are either new or have been significantly updated since version 0.9.0:

* The welcome screen's capture-source activity sparklines now keep their history for the whole session.
  Previously the sparklines, and the activity-first ordering of the source list, were reset whenever you
  started or stopped a capture or returned to the welcome screen, so the list re-shuffled each time.
  Now the history persists, the ordering stays stable, and a break in a sparkline marks the interval during
  which a capture was running (statistics are not sampled while capturing).
  When a source is dropping packets, the drops are shown as a separate line.
  wsbuglink:21318[]

//* The Windows installers now ship with Qt 6.5.2.
//  They previously shipped with Qt 6.2.3.

=== Removed Features and Support

Dumpcap's TCP@host:port interface has been removed.

Building with Qt 5 is no longer supported.

// === Removed Dissectors


//=== New File Format Decoding Support

//[commaize]
//--
//--

// === New Protocol Support

// Add one protocol per line between the -- delimiters in the format
// “Full protocol name (Abbreviation)”
// git log --oneline --diff-filter=A --stat v4.3.0rc0.. epan/dissectors plugins
// [commaize]
// --
// --

// === Updated Protocol Support

// Too many protocol updates have been made to list them all here.

//=== New and Updated Capture File Support

// There is no new or updated capture file support in this release.
// Add one file type per line between the -- delimiters.
// [commaize]
// --
// --

// === New and Updated Capture Interfaces support
// [commaize]
// --
// --

//=== New and Updated Codec support

//_Non-empty section placeholder._

// === Major API Changes


== Getting Stratoshark

Stratoshark source code and installation packages are available from
https://www.stratoshark.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
// https://www.wireshark.org/download.html[download page]
// on the Wireshark web site.

== File Locations

Stratoshark looks in several different locations for preference files, plugins, and other files.
These locations vary from platform to platform.
You can use menu:Help[About Stratoshark,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
https://ask.wireshark.org/[Wireshark’s Q&A site]
and on the wireshark-users mailing list.
Subscription information and archives for all of Wireshark’s mailing lists can be found on https://lists.wireshark.org/lists/[the mailing list site].

Bugs and feature requests can be reported on
https://gitlab.com/wireshark/wireshark/-/issues[the issue tracker].

You can learn system call and log analysis and meet Stratoshark’s developers at
https://sharkfest.wireshark.org[SharkFest].

// Official Wireshark training and certification are available from
// https://www.wiresharktraining.com/[Wireshark University].

== How You Can Help

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

// == Frequently Asked Questions

// A complete FAQ is available on the
// https://www.wireshark.org/faq.html[Stratoshark web site].
