Re: [lamps] Semi-OT: crypto code in RFCs

"Salz, Rich" <rsalz@akamai.com> Thu, 03 May 2018 01:43 UTC

Return-Path: <rsalz@akamai.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 D189812D77B for <spasm@ietfa.amsl.com>; Wed, 2 May 2018 18:43:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level:
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
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 ZxtNzoT50axT for <spasm@ietfa.amsl.com>; Wed, 2 May 2018 18:43:42 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 1F0A9127599 for <spasm@ietf.org>; Wed, 2 May 2018 18:43:42 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.22/8.16.0.22) with SMTP id w431bR5a003791; Thu, 3 May 2018 02:43:41 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=Uj13f1gKtjt+ZyQWwc+WjZGqUSvfVE1hEzKFpxmR17M=; b=KYjoZTi63NzHC5HXlmMv1G3TuHZ0VUIe9d+0M3DcUnGNbqymSVHtKCyDHhEv8Nip/555 +NfLc0nlTNVx4q7BpDmd+J6zV3l/yWDBk/ECWjDiCk5Cz2XpewVnPlAzpEQ8LRt9i8jZ bfHpPlt/d5E50UGNdt/SFLH9aMHLtlWHMJcizFtKNfwV5uSqu2YuwWqsoDYd6WyIOwN5 4XE4dS+Ha8POIFqQa0H6sP4NnDF9mSv8gRFeS2XYm1P+QxCj5ypsT5U7HFYxktSc7axw lGb2j8VXFhijb0q7lQyBeUevS2tLbixiRymX1zVccpAqxpgJz5ovW//+lKBDasCULhMu hg==
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19]) by m0050102.ppops.net-00190b01. with ESMTP id 2hq4snjsy7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 03 May 2018 02:43:41 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w431f5uI023002; Wed, 2 May 2018 21:43:40 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.57]) by prod-mail-ppoint2.akamai.com with ESMTP id 2hmm9v41wk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 02 May 2018 21:43:39 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 2 May 2018 21:43:39 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1365.000; Wed, 2 May 2018 21:43:39 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: John Levine <johnl@taugh.com>, "spasm@ietf.org" <spasm@ietf.org>
Thread-Topic: [lamps] Semi-OT: crypto code in RFCs
Thread-Index: AQHT4n6GZGc/052ZzkSj1BAI1nsrOaQdO1MA
Date: Thu, 03 May 2018 01:43:38 +0000
Message-ID: <D783C681-F08A-411E-B432-B3215F984431@akamai.com>
References: <20180503013149.5C4B025CE95C@ary.qy>
In-Reply-To: <20180503013149.5C4B025CE95C@ary.qy>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.c.0.180410
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.41.28]
Content-Type: text/plain; charset="utf-8"
Content-ID: <8C0C9A62B6019449A3329C78700BDE32@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-03_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805030012
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-03_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805030012
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/mv0f8E4YUEnYklVPs2Qjl6qD6UQ>
Subject: Re: [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:43:44 -0000

I believe that Bernstein v US showed that documents are protected, even in the US

´╗┐On 5/2/18, 9:31 PM, "John Levine" <johnl@taugh.com> wrote:

    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.
    
    _______________________________________________
    Spasm mailing list
    Spasm@ietf.org
    https://www.ietf.org/mailman/listinfo/spasm