Skip to content

TLS implementation#74

Open
MrIron-no wants to merge 17 commits intoUndernetIRC:u2_10_12_branchfrom
MrIron-no:tls
Open

TLS implementation#74
MrIron-no wants to merge 17 commits intoUndernetIRC:u2_10_12_branchfrom
MrIron-no:tls

Conversation

@MrIron-no
Copy link
Contributor

No description provided.

entrope and others added 17 commits September 18, 2025 14:53
Add a user mode FLAG_TLS (+z) to indicate users connected via SSL or TLS.
Add a channel mode MODE_TLSONLY (+Z) to only allow +z users to join or
send messages to the channel.
Add configuration settings and features to allow configuration of the
underlying TLS library.

The underlying TLS library is selected by ./configure --with-tls=<NAME>,
among several available implementations (include a stub, "none").  By
design (to make behavior homogenous across a network), very little code
depends on whether TLS is actually available or not.
Add ircd_tls_listen() to configure a TLS listener.  Require this to
succeed on any TLS-enabled listening port.
Delete ircd_tls_fingerprint_matches() in favor of cli_tls_fingerprint.
…the connection. start_auth() is now called from ET_WRITE which immediately return
@eaescob
Copy link

eaescob commented Mar 11, 2026

I wonder if admins would event want to define ciphers. If no ciphers are provided, which ones will ircu default to? Did IRC clients add TLS support post SSLv3? Just trying to understand if we even need the SSLv3 bits.

@MrIron-no
Copy link
Contributor Author

Hi, this introduces S2S too.

@eaescob
Copy link

eaescob commented Mar 11, 2026

Hi, this introduces S2S too.

Yup! Just got to the server part. Edited my comment

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.

3 participants