IETF Logo Mail Archive

Re: [openpgp] Expiration impending: <draft-ietf-openpgp-rfc4880bis-01.txt>

openpgp.dirk@o.banes.ch Mon, 03 July 2017 19:41 UTC

Return-Path: <dirk@o.banes.ch>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EDE112ECC1 for <openpgp@ietfa.amsl.com>; Mon, 3 Jul 2017 12:41:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=banes.ch
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 d_SLh1JwbZbD for <openpgp@ietfa.amsl.com>; Mon, 3 Jul 2017 12:41:40 -0700 (PDT)
Received: from mail.banes.ch (mail.banes.ch [IPv6:2a03:4000:6:30bc::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 4735813171F for <openpgp@ietf.org>; Mon, 3 Jul 2017 12:41:39 -0700 (PDT)
Received: from [IPv6:2001:8e0:1084:de02:e9f8:f772:64a7:84e0] (unknown [IPv6:2001:8e0:1084:de02:e9f8:f772:64a7:84e0]) by mail.banes.ch (Postfix) with ESMTPSA id 09244FFC67 for <openpgp@ietf.org>; Mon, 3 Jul 2017 21:41:33 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=banes.ch; s=mail; t=1499110893; bh=BpMGL5DxOO5JAGHcIwsUr1WNjodfAorXwGO05b7ow90=; h=Subject:To:References:From:Date:In-Reply-To; z=Subject:=20Re:=20[openpgp]=20Expiration=20impending:=0D=0A=20<dra ft-ietf-openpgp-rfc4880bis-01.txt>|To:=20openpgp@ietf.org|Referenc es:=20<149847732613.7086.8580563657011849337.idtracker@ietfa.amsl. com>=0D=0A=20<CALaySJKxWevOZYv1hOBFV-+3T=3D2x43vmie50t6ko2A+a-gTS_ A@mail.gmail.com>=0D=0A=20<a3a82aab-a0d9-f044-21c0-26de346bf6b3@si xdemonbag.org>=0D=0A=20<20170702232541.t25v6mf36qnrxkex@genre.crus tytoothpaste.net>=0D=0A=20<1b5da7bf-d43b-fde5-f6b6-28d9c6fd6edb@gm x.net>=0D=0A=20<94a05934-4b5c-4fb6-d127-beb0eacb47cf@sixdemonbag.o rg>=0D=0A=20<679411c5b2de4c308cbfbb3733c4fe54@usma1ex-dag1mb1.msg. corp.akamai.com>|From:=20openpgp.dirk@o.banes.ch|Date:=20Mon,=203= 20Jul=202017=2021:41:36=20+0200|In-Reply-To:=20<679411c5b2de4c308c bfbb3733c4fe54@usma1ex-dag1mb1.msg.corp.akamai.com>; b=Qz5ILstk3bd1IVtwCpazFOpKaFLOZpNSLyK34HsPsp6uH74N6rdjRV2PjERXwNYB5 zeYMK8U/3/dn3RT9fvp0bkV8hM0MdiL6ulaKaBGF25zmiv/S+nrNOLRCrhL2WTiYs8 QtCAPef4+hq00FmEzYrIWqKmv+oPC8WoaIoEsxmw=
To: openpgp@ietf.org
References: <149847732613.7086.8580563657011849337.idtracker@ietfa.amsl.com> <CALaySJKxWevOZYv1hOBFV-+3T=2x43vmie50t6ko2A+a-gTS_A@mail.gmail.com> <a3a82aab-a0d9-f044-21c0-26de346bf6b3@sixdemonbag.org> <20170702232541.t25v6mf36qnrxkex@genre.crustytoothpaste.net> <1b5da7bf-d43b-fde5-f6b6-28d9c6fd6edb@gmx.net> <94a05934-4b5c-4fb6-d127-beb0eacb47cf@sixdemonbag.org> <679411c5b2de4c308cbfbb3733c4fe54@usma1ex-dag1mb1.msg.corp.akamai.com>
From: openpgp.dirk@o.banes.ch
Message-ID: <9fbed93a-e4a7-3d00-1c53-ee587c2dface@o.banes.ch>
Date: Mon, 03 Jul 2017 21:41:36 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <679411c5b2de4c308cbfbb3733c4fe54@usma1ex-dag1mb1.msg.corp.akamai.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Language: de-CH
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/QJkqmorRi-Gjs-LSBk-C7ozvmOQ>
Subject: Re: [openpgp] Expiration impending: <draft-ietf-openpgp-rfc4880bis-01.txt>
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jul 2017 19:42:37 -0000

Dear List,

May I kindly ask if part of the critcal an necessary changes is
sunsetting 3DES, SHA1.
Yes I know they are still good but I think in current operation speed of
standards it is definitly time to start it.

I expierence in private an buisness live extra efforts to ensure pgp
communication is not using 3DES for example which
costs percious time in our projects.

best regards

Dirk


On 03.07.2017 21:35, Salz, Rich wrote:
>>> What's your opinion about defining additional (non-ECC) public-key
>>> algorithms, e.g., Cramer-Shoup or an IND-CPA secure variant of ElGamal?
>> I would be opposed to this.  This is not the time to start adding neat stuff to
>> the RFC.  Now is the time to make the critical and necessary changes to the
>> RFC and *get it published*.
> Strongly agree.
>
> _______________________________________________
> openpgp mailing list
> openpgp@ietf.org
> https://www.ietf.org/mailman/listinfo/openpgp

v2.23.0 | Report a Bug | By Email