-
Notifications
You must be signed in to change notification settings - Fork 7
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
chore: prefer publicKey
over pemCSR
in API
#143
Conversation
with open(ca_filename, "w+") as ca_out: | ||
ca_out.write("".join(cert_chain)) | ||
with open(cert_chain_filename, "w+") as chain_out: | ||
chain_out.write("".join(full_chain)) | ||
chain_out.write("".join(cert_chain)) |
Check failure
Code scanning / CodeQL
Clear-text storage of sensitive information
with open(ca_filename, "w+") as ca_out: | ||
ca_out.write("".join(cert_chain)) | ||
ca_out.write(ca_cert) |
Check failure
Code scanning / CodeQL
Clear-text storage of sensitive information
publicKey
over pemCSR
in API
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.
LGTM
Can we disable the false-positive lint errors?
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.
Thanks Jack, LGTM
@enocom its nots part of the lint its part of the security scan. I've already marked them as false positives so they won't show up in future PRs I believe. Should be good. |
Prefer
publicKey
overpemCSR
in API request body.Will follow up after this PR with #14 to make key generation async and non-blocking
Closes #110