Skip to content

Releases: aws/s2n-quic

Release V1.55.0

10 Mar 18:21
25e2706
Compare
Choose a tag to compare

Release Summary:

  • New API added to allow users to change connection limits based on the information in the TLS handshake, such as server name and application protocol. Previously users could only change connection limits based on their peer's remote address.
  • Expose dc::Path creation event in s2n-quic Subscriber.
  • Connection migrations are now allowed even when the disable_active_migration is set to true, as it is not possible to distinguish between the peer performing an active migration, and a NAT rebind.
  • feat(dc): Support storing arbitrary application-provided data in Entry.

What's Changed

Full Changelog: v1.54.0...v1.55.0

Release v1.54.0

27 Feb 01:29
65d6b6e
Compare
Choose a tag to compare

Summary

  • Expand the DataDroppedReason to include the expanded MigrationDenyReason, which would explain more specifically why a connection migration was denied, not just that it was denied.
  • We currently consider the full 4-tuple (local + remote IP addresses and ports) when identifying a path. This seems to be an overly strict interpretation, we should really only be considering the peer address when deciding if it tried to migrate.
  • Fix an issue where clients may (unknowingly) rebind ports/IPs mid-handshake and not be able to complete the handshake.
  • Allow users to configure only_v6 settings through a new Tokio IO API.

What's Changed

Full Changelog: v1.52.1...v1.54.0

v1.52.1

23 Jan 05:36
36fbf86
Compare
Choose a tag to compare

Summary

  • Fixes an issue with IPv4-mapped local addresses causing issues if packets are arriving on both IPv4 and IPv4-mapped spaces.

What's Changed

Full Changelog: v1.52.0...v1.52.1

v1.52.0

07 Jan 23:47
2f357d5
Compare
Choose a tag to compare

Summary

  • Adds a new event, on_connection_close_frame_received. This event contains additional details from the CONNECTION_CLOSE frame received from the peer, particularly the reason the connection closed (if provided).
  • Adds stream batching functionality to s2n-quic sending behavior. Stream batching is a sending strategy which provides each stream with the opportunity to fill up a packet "batch-size" times, before then passing that priority to the next stream.
  • Adds address and connection ID information to the on_datagram_dropped event. NOTE: This is a breaking change if your application stores the DatagramDropped events, as a named lifetime was added to the struct.

What's Changed

New Contributors

Full Changelog: v1.51.0...v1.52.0

v1.51.0

21 Nov 19:11
23df2c5
Compare
Choose a tag to compare

Summary

  • Additional events and visibility for s2n-quic-dc

What's Changed

Full Changelog: v1.50.0...v1.51.0

v1.50.0

12 Nov 01:00
665d3d1
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.49.0...v1.50.0

v1.49.0

04 Nov 22:32
b07c9fd
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.48.0...v1.49.0

v1.48.0

04 Nov 22:31
005f946
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.47.0...v1.48.0

v1.47.0

04 Nov 22:30
2a735a9
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.46.0...v1.47.0

Release v1.46.0

11 Sep 20:57
5d73bf8
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.45.0...v1.46.0