Sourced from snow's releases.
v0.9.6
- Validate invalid PSK positions when building a Noise protocol.
- Raise errors in various typos/mistakes in Noise patterns when parsing.
- Deprecate the
sodiumoxidebackend, as that crate is no longer maintained. We may eventually migrate it to a maintaned version of the crate, but for now it's best to warn users.- Set a hard limit in
read_message()in transport mode to 65535 to be fully compliant with the Noise specification.Full Changelog: https://github.com/mcginty/snow/compare/v0.9.5...v0.9.6
v0.9.5
This is a security release that fixes a logic flaw in decryption in
TransportState(i.e. the stateful one), where the nonce could increase even when decryption failed, which can cause a desync between the sender and receiver, opening this up as a denial of service vector if the attacker has the ability to inject packets in the channel Noise is talking over.More details can be found in the advisory: https://github.com/mcginty/snow/security/advisories/GHSA-7g9j-g5jg-3vv3
All users are encouraged to update.
v0.9.4
This is a dependency version bump release because a couple of important dependencies released new versions that needed a
Cargo.tomlbump:
ring0.17pqcrypto-kyber0.8aes-gcm0.10chacha20poly13050.10
a4be73f
meta: v0.9.6 release9e53dcf
TransportState: limit read_message size to 65535faf0560
Deprecate sodiumoxide resolver308a24d
Add warnings about multiple calls to same method in Builderf280991
Error when extraneous parameters are included in string to parsedbdcc48
Error on duplicate modifiers in parameter string8b1a819
Validate PSK index in pattern to avoid panic74e30cf
meta: v0.9.5 release12e8ae5
Stateful nonce desync fix02c26b7
Remove clap from simple example