-
Notifications
You must be signed in to change notification settings - Fork 7
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
QUESTION: commands to generate new certificates #83
Comments
UPDATE: generate EC Keyopenssl ecparam -name prime256v1 -genkey -noout -out issuer-ec-key.pem convert the ec format pem from traditional pem to PKCS8 pem formatopenssl pkcs8 -topk8 -in issuer-ec-key.pem -nocrypt -out issuer-key.pem generate the certificate using the generated keyopenssl req -new' -x509 '-key' issuer-key.pem -subj '/CN=Issuer' -out issuer-cert.pem |
Hi Warren, certificates are used for issuer authentication upon presentation of an mDL. This allows a verifier to establish that the mDL comes from a valid authority. Creating certificates that comply with the ISO 18013-5 specification requires a specific configuration, which is detailed in this document: Nevertheless, here is a sequence of commands that you can use to create a root certificate and use that to sign a signer certificate that you can use with isomdl. Preparation
-> fill in your configuration files Root CertificateCreate an EC key pair 'ca.key': Generate a 'root' certificate that is valid for one year: Verify the contents: Signer CertificateCreate an EC key pair 'signer.key: Generate a Certificate Signing Request (.csr): Generate certificate: Verify the contents: Certificate support in this crate is definitely something we are looking to work on. Until that time, I hope this helps! |
What openssl (or other) commands are required to generate new files:
issuer-cert.pem
issuer-key.pem
device_key.b64
Here is my best guess for issuer-cert and issuer-key:
openssl req -new -newkey ec -pkeyopt ec_paramgen_curve:prime256v1 -x509 -sha256 -subj "/CN=Issuer" -nodes -days 365 -out issuer-cert.pem -keyout issuer-private-key.pem
The text was updated successfully, but these errors were encountered: