-
Notifications
You must be signed in to change notification settings - Fork 78
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
Support Multiple Key Types #901
Comments
Thanks. In the latest release, I think you could use |
Yea thats the idea, get the key/cert and create a Some ConfigTls::AsBytes. I didn't go the ConfigTls::Dynamic route as it looked like that was maybe looking for its own TLS handler... but I could misunderstanding the usage. |
Dropshot always constructs a dropshot/dropshot/src/server.rs Line 481 in 59f102e
dropshot/dropshot/src/server.rs Lines 483 to 537 in 59f102e
So if you need a workaround, you can make your own #902 still seems worth doing. I just wanted to let you know in case this unblocks you. |
Closing this because I think you can do this today with |
Currently Dropshot ConfigTls expects a key that matches Item::Pkcs8Key. Some certificate authorities do not provide a key pair that matches this.
A concrete example is using a key pair obtained from tailscale cert. Today the only key proved by tailscale is an EC key.
The text was updated successfully, but these errors were encountered: