Skip to content

Algorithm Support

Signature algorithms

The same set signs and verifies everywhere a signature appears: certificates, CSRs, CRLs, OCSP requests and responses, PKCS#7 SignedData, and detached signatures through micro509/crypto (signData / verifySignature).

AlgorithmSigningVerification
RSA PKCS#1 v1.5yesyes
RSA‑PSSyesyes
ECDSA P‑256yesyes
ECDSA P‑384yesyes
ECDSA P‑521yesyes
Ed25519yesyes

Key formats

FormatImportExportEncrypted
PKCS#8yesyesPBES2 (AES‑CBC + PBKDF2)
SPKIyesyes
JWKyesyes
PKCS#1 (RSA)yesyesLegacy PEM (AES‑CBC)
SEC1 (EC)yesyesLegacy PEM (AES‑CBC)

Encryption

ContextSchemes
Encrypted PKCS#8PBES2 with AES‑CBC + PBKDF2 HMAC‑SHA1 or HMAC‑SHA256
Encrypted PFXPBES2 with AES‑CBC + PBKDF2 HMAC‑SHA1 or HMAC‑SHA256
Legacy encrypted PEMAES‑128‑CBC, AES‑192‑CBC, AES‑256‑CBC
PKCS#12 MACPKCS#12 KDF + HMAC‑SHA‑256
RSA‑OAEPkey encapsulation with SHA‑256/384/512 keys and optional label

Not supported

micro509 does not try to mirror every primitive some WebCrypto runtimes expose:

  • DSA
  • Ed448, X25519, X448 key operations. Certificates carrying them still parse, and RFC 9295 key-usage rules are enforced for all four safe-curve OIDs
  • ECDH and other key agreement
  • Generic symmetric-crypto APIs
  • Brainpool curves

Released under the MIT License.