Skip to content
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 certgen in rama-cli #335

Open
GlenDC opened this issue Oct 17, 2024 · 2 comments
Open

support certgen in rama-cli #335

GlenDC opened this issue Oct 17, 2024 · 2 comments
Labels
blocked Tasks which are blocked on other work. low prio Low priority item. needs input

Comments

@GlenDC
Copy link
Member

GlenDC commented Oct 17, 2024

  • generate server / client certs
  • fully self-signed, or by passing it a root (CA)
  • via cli opts and asking input where missing

to be used as rama certgen ...
e.g. rama certgen --out /tmp/localhost.crt --key-out /tmp/localhost.key

To make this work a public API will also need to be made available in rama-tls, to expose generating
certs in a friendly manner, as that's currently only accessible by those services.

@GlenDC GlenDC added low prio Low priority item. easy An easy issue to pick up for anyone. mentor available A mentor is available to help you through the issue. labels Oct 17, 2024
@NOOMA-42
Copy link
Contributor

I'm interested in this. Could you assign me?

@GlenDC GlenDC added needs input blocked Tasks which are blocked on other work. and removed easy An easy issue to pick up for anyone. mentor available A mentor is available to help you through the issue. labels Dec 29, 2024
@GlenDC
Copy link
Member Author

GlenDC commented Dec 29, 2024

Hi @NOOMA-42 normally I would say yes. However a week or two I have realised that the current tls support in Rama needs a complete rework, as it currently has serious limitations and a lot of awkwardness in its UX due to its flawed design.

The gist of it will be that I'm dropping the entire one TLS API to rule them all and instead have rustls and boring live in their own modules or crates isolated from one another. With our core focus on boring.

This will be something for 0.3 however and so until then I think it's better to have a freeze on smaller tls issues like this.

Sorry for the confusion though, didn't update these tls issues after I made this decision a week or two ago.

Feel free to pick something else up though. Or if you don't find something do talk to me on discord, do got some other things in mind that can be done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Tasks which are blocked on other work. low prio Low priority item. needs input
Projects
None yet
Development

No branches or pull requests

2 participants