SSL: Implement SNI #13
Labels
No labels
Compat
Breaking
Discourse migration
Feature
IRCv3
Feature
RFC1459
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: swee/IRCat#13
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently, IRCat and SweeNet would need a wildcard certificate to work with multiple domains (i.e. irc.domain.tld and server.domain.tld)
There's a feature in SSL/TLS that allows clients' handshakes to report what hostname they're trying to connect with, the server can optionally use this information to provide the correct certificate.
Python's built-in
ssl
module already has SNI support since Python 3.7 (fits with our target of Python 3.12) by settingctx.sni_callback
.It can also check if the system's OpenSSL build supports SNI (since 3.2) using
ssl.HAS_SNI
Example code:
Because SNI is only supported in TLS version 1.1 and up, the server has two options for older SSL/TLS versions:
This is also an IRCv3 feature: https://ircv3.net/docs/sni