Public key crytography glossary of terms for .NET Core developers
November 09, 2020
Big disclaimer: I’m by no means an expert in Cryptography. All these definitions are my own, rewritten from Wikipedia, Stackoverflow and other sources across the internet, geared towards .NET Core usage. If you spot any glaring errors please contact me via Github.
Public key cryptography
It might be a little ambitious to summarise this in one paragraph, but it’s essentially about generating two keys: a public and private key. You keep your private key safe. You distribute your public key, and another person (or you) can encrypt a file or message with it, and then send you the encrypted text or file. You then decrypt this with your private key.
There is also data signing and verification, where you sign or generate a verification code for a file, document, piece of text with your private key. You send somebody the file/document/piece of text, verification code and your public key, and they can check the verification code matches using that public key. This is better illustrated with example code
Public Key Cryptography Standards. These are crytopgraphy standards, with the first versions being in the 90s from RSA, but strangely not starting with PKCS#1. If you look on wikipedia, quite a few of them have been abandonded and the ordering is a bit unusual. The important ones for .NET Core are PKCS#1 (private RSA key), PKCS#8 (the default private key format openssl outputs as), and PCKS#12 (the PFX file format standard)
.PFX file/PFX file format
A binary file format,
.pfx being the file extension. This was originally Microsoft’s own certificate format, that then became a standard via PKCS#12.
If you’re a .NET developer you will find, at some time your life, exporting or importing one of these on Windows - they’re very Windows centric - possibly alongside IIS.
How to convert PFX to PEM files and use the PEM files in .NET Core Wikipedia link
.cert, cer, .crt, .pem, .key files
These are all the same file format, plain text files that contain a public or private key certificate in X509 format, or both. They typically have a header, a footer to match:
-----BEGIN CERTIFICATE----- (base64'd cert here)
For private keys:
-----BEGIN PRIVATE KEY----- (base64'd cert here)
-----BEGIN RSA PRIVATE KEY----- (base64'd cert here)
.key files will typically only contain the private key.
You might find yourself combining many of these when dealing with SSL authority chains, or just combining a public and private key. .NET Core 3.0 doesn’t support loading them in this format, but will in .NET Core 5.
I'm Chris Small, a software engineer working in London. This is my tech blog. Find out more about me via Github, Stackoverflow, Resume