-
Notifications
You must be signed in to change notification settings - Fork 233
feat: present client certs for outbound SIP TLS mTLS (#530) #776
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
lixuanqun
wants to merge
1
commit into
livekit:main
Choose a base branch
from
lixuanqun:cursor/feat-outbound-mtls-33f3
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Outbound TLS connection can crash when no client identity is configured
An empty result is handed back to Go's TLS client (
return nil, nilatpkg/sip/tls.go:49) when no client identity is configured, so a call placed over an encrypted trunk that asks for a client certificate can crash the service instead of connecting without one.Impact: If this path is ever reached, the process panics during the handshake instead of gracefully continuing without a client certificate.
crypto/tls requires GetClientCertificate to return a non-nil Certificate
Go's documentation for
tls.Config.GetClientCertificatestates the hook must return a non-nil*Certificate; to send no certificate it must return an empty&tls.Certificate{}. Internally the client doescertMsg.certificate = *cert(TLS 1.3) /certMsg.certificates = chainToSend.Certificate(TLS 1.2), which nil-dereferences on a nil return. The default implementation returnsnew(Certificate)for exactly this reason.Today
pkg/sip/service.go:244-254rejects a TLS config with zerocerts, soclientCertsis always non-empty in production, making the branch effectively unreachable — but the helper is exported to the package andpkg/sip/tls_test.go:13-16asserts the nil behaviour, locking in the contract violation for any future caller.Was this helpful? React with 👍 or 👎 to provide feedback.