-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Add support for generating ed25519 keys and certs #1061
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1061 +/- ##
==========================================
- Coverage 56.40% 56.28% -0.13%
==========================================
Files 76 76
Lines 7256 7308 +52
==========================================
+ Hits 4093 4113 +20
- Misses 2697 2726 +29
- Partials 466 469 +3
Continue to review full report at Codecov.
|
Hi @lgarofalo ! I'll review this tomorrow ;) |
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.
It might need some changes, as well as adding some other tests. @izolight if you want we can do it together...
Hi @lgarofalo ! I'll go ahead and make these little changes so it can be merged ;) |
@claucece I've addressed some of your questions and updated the pr, |
any hope for this pr moving forward? |
|
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
- | Generic Private Key | c639e67 | initca/testdata/5min-ed25519-key.pem | View secret |
- | Generic Private Key | cf7fb43 | initca/testdata/5min-ed25519-key.pem | View secret |
- | Generic Private Key | ad00b62 | initca/testdata/5min-ed25519-key.pem | View secret |
- | Generic Private Key | bca3df9 | initca/testdata/5min-ed25519-key.pem | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Our GitHub checks need improvements? Share your feedbacks!
Codecov Report
@@ Coverage Diff @@
## master #1061 +/- ##
==========================================
+ Coverage 52.94% 56.23% +3.29%
==========================================
Files 76 76
Lines 9095 7350 -1745
==========================================
- Hits 4815 4133 -682
+ Misses 3813 2745 -1068
- Partials 467 472 +5
|
merged changes from #1097 |
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 for driving this PR forward! I left a few comments and requested changes, but overall this is looking good.
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.
Looks good. I agree with @lukevalenta .
I no longer work at Cloudflare, so I don't have time to check in depth these PRs, but happy to see this work move forward.
Co-authored-by: Luke Valenta <lvalenta@cloudflare.com>
@nickysemenza this PR looks good to me but I lack permissions to approve. Would you be able to add this to your review queue? |
Is this going to make a release sometime soon? It was confusing as hell to spend the last two hours wondering why I couldn't generate a ed25519 key when your csr.go file pretty clearly shows a case match on it, to see the original request for support was from five years ago, then to finally look at the date on this merge and the date of the last release and realize you haven't released since April. I'm perfectly willing to build from main and give it a whirl, but man, maybe merge the website updates from three and a half years ago: #1095 Not a great experience to spend all this time digging through your source code because there's no documentation only to find out the source code doesn't actually match the latest release. I know it's a free tool so honestly I apologize if this sounds harsh. Dealing with demanding jackasses on Github can be a pain, so honest to God, I've gotten a ton out of Cloudflare knowledge base material in general in the past and I really do appreciate it. This toolsuite is still a heck of a lot less inscrutable than openssl and at least the source code is very readable. |
It is now possible to generate ed25519 keys and certificates by specifying ed25519 as algo in the json.
This should fix #926