RFC 9579: Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9879.
Current version: 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 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
- RFC9579
- Published
- May 2024
- Authors
- H. Kario
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 15
- Also known as
- —
- Obsoleted by:
- RFC 9879
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
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 9580OpenPGPCurrent
July 2024
- RFC 9578Privacy Pass Issuance ProtocolsCurrent
June 2024
- RFC 9577The Privacy Pass HTTP Authentication SchemeCurrent
June 2024
- RFC 9576The Privacy Pass ArchitectureCurrent
June 2024
- RFC 9588Kerberos Simple Password-Authenticated Key Exchange (SPAKE) Pre-authenticationCurrent
August 2024
- RFC 9593Announcing Supported Authentication Methods in the Internet Key Exchange Protocol Version 2 (IKEv2)Current
July 2024
- RFC 9594Key Provisioning for Group Communication Using Authentication and Authorization for Constrained Environments (ACE)Current
September 2024
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?