RFC 9879: Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax
In plain English — editorial summary, not part of the RFC
This document specifies additions and amendments to RFCs 7292 and 8018. It also obsoletes the RFC 9579. It defines a way to use the Password-Based Message Authentication Code 1 (PBMAC1), defined in RFC 8018, inside the PKCS #12 syntax. The purpose of this specification is to permit the use of more modern Password-Based Key Derivation Functions (PBKDFs) and allow for regulatory compliance.
Document record
- Document ID
- RFC9879
- Published
- September 2025
- Authors
- A. Kario
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 16
- Also known as
- —
- Obsoletes:
- RFC 9579
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9216S/MIME Example Keys and CertificatesCurrent
April 2022
- RFC 9881Internet X.509 Public Key Infrastructure -- Algorithm Identifiers for the Module-Lattice-Based Digital Signature Algorithm (ML-DSA)Current
October 2025
- RFC 9882Use of the ML-DSA Signature Algorithm in the Cryptographic Message Syntax (CMS)Current
October 2025
- RFC 9883An Attribute for Statement of Possession of a Private KeyCurrent
October 2025
- RFC 9867Mixing Preshared Keys in the IKE_INTERMEDIATE and CREATE_CHILD_SA Exchanges of the Internet Key Exchange Protocol Version 2 (IKEv2) for Post-Quantum SecurityCurrent
November 2025
- RFC 9891Automated Certificate Management Environment (ACME) Delay-Tolerant Networking (DTN) Node ID Validation ExtensionCurrent
November 2025
- RFC 9865Cursor-Based Pagination of System of Cross-domain Identity Management (SCIM) ResourcesCurrent
October 2025
- RFC 9864Fully-Specified Algorithms for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE)Current
October 2025
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?