[Cfrg] RFC 8937 on Randomness Improvements for Security Protocols
rfc-editor@rfc-editor.org Sat, 17 October 2020 12:34 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72E6B3A0AE8; Sat, 17 Oct 2020 05:34:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ugvtrzpB6Ioc; Sat, 17 Oct 2020 05:34:05 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE4993A0AE6; Sat, 17 Oct 2020 05:34:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7F563F406F4; Sat, 17 Oct 2020 05:33:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, cfrg@irtf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20201017123343.7F563F406F4@rfc-editor.org>
Date: Sat, 17 Oct 2020 05:33:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/giIT8WSBVALjf9DptNpqaSmCRkg>
Subject: [Cfrg] RFC 8937 on Randomness Improvements for Security Protocols
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Oct 2020 12:34:11 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8937
Title: Randomness Improvements for Security Protocols
Author: C. Cremers,
L. Garratt,
S. Smyshlyaev,
N. Sullivan,
C. Wood
Status: Informational
Stream: IRTF
Date: October 2020
Mailbox: cremers@cispa.saarland,
lgarratt@cisco.com,
svs@cryptopro.ru,
nick@cloudflare.com,
caw@heapingbits.net
Pages: 9
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-irtf-cfrg-randomness-improvements-14.txt
URL: https://www.rfc-editor.org/info/rfc8937
DOI: 10.17487/RFC8937
Randomness is a crucial ingredient for Transport Layer Security (TLS)
and related security protocols. Weak or predictable
"cryptographically secure" pseudorandom number generators (CSPRNGs)
can be abused or exploited for malicious purposes. An initial entropy
source that seeds a CSPRNG might be weak or broken as well, which can
also lead to critical and systemic security problems. This document
describes a way for security protocol implementations to augment
their CSPRNGs using long-term private keys. This improves randomness
from broken or otherwise subverted CSPRNGs.
This document is a product of the Crypto Forum Research Group (CFRG)
in the IRTF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
https://www.irtf.org/mailman/listinfo/irtf-announce
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC