-
Notifications
You must be signed in to change notification settings - Fork 31
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
New x509 command #74
Comments
jhunt
added a commit
that referenced
this issue
Mar 14, 2017
The `safe x509` command (and all of its sub-commands) now allow flexible creating, verification, and revocation of x.509 (TLS/SSL) certificates. This new set of commands supports arbitrarily-deep certificate authorities, painless self-signed certificates, and more. In time, this will replace the `pki`, `cert`, `revoke`, `crl-pem` and `ca-pem` commands as we move away from the Vault `pki/` backend. Fixes #74.
jhunt
added a commit
that referenced
this issue
Mar 15, 2017
The `safe x509` command (and all of its sub-commands) now allow flexible creating, verification, and revocation of x.509 (TLS/SSL) certificates. This new set of commands supports arbitrarily-deep certificate authorities, painless self-signed certificates, and more. In time, this will replace the `pki`, `cert`, `revoke`, `crl-pem` and `ca-pem` commands as we move away from the Vault `pki/` backend. Fixes #74.
jhunt
added a commit
that referenced
this issue
Mar 15, 2017
The `safe x509` command (and all of its sub-commands) now allow flexible creating, verification, and revocation of x.509 (TLS/SSL) certificates. This new set of commands supports arbitrarily-deep certificate authorities, painless self-signed certificates, and more. In time, this will replace the `pki`, `cert`, `revoke`, `crl-pem` and `ca-pem` commands as we move away from the Vault `pki/` backend. Fixes #74.
jhunt
added a commit
that referenced
this issue
Mar 15, 2017
The `safe x509` command (and all of its sub-commands) now allow flexible creating, verification, and revocation of x.509 (TLS/SSL) certificates. This new set of commands supports arbitrarily-deep certificate authorities, painless self-signed certificates, and more. In time, this will replace the `pki`, `cert`, `revoke`, `crl-pem` and `ca-pem` commands as we move away from the Vault `pki/` backend. Fixes #74.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Build a new command set,
safe x509
for dealing with x509 PKI certificate stuff, without being constrained by the limitations of thepki
backend in Vault.This new command should allow us to issue new certificate authorities, storing the certificate and key somewhere under
secret/
, and also use those CAs (identified by path) to sign other certificates and store them in under other arbitrary paths undersecret/
.We should allow the special cases of self-signed certificates and intermediary CAs.
The point of this new command is to expose as much raw functionality as possible for setting up complicated PKI implementations as possible. In part, this replaces
safe {pki,cert,ca-pem,crl-pem,revoke}
A future command will be introduced to provide a more simplified interaction for zone-based authority domains like those found in Cloud Foundry. That command will use backend logic that we build out for thex509
command (but not call front-end commands directly)Example invocations:
For certificate authorities, the following attributes should be set on the CA path:
safe x509
)For non-CA certificates, the following attributes should be set on the certificate path:
The text was updated successfully, but these errors were encountered: