Skip to content

Conversation

@mkauf
Copy link

@mkauf mkauf commented Oct 18, 2025

Preserve existing flags (SSL_RECEIVED_SHUTDOWN or SSL_SENT_SHUTDOWN) when calling SSL_set_shutdown().

For abortive or unclean shutdowns, additionally call SSL_set_quiet_shutdown().

Preserve existing flags (SSL_RECEIVED_SHUTDOWN or SSL_SENT_SHUTDOWN) when
calling SSL_set_shutdown().

For abortive or unclean shutdowns, additionally call SSL_set_quiet_shutdown().
@notroj
Copy link
Collaborator

notroj commented Oct 28, 2025

Thanks @mkauf LGTM, is there a user-visible impact for this?

@mkauf
Copy link
Author

mkauf commented Oct 30, 2025

@notroj I think that there is a user-visible impact if "ssl-accurate-shutdown" is used, and the client shuts down the connection first by sending a close notify alert. Previously, mod_ssl would wait for a second close notify alert from the client, ignoring that the client has already sent one.

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.

2 participants