| 1 |
Limited local-only support, helpers for external IPA and certmaster-based CAs. |
| 2 |
Keys can also be self-signed. |
| 3 |
|
| 4 |
Complete: |
| 5 |
* Generating RSA keys of configurable size. |
| 6 |
* Storing keys in either PEM or NSSDB format. |
| 7 |
* Generating signing requests for keys in PEM or NSSDB format. |
| 8 |
* Self-sign requests using keys in PEM or NSSDB format. |
| 9 |
* Save issued certificate in PEM or NSSDB format. |
| 10 |
* Refresh certificate parameters from the certificates at startup, |
| 11 |
parsing and recovering fields and extensions that we care about to refresh |
| 12 |
the request tracking file (key usage, extended key usage, subject alt name |
| 13 |
of type email, dns, or kerberos/nt principal name). |
| 14 |
* Populate requested-extensions in signing requests with as much |
| 15 |
information as we can. |
| 16 |
* Locally-signed certificates use the requested extension values. |
| 17 |
* Locally-signed certificates get a configured validity lifetime. |
| 18 |
* Locally-signed certificates get a somewhat-useful serial number. |
| 19 |
* Locally-signed certificates are marked as not being CAs. |
| 20 |
* Maintaining queued items in an upgrade-proofable format. |
| 21 |
* Should offer an API over D-Bus which the client uses instead of |
| 22 |
mutilating the queue directly (see doc/api.txt): |
| 23 |
* Add new entry. Figure out the state based on what the requester supplies |
| 24 |
(i.e., if there's a certificate where the request says it should go, |
| 25 |
assume it's been issued; ditto for private keys). |
| 26 |
* List entries. |
| 27 |
* List known CAs. |
| 28 |
* Resubmit requests after generating a new signing request. |
| 29 |
* Provide introspection data as a well-behaved D-Bus service would. |
| 30 |
* D-Feet seems to be happy. |
| 31 |
* Start and stop tracking (i.e., notification of expiration). |
| 32 |
* Make certmonger a proper daemon. |
| 33 |
* Detach from console, foreground for debugging. |
| 34 |
* Sort out an init script. |
| 35 |
* Sort out storage for system-local defaults which are consulted |
| 36 |
before falling back to compiled-in defaults. |
| 37 |
* Actually do notification of expiration and impending expiration. |
| 38 |
* Learn to exec a helper to do non-local enrollment. |
| 39 |
* Detect when network connections go up and "kick" anything that's |
| 40 |
waiting for a server to become reachable. |
| 41 |
* Learn to submit to at least one actual CA: IPA via XML-RPC over |
| 42 |
HTTPS, authenticating using Negotiate with creds obtained using |
| 43 |
the host's keytab (administrator may have logged off long before |
| 44 |
we could have contacted the CA). |
| 45 |
* Learn to submit to a second CA: certmaster via XML-RPC over HTTP. |
| 46 |
* Learn how certmaster's root gets distributed. It doesn't. |
| 47 |
* Learn to submit to certmaster's XMLRPC interface, preferably by |
| 48 |
calling out to the python library it supplies. Ended up reusing |
| 49 |
large chunks of the IPA client code, so it's in C. |
| 50 |
* Handle PIN values for encrypted key storage. |
| 51 |
* Be able to use hashes other than SHA256. |
| 52 |
* Make certmonger a proper daemon. |
| 53 |
* Sort out SELinux policy. (unscoped) |
| 54 |
* Figure out how to let the local deamon's client do key generation. |
| 55 |
It's either that or force them to give the daemon the PIN for |
| 56 |
encrypted storage. Or don't support encrypted key storage at all, |
| 57 |
which is probably not going to be a popular limitation to have. (3 days) |
| 58 |
DROPPED in favor of giving the daemon the PIN for encrypted storage. |
| 59 |
* Offer an API over D-Bus which the client can use instead of |
| 60 |
mutilating the queue directly (per doc/api.txt). |
| 61 |
* Generate an SPKAC value when generating PKCS#10 CSRs. |
| 62 |
* Put NSS into FIPS mode. |
| 63 |
* Offer to store certificates for CAs and their intermediates, potentially in |
| 64 |
multiple certificate databases and PEM files. |
| 65 |
* Local signing should support signing with a key other than the one |
| 66 |
used to generate the CSR. |
| 67 |
* Add an option to getcert to specify a challenge password and a friendly |
| 68 |
name to add to a CSR. |
| 69 |
* Learn to generate SCEP messages. |
| 70 |
* Learn to parse SCEP responses. |
| 71 |
* Display timestamps in local time rather than UTC, unless a --utc flag is |
| 72 |
specified. |
| 73 |
|
| 74 |
To-do: |
| 75 |
* Also generate a CRMF request (RFC 4211) when we generate CSRs. Not sure |
| 76 |
if we can do this as easily with PEM keys as OpenSSL doesn't appear to |
| 77 |
offer APIs for it, and I don't want to just break if the PEM module's not |
| 78 |
available. (more research needed) |
| 79 |
* Make certmonger a proper daemon. |
| 80 |
* Sort out logging levels for log messages. (1 day) |
| 81 |
MUST |
| 82 |
* Local signing should track a revocation list for each signing key |
| 83 |
and maintain a CRL for it. (3 days) |
| 84 |
COULD |
| 85 |
* Learn to handle keys and certificates stored in files in virtual |
| 86 |
guests of the current OS instance (using libguestfs). Would need |
| 87 |
to refactor some of the current storage code to to it for "file". |
| 88 |
Not at all sure how to do it for "nssdb". |
| 89 |
COULD |
| 90 |
* Learn to "handle" keys and certificates stored in PKCS12 bundles. |
| 91 |
COULD |
| 92 |
* Learn to handle keys and certificates stored in PKCS11 modules directly. |
| 93 |
COULD |
| 94 |
* Queue management. |
| 95 |
COULD -> Move entries and CAs from hand-rolled files to simple XML. (2 days) |
| 96 |
COULD -> Move them to JSON. (2 days) |
| 97 |
COULD -> Move them to an ldb. (3 days) |
| 98 |
COULD -> Move them to something that's more end-user-serviceable. (3 days) |
| 99 |
- IPA mucks with our files directly in their current form, so this is |
| 100 |
tabled indefinitely. |
| 101 |
* Lighten build requirements by crafting and parsing XML-RPC ourselves |
| 102 |
since we already have to deal with non-XML-RPC XML and HTTP for Dogtag. |
| 103 |
* Add IDENTIFY operations to helpers, so they can output their |
| 104 |
preferred/default name, and we can cache root and intermediate chain |
| 105 |
certificates from CAs which provide a way for clients to retrieve them via |
| 106 |
an integrity-checked path. |
| 107 |
* Populate/update the known-issuer-names list for the CA using these. |
| 108 |
* Cache the authorityKeyIdentifier and/or subjectPublicKeyIdentifier from |
| 109 |
the CA certificate, and use that to match up certificates that need to be |
| 110 |
renewed with their CAs. |
| 111 |
* If the CA cert includes a CRL distribution point extension, cache the |
| 112 |
CRL, too. This'll require a new dependency on a retrieval library |
| 113 |
(probably libcurl again) and changes to the internal state machine to |
| 114 |
handle CRL retrieval as another type of task. The local signer's CRL |
| 115 |
would be regenerated before being "retrieved". |
| 116 |
* More on this in "doc/submit.txt". |
| 117 |
* Add a GET_NEW_REQUEST_REQUIREMENTS operation to helpers so that they can |
| 118 |
list variables which the daemon should supply for them for it to note, so |
| 119 |
that if they're not specified by a client, we can intelligently decide |
| 120 |
whether or not they're actually required to be specified for a given CA, |
| 121 |
rather than sloppily hard-coding it as we do now. |
| 122 |
* Learn about using SRV records for locating servers, particularly KCA ones. |
| 123 |
* Learn to talk to KCAs (RFC 6717) |
| 124 |
* Learn to speak CMP (see http://marc.info/?l=openssl-dev&m=137535536301203) |
| 125 |
* Learn to talk to puppet CAs. |
| 126 |
* Check in with awnuk, who's been looking at this combination. |
| 127 |
* Learn to talk to r509 CAs. |
| 128 |
* Switch to SSL access methods when submitting end-entity requests to Dogtag |
| 129 |
CAs (profileSubmit, checkRequest, displayCertFromRequest). |
| 130 |
* Be able to fill requester contact info when submitting end-entity |
| 131 |
enrollment requests, particularly for cases when we don't have agent |
| 132 |
credentials, and make that a client-suppliable value. |
| 133 |
* Stamp "approved by certmonger $version", or something, on certificates, |
| 134 |
to help identify certificates that we approve with agent credentials. |
| 135 |
* Learn to read and create RFC3820 ProxyCertInfo extensions. |
| 136 |
* Learn to speak ACME (see https://github.com/letsencrypt/acme-spec). |
| 137 |
* Learn to sign messages as needed by ACME using a request's private key. |
| 138 |
* Learn to read and create NameConstraints extensions. |
| 139 |
* Correctly mark randomly-generated UUID values as version 4, per RFC4122. |
| 140 |
* Add "profiles" of some kind to the local signer. |
| 141 |
* Support RSA-PSS signing. |
| 142 |
* Support a post-failure hook, much as we do a post-success hook now. |
| 143 |
* Expose notification settings in getcert. |
| 144 |
* Add some smaller TTL thresholds to the default list. |
| 145 |
* Make TTL thresholds overridable on a per-certificate basis. |
| 146 |
* Learn to talk to anchor (https://github.com/openstack/anchor) CAs. |