Skip to content

Fix JAXB copy of QUIC preferred address - #255

Open
sean0407 wants to merge 1 commit into
tls-attacker:mainfrom
sean0407:codex/tls-attacker-252-jaxb-preferred-address-20261019
Open

sean0407 wants to merge 1 commit into
tls-attacker:mainfrom
sean0407:codex/tls-attacker-252-jaxb-preferred-address-20261019

Conversation

@sean0407

Copy link
Copy Markdown

Summary

Config.createCopy() serializes and unmarshals configuration through JAXB:

Config.createCopy()
  -> ConfigIO.write()
  -> JAXB unmarshal
  -> PreferredAddress no-arg constructor + InetAddress byte adapter

JAXB could not instantiate PreferredAddress, and its InetAddress properties were not JAXB-compatible. The change adds a no-argument constructor and maps both addresses to their raw bytes for the configuration round trip.

Changed files:

  • TLS-Core/src/main/java/de/rub/nds/tlsattacker/core/protocol/message/extension/quic/QuicTransportParametersExtensionMessage.java
  • TLS-Core/src/test/java/de/rub/nds/tlsattacker/core/config/PreferredAddressConfigCopyTest.java

Fixes #252.

Evidence

  • Before: the focused Config.createCopy() reproduction failed with NoSuchMethodException for PreferredAddress.<init>().
  • After: mvn -o -B -pl TLS-Core -am '-Dtest=PreferredAddressConfigCopyTest,QuicTransportParameterTest' -Dsurefire.failIfNoSpecifiedTests=false test passed (3 tests).

Merge Danger

Door: Two-way

Blast Radius: Low

This changes JAXB mapping for QUIC preferred-address IPv4/IPv6 values in configuration copies. The adapter preserves each address as raw address bytes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Config.createCopy() fails during JAXB deserialization

1 participant