RSA PKCS#1 v1.5 (signatures)
For RSA PKCS#1 v1.5 (signatures), purpose is digital signature; current status is Approved; planned status is deprecated after 2030 and disallowed after 2035; replacement is ML-DSA (FIPS 204); source document is IR 8547, recorded from its source on 2026-08-16; source re-checked 2026-11-18.
- Algorithm
- RSA PKCS#1 v1.5 (signatures)
- Purpose
- digital signature our reading
- Current status
- Approved our reading
- Planned status
- deprecated after 2030 and disallowed after 2035 our reading
- Replacement
- ML-DSA (FIPS 204) our reading
- Source document
- IR 8547 our reading
Values marked our reading are our classification of what the source says — the source does not print them in those words. The quote below is the evidence for each one; judge it yourself.
Cite as: RSA PKCS#1 v1.5 (signatures) — NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when (NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when), referencesource.org/nist-cryptographic-algorithm-deprecation-schedule/rsa-pkcs-1-v1-5-signatures/, checked 2026-11-18.
What the source says
ECDSA, EdDSA, RSA-PSS, RSA PKCS#1 v1.5), and key-establishment schemes including RSA key transport, elliptic-curve Diffie-Hellman (ECDH), and finite-field Diffie-Hellman.
— encryptionconsulting.com, retrieved 2026-08-16
Source
- encryptionconsulting.comhttps://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/
Open the page on encryptionconsulting.com that states this — the page quoted above, at its publisher. Unpaid: we earn nothing from this link and it is not an advertisement.
Does your own code still call RSA PKCS#1 v1.5 (signatures)? npx crypto-deprecation-check reads the places where naming an algorithm is the point of the line -- createHash, a JWT alg, Cipher.getInstance, MODE_ECB, generateKeyPair, createECDH, an SSH HostKeyAlgorithms setting, an openssl subcommand -- and prints the status we hold for each with this page's sentence quoted. It fails a build only on a status that is already deprecated or disallowed, says nothing at all about algorithms we hold no record for, and makes no network calls. crypto-deprecation-check on npm