Skip to content
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

ircd/listener: return a fatal TLS alert for early rejected TLS clients #412

Merged
merged 1 commit into from
Nov 7, 2023

Conversation

aaronmdjones
Copy link
Member

This is in furtherance of commit 3fdf26a which added functionality to reply with a TLS record layer alert for D-Lined TLS clients. It turns out that there are other plaintext error messages in this same function that should receive the same treatment.

Also move another error string to a variable and use a compile-time optimised-out strlen for it too, to use the same approach as an existing error string.

ircd/listener.c Outdated Show resolved Hide resolved
ircd/listener.c Show resolved Hide resolved
@aaronmdjones aaronmdjones force-pushed the amdj/rejectcache-tls-alert branch 2 times, most recently from 764eef4 to beecb81 Compare July 1, 2023 18:23
ircd/reject.c Show resolved Hide resolved
This is in furtherance of commit 3fdf26a which added
functionality to reply with a TLS record layer alert for D-Lined TLS
clients. It turns out that there are other plaintext error messages
in this same function that should receive the same treatment.

Also move another error string to a variable and use a compile-time
optimised-out strlen for it too, to use the same approach as an
existing error string.

Finally, use a different alert (internal_error) for the case where
IRCd is simply unable to accept more connections.
@aaronmdjones aaronmdjones merged commit 642c73d into main Nov 7, 2023
9 checks passed
@aaronmdjones aaronmdjones deleted the amdj/rejectcache-tls-alert branch November 7, 2023 23:52
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.

4 participants