Today, we are releasing the next alpha release of the nzyme v2.0.0 series: alpha.13. In this release, we fixed a lot bugs and added new functionality for the 802.11/WiFi subsystem.
Changelog
- New Feature: Automatic 802.11/WiFi Channel Width Modulation
- New Feature: 802.11/WiFi Channel Coverage Overview
- New Feature: Customizable web interface title and favicon
- New feature: Support for environment variables in tap configuration file
- Improvement: Rewritten 802.11/WiFi channel hopping mechanism for improved reliability
- Many other bugfixes and improvements
New Feature: Automatic 802.11/WiFi Channel Width Modulation
WiFi channels can be bonded to increase bandwidth. Before this feature, nzyme was only listening on the default channel width of 20 MHz. From now on, nzyme will automatically cycle through all supported channel widths automatically and ensure that you are not missing wireless traffic.
You can change this behavior back to only 20 MHz coverage by setting the channel_width_hopping_mode or a WiFi capture
to limited. This can make sense if you want to maximize discovery of access points. You can learn more about this new
hopping mode in the documentation.
New Feature: 802.11/WiFi Channel Coverage Overview
There are a lot of WiFi channels, and you want to make sure that you analyze all of them. Missing a channel or channel width can make you blind to attacks using such a channel configuration.
The new channel coverage overview on the tap details page shows you exactly which channel configurations your nzyme tap is monitoring and which may be missing.
New Feature: Customizable web interface browser title and icon
You can now customize the browser title and icon of the nzyme web interface using this new node configuration:
# Miscellaneous.
misc: {
# Custom web interface browser title.
custom_title: "nzyme - Network Defense System"
# URL to a custom favicon.
custom_favicon_url: "https://example.org/favicon.png"
}
New feature: Support for environment variables in tap configuration file
Just like the node configuration file always did, the tap configuration file is now supporting environment variables:
interfaces: {
rest_listen_uri: "https://${REST_LISTEN_URI_HOST}:22900/"
http_external_uri: "${HTTP_EXTERNAL_URI}"
}
You can learn more about environment variables for nzyme config files in the documentation.
Fact: Lennart wrote this feature live on stream. Follow his YouTube channel if you want to see more of this.
Download & Upgrading
All packages are available for download on the downloads page. Upgrading is easy. Please follow the release notes on the downloads page.
New installations should follow the installation documentation.
How can I help?
You are some of the first users to try out nzyme v2.0.0, and we are looking for any kind of feedback:
- What didn’t work, what bugs did you experience?
- What was confusing or seemingly unnecessarily complex?
- What is missing?
- What do you think should be changed?
Again, this is an early release and no feelings will be hurt.
You can file issues on GitHub, join the nzyme Discord or post in the discussion forums to provide your feedback or ask questions.
