Skip to content

cryptosense/key-parsers

Repository files navigation

key-parsers

Build Status

Key-parsers offers parsers and printers for various asymmetric key formats.

Key_parsers

It currently comes with four submodules.

Asn1

Note that all the parsers in this module expect the raw DER encoded byte string. They don't handle PEM armoring (----BEGIN X---- and ----END X----) nor decode Base64 or hex.

Here you can find parsers for the following formats:

  • PKCS#1 encoding of RSA Private and Public keys as defined in PKCS#1 v2.2
  • PKCS#8 encoding of RSA, DSA, EC and DH Private keys as defined in RFC 5208
  • X.509 SubjectPublicKeyInfo encoding of RSA, DSA, EC and DH Public keys as defined in RFC 5280
  • DER encodings of DSA, EC and DH Parameters and Private keys as produced by OpenSSL commands such as dsaparam and gendsa

Pgp

Parsers for PGP (Pretty Good Privacy) encodings of DSA, RSA and Elgamal Public and Private keys and user IDs as defined in [RFC 4880] (https://datatracker.ietf.org/doc/html/rfc4880) Note that the parsers in this module expect raw byte string. They don't handle PEM armoring nor decode Base64 or hex.

Ltpa

Parsers for LTPA (Lightweight Third Party Authentication) encodings of RSA private and public keys.

Cvc

Parsers for CVC (Card Verifiable Certificates) encodings of RSA and EC Public keys.

Make a new version

Check that the changelog is up to date.

Create an annotated tag with the new version:

git tag --message 'Version 1.2.3' 1.2.3

Then, use dune-release:

dune-release distrib
dune-release check
dune-release publish
dune-release opam pkg
dune-release opam submit

The command dune-release bistro can do all of that in one invocation but can be more confusing if you're not used to dune-release.