-
Notifications
You must be signed in to change notification settings - Fork 21
Add TLS support for RPC/CLI #92
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
Conversation
|
🎉 This PR is now ready for review! |
|
🔔 1st Reminder Hey @tnull! This PR has been waiting for your review. |
| Ok(PrivateKeyDer::Pkcs8(der.into())) | ||
| } | ||
|
|
||
| /// Generates a self-signed TLS certificate and saves it to the storage directory. |
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.
Do we also want to support non-self-signed certificates, i.e., if users would for example use Lets Encrypt? Or out-of-scope for now and we'll just support mandatory local self-signed certificates?
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.
yeah i think out of scope for now, would be a good feature for the future though
With TLS we can now have encrypted communication with the client and server. We auto generate a self signed cert on startup. Co-Authored-By: Claude Opus 4.5 <[email protected]>
Built on top of #88 to reduce conflicts
With TLS we can now have encrypted communication with the client and
server. We auto generate a self signed cert on startup.
Co-Authored-By: Claude Opus 4.5 [email protected]