IETF Logo Mail Archive

[lamps] Semi-OT: crypto code in RFCs

"John Levine" <johnl@taugh.com> Thu, 03 May 2018 01:31 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCF4412D777 for <spasm@ietfa.amsl.com>; Wed, 2 May 2018 18:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level:
X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=H6RJfvxl; dkim=pass (1536-bit key) header.d=taugh.com header.b=kb6j9BCH
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 nRMeNpnwB5wL for <spasm@ietfa.amsl.com>; Wed, 2 May 2018 18:31:50 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5DD4127599 for <spasm@ietf.org>; Wed, 2 May 2018 18:31:50 -0700 (PDT)
Received: (qmail 16437 invoked from network); 3 May 2018 01:31:49 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=4032.5aea6685.k1805; bh=c0B7wRt8CzBMm07bOdvmpqG7SNxzT9Ss3dg06XxIPmY=; b=H6RJfvxlc7elJFfSrqvdMdU6SQzda64KfgWAxEQjl0YzzqXZGb42IUAJppoIS7RLS6whZUcgclXAt8R+k4QCnjXLP+wqfGNEDbbJtbvmkgukZKxSgiqqbF+WzucPMbcmV+0GfVXjc3iUF5zIfVdi9Rrj/cs4Iymdz5UzZkQYAjzJI/qhsHSlpef4gSSiGaNehmaHVZSyaWB3wr55s0exy7wz14pyJjyAksyzE0z+2PhcB7pekqAK7SgMnjearOaf
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=4032.5aea6685.k1805; bh=c0B7wRt8CzBMm07bOdvmpqG7SNxzT9Ss3dg06XxIPmY=; b=kb6j9BCHrAfr/7b0tqjLeGUYjz9o66pVj7Nf1VbYO0gW9aOiZR6GIZfBApI8YbDdHMAdV09T/chD0pNgwVqK1a7atJJYlpd0XfzJ8J+bPbSRL+SuZSjGEO1HUHjrNYFmLuXjWmUbnB8aDENExqextaFZaQBNkEAbRAXZ97mM/C4C9cYsqR9N9tdC8Gt6QYTgOAELtppIiDr8icQ7zcD3ugJQuCArJSqs52lLU9YskstbwK6V1SyaKuMPfZ5NjfMX
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 03 May 2018 01:31:49 -0000
Received: by ary.qy (Postfix, from userid 501) id 5C4B025CE95C; Wed, 2 May 2018 21:31:49 -0400 (EDT)
Date: Wed, 02 May 2018 21:31:49 -0400
Message-Id: <20180503013149.5C4B025CE95C@ary.qy>
From: John Levine <johnl@taugh.com>
To: spasm@ietf.org
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/cgFvGXVFOIVrQ0fPZpARp0b7iDk>
Subject: [lamps] Semi-OT: crypto code in RFCs
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 May 2018 01:31:52 -0000

For reasons anyone familiar with US law can probably guess, I'm trying
to collect all of the RFCs that include cryptographic source code.
RFC 8032 has python code for EC signing and verification.  Any others
I should put on the list?

R's,
John

PS: Please do not tell us how silly the US rules about crypto software
export are.  We know.

v2.23.0 | Report a Bug | By Email