8000 Explain certificate chains and signing by sensomatic · Pull Request #2 · sensomatic/sql-docs · GitHub
[go: up one dir, main page]

Skip to content

Explain certificate chains and signing#2

Open
sensomatic wants to merge 1 commit intopatch-1from
sensomatic-pki-patch1
Open

Explain certificate chains and signing#2
sensomatic wants to merge 1 commit intopatch-1from
sensomatic-pki-patch1

Conversation

@sensomatic
Copy link
Owner

Some points that needed clarifying

  • Certificates always contain signatures and public keys. "Often used as containers for asymmetric keys" is somewhat misleading or at least is not very informative
  • The note on key length and "two methods for the cryptographic algorithm" is out of context, and it is difficult to gauge the meaning even for someone knowledgeable in the subject
  • Technically it is the key, either private or public, that is used to encrypt, not the certificate itself.
  • Public keys do have different formats and can be exported to file. The statement contrary to this is incorrect and doesn't add to the discussion so I removed it. You can export a public key from a certificate to file.
  • x509 does not include any private keys in the certificate. The statement that the certificate can optionally include a private key is incorrect in this context.

Some points that needed clarifying
- Certificates always contain signatures and public keys. "Often used as containers for asymmetric keys" is somewhat misleading or at least is not very informative
- The note on key length and "two methods for the cryptographic algorithm" is out of context, and it is difficult to gauge the meaning even for someone knowledgeable in the subject
- Technically it is the key, either private or public, that is used to encrypt, not the certificate itself.
- Public keys do have different formats and can be exported to file. The statement contrary to this is incorrect and doesn't add to the discussion so I removed it. You can export a public key from a certificate to file.
- x509 does not include any private keys in the certificate. The statement that the certificate can optionally include a private key is incorrect in this context.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0