Security certificates module #327498
Draft
Security certificates module #327498
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
This module provides a framework for generating certificates from provided "specifications" using one or more "authorities". The specifications are defined in `security.certificates.specifications` while authorities are defined in `security.certificates.authorities`. Specifications, in addition to mostly self explanatory options, have a `authority` option to allow overriding the default authority. It is defined as a `attrTag` where the tag/name indicates the authority to be used and the value is a option defined by the selected authority (the option may itself be a submodule of other options). Authorities are able to define whatever global options they may require within `security.certificates.authorities.<authority>`. They MUST also provide a `settings` option, it's type is irreleveant so long as it does exist. The `settings` option will become the certificate specific options under `security.certificates.specifications.<cert-spec>. \ authority.<authority>`. A default authority and settings are defined under `security.certificates.defaultAuthority` following the same principles as `specifications.authority.<...>.settings`. Signed-off-by: Michael 'ASAP' Weinrich <michael@a5ap.net>
moved certificate specification to seperate file
These scripts will generate the key, csr, and install the final certificate according to the specification.
MadnessASAP
force-pushed
the
security-certificates-module
branch
from
2149c87
to
67d2fda
Compare
MadnessASAP
force-pushed
the
security-certificates-module
branch
from
67d2fda
to
d0b2320
Compare
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.
Description of changes
Provide a framework for runtime generation of TLS certificates using 1 or more interchangeable certificate authorities/services. It allows for services that require certificates to provide a specification and for the user to customize that specification as well as assign a default and per-certificate authority.
All options exist under
security.certificatesand are mostly (well?) documented and relatively straightforward.Currently there is a
localauthority that will generate a root certificate and then issue requested certificates from it, and avaultauthority that will request certificates from a Hashicorp Vault server. Both are WIP with some important features missing. However both are also passing all the tests that I have written (that being the ones I know they pass).Currently a draft as I am at a point where external eyeballs and comments would be greatly appreciated as I start to polish this into something useful.
Things done
Add a 👍 reaction to pull requests you find important.