Skip to content

[AI] Fix: DTLS finishWithCloseNotify override issue (#182) #224

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ic0ns
Copy link
Contributor

@ic0ns ic0ns commented Jun 26, 2025

Summary

Details

The issue occurred because the ProtocolVersionDelegate was unconditionally setting finishWithCloseNotify to true for all DTLS versions, overriding any value set in the configuration file. This made it impossible for users to disable the close notify alert when using DTLS.

The fix is simple: remove the line that sets this value, allowing the configuration file setting to be respected.

Test plan

  • Added unit tests to verify that finishWithCloseNotify configuration is respected for DTLS versions
  • Tests verify that both true and false values are preserved when set in config
  • All existing tests pass
  • Code formatted with spotless

Remove automatic setting of finishWithCloseNotify to true when using -version DTLS* parameter. This allows users to control the finishWithCloseNotify setting via configuration file as intended.
@ic0ns ic0ns changed the title Fix: DTLS finishWithCloseNotify override issue (#182) [AI] Fix: DTLS finishWithCloseNotify override issue (#182) Jun 26, 2025
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.

Issue with defaultServerConnection and finishWithCloseNotify Settings in DTLS
1 participant