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.

Sign up for GitHub

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

Jump to bottom

Expose the CA's private key #27

Closed
thedrow opened this issue Feb 21, 2018 · 1 comment · Fixed by #31
Closed

Expose the CA's private key #27

thedrow opened this issue Feb 21, 2018 · 1 comment · Fixed by #31

Comments

@thedrow
Copy link

thedrow commented Feb 21, 2018

The CA's private key is required for tasks like creating a TLS secret in Kubernetes (if I understand correctly).
See https://github.com/jetstack/cert-manager/blob/master/docs/user-guides/ca-based-issuer.md for example.
@njsmith
Copy link
Member

njsmith commented Feb 21, 2018

Sure, fair enough, should be pretty easy. I don't have a use case or spare time this week so probably won't do it myself, but happy to accept PRs.

pquentin referenced this issue in pquentin/trustme Aug 11, 2018
@pquentin
Expose CA private key
5e04e49 
Closes #27. To avoid generating a new CA each time, we first need to
export its private key.
pquentin referenced this issue in pquentin/trustme Aug 11, 2018
@pquentin
Expose CA private key
4ce4f25 
Closes #27. To avoid generating a new CA each time, we first need to
export its private key.
@pquentin pquentin mentioned this issue Aug 11, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Expose CA private key pquentin/trustme
2 participants
@thedrow @njsmith