-
Notifications
You must be signed in to change notification settings - Fork 27
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
Inlcude challenge password attribute if required by EST server #34
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ecoverer Fix logging call in recoverer
…ists Outdent doc comment lists
…ents Code quality enhancements
Update to version 1.0.2.
Release version 1.0.2.
…tput Break base64 HTTP messages into lines.
…ontent-types Support more error content types.
`rootOutFlag` is just a boolean flag and does not accept a path. Signed-off-by: Ievgen Popovych <[email protected]>
…athFmt-from-rootOutFlag cmd: estclient: flags: Remove path formatting from rootOutFlag
This implements filtering of CA certificates - using one of `roots` or `intermediates` flags allows the user to output only root or intermediate CA certificates respectively. In contrast with `rootout` flag, `roots` flag also supports outputting multiple root certificates. `rootout` flag is now deprecated and will be removed in favor of `roots` in the future. Signed-off-by: Ievgen Popovych <[email protected]>
It is often required to have every CA certificate in its own file, so instead of splitting them manually (which is clunky) - provide this option. A new flag, `separate`, enables this mode. It is possible to set filename prefix with `out` flag. Files are written in a format `<prefix>-<index>.pem`, `ca` is the default prefix, prefix can also end with `.pem`.
…dual-file-per-ca cacerts - support individual file per CA, more flexible filtering
Updated installation instructions
Next: find a workaround
Next : try another go package
… argument type so that we don't depend on x509 package anymore, which today still ignores the challenge password attribute
- Update readme and documentation
Features/expose tlsunique
There has been a |
PR is closed : once the PR is "clean" enough, new PR will be created. |
Thank you for the contribution, yes a cleaner version would be great :)! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The changes introduced come after an issue/feature request has been opened.
They allow us to enroll a CSR that includes the TLS-unique value as recommended by the RFC 7030