bk99.de entertain the web since 1997

bk99.de
RFC · CryptographyStandard explained

RFC 9580: OpenPGP modernised

Summary

RFC 9580 renews the OpenPGP standard with modern algorithms, clearer packet formats and revised security rules. Long-lived cryptographic formats have to actively shed legacy baggage. Interoperability covers data format, algorithm choice and key maintenance.

Ideas

  • OpenPGP combines public keys, signatures and symmetric encryption.
  • New AEAD methods protect confidentiality and integrity together.
  • Fingerprints identify keys more stably.

Facts

  • RFC 9580 replaces RFC 4880.

Remarks

  • RFC 9580 has the status “Proposed Standard”; current errata and successor documents should also be checked.

Recommendations

  • Prefer implementations with RFC 9580 support.
  • Migrate old keys and weak algorithms in a planned way.

References

Read the RFC at the RFC Editor

Search the Web Archive

RFC · 2026

RFC 9958: Post-quantum cryptography for practitioners

RFC 9958 explains to engineers the properties, transition risks and deployment patterns of post-quantum cryptography. Cryptographic migration starts long before quantum attacks are practically available. Harvest-now-decrypt-later makes data that must stay confidential for a long time relevant today.

RFC · 2023

RFC 9420: Messaging Layer Security

RFC 9420 defines MLS for efficient end-to-end encryption in dynamic groups. Group encryption is more than pairwise encryption between many participants. Removed members must lose future access cryptographically.

RFC · 2021

RFC 9106: Argon2 for password hashing

RFC 9106 describes Argon2 as a memory-hard password derivation function and gives recommendations for secure parameters. Every implementation compliant with RFC 9106 must support Argon2id; Argon2d and Argon2i are optional. For password hashing, the RFC recommends an individual salt 16 bytes long.