I'm reading up the source code ca.create() where a self-signed certificate is created. It basically consists of 3 steps:
generate a keypair
create a csr
sign the csr with its own key
I wonder if it might make sense to refactor the code (2nd point above) into the csr module so that one can call csr.create_csr() to create a csr with the specified private key in the device.
Typical use cases are: cross signing and an intermediate CA.
For the cross signing scenario, e.g. when the CA is created, there is no intention to have the root CA to be signed by another CA. Thus, the csr returned by ca.create() may not be saved. However, 5 years later, the new situation warrants a cross signing and at that point, a csr.create_csr() function would be useful to re-create the csr.
Hi again. :)
I'm reading up the source code
ca.create()
where a self-signed certificate is created. It basically consists of 3 steps:I wonder if it might make sense to refactor the code (2nd point above) into the
csr
module so that one can callcsr.create_csr()
to create a csr with the specified private key in the device.Typical use cases are: cross signing and an intermediate CA.
For the cross signing scenario, e.g. when the CA is created, there is no intention to have the root CA to be signed by another CA. Thus, the csr returned by
ca.create()
may not be saved. However, 5 years later, the new situation warrants a cross signing and at that point, acsr.create_csr()
function would be useful to re-create the csr.Just my 2 cents. Thanks for the great package!