We are expanding our previous experiment to include people who posses PGP keys hosted at certain domains. For now we are whitelisting Keybase.io, meaning if you have a Keybase PGP key it can be used to procure a trust anchor certificate via the Certisfy app.
It should be noted that this is strictly experimental, meaning most certificates will likely at some point be suspended or out right revoked if it seems they are being used to issue untrustworthy certificates.
The allowance of Keybase is not ideal since there is no id proofing and there is no reason to assume the person behind the Keybase key is a suitable trust anchor. It is however something used by folks interested in cryptographic solutions related to internet trust and security, so at least for experimentation it is appropriate.
To validate a certificate request with your Keybase PGP key, first use your Keybase key to sign the following text (no trailing or leading spaces):
Using public key hosted at ${PGPPubkeyURL}, I am requesting a Certisfy trust anchor certificate. I promise to act in good faith as a Certisfy trust anchor partner.
Replace the place holder ${PGPPubkeyURL} with the full url to your Keybase public key. The output signature must be text, ie the gpg equivalent of --textmode option.
Once you have a signature, follow this process to acquire a certificate:
- Create a trust anchor document (simple name/value pair) via the Certisfy app.
- Generate a certificate request (CSR) via the Certisfy app.
- Submit the request with PGP Signature selected as your validation type.
- If validation is successful, you will be able to download (via the Certisfy app) a trust anchor certificate that you can then use to issue (via the Certisfy app) trustworthy certificates.
Comments
Post a Comment