[smime] [Errata Verified] RFC5083 (8356)
RFC Errata System <rfc-editor@rfc-editor.org> Wed, 02 April 2025 16:40 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: smime@ietf.org
Delivered-To: smime@mail2.ietf.org
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D594D1685316; Wed, 2 Apr 2025 09:40:45 -0700 (PDT)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 9022A20B1F7; Wed, 2 Apr 2025 09:40:45 -0700 (PDT)
To: rdonchen@outlook.com, housley@vigilsec.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20250402164045.9022A20B1F7@rfcpa.rfc-editor.org>
Date: Wed, 02 Apr 2025 09:40:45 -0700
Message-ID-Hash: A7NJCESJQ657WR2BB7ZTXN2YO55R5DJL
X-Message-ID-Hash: A7NJCESJQ657WR2BB7ZTXN2YO55R5DJL
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-smime.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-ed@rfc-editor.org, iesg@ietf.org, smime@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [smime] [Errata Verified] RFC5083 (8356)
List-Id: SMIME Working Group <smime.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/y_-Msu4dT2COFCkRqDYAhTVxYYA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/smime>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Owner: <mailto:smime-owner@ietf.org>
List-Post: <mailto:smime@ietf.org>
List-Subscribe: <mailto:smime-join@ietf.org>
List-Unsubscribe: <mailto:smime-leave@ietf.org>
The following errata report has been verified for RFC5083, "Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8356 -------------------------------------- Status: Verified Type: Editorial Reported by: Roman Donchenko <rdonchen@outlook.com> Date Reported: 2025-03-30 Verified by: RFC Editor Section: 3 Original Text ------------- generation of public/private key pairs relies on a random numbers. Corrected Text -------------- generation of public/private key pairs relies on random numbers. Notes ----- A simple typo. -------------------------------------- RFC5083 (draft-ietf-smime-cms-auth-enveloped-06) -------------------------------------- Title : Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type Publication Date : November 2007 Author(s) : R. Housley Category : PROPOSED STANDARD Source : S/MIME Mail Security Stream : IETF
- [smime] [Errata Verified] RFC5083 (8356) RFC Errata System
- [smime] Re: [Errata Verified] RFC5083 (8356) Sean Turner