Re: [openpgp] How to re-launch the OpenPGP WG

Christoph Anton Mitterer <calestyo@scientia.net> Tue, 17 March 2015 03:46 UTC

Return-Path: <calestyo@scientia.net>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A03D1A1BED for <openpgp@ietfa.amsl.com>; Mon, 16 Mar 2015 20:46:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.1
X-Spam-Level:
X-Spam-Status: No, score=0.1 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 RMD-FNbCOADl for <openpgp@ietfa.amsl.com>; Mon, 16 Mar 2015 20:46:42 -0700 (PDT)
Received: from mailgw01.dd24.net (mailgw-01.dd24.net [193.46.215.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8E2F1ACDF9 for <openpgp@ietf.org>; Mon, 16 Mar 2015 20:46:40 -0700 (PDT)
Received: from mailpolicy-01.live.igb.homer.key-systems.net (mailpolicy-01.live.igb.homer.key-systems.net [192.168.1.26]) by mailgw01.dd24.net (Postfix) with ESMTP id 2F9965FB09 for <openpgp@ietf.org>; Tue, 17 Mar 2015 03:46:39 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at mailpolicy-01.live.igb.homer.key-systems.net
Received: from mailgw01.dd24.net ([192.168.1.35]) by mailpolicy-01.live.igb.homer.key-systems.net (mailpolicy-01.live.igb.homer.key-systems.net [192.168.1.25]) (amavisd-new, port 10235) with ESMTP id gSV0Y0OSqtl3 for <openpgp@ietf.org>; Tue, 17 Mar 2015 03:46:37 +0000 (UTC)
Received: from heisenberg.fritz.box (ppp-93-104-121-105.dynamic.mnet-online.de [93.104.121.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailgw01.dd24.net (Postfix) with ESMTPSA for <openpgp@ietf.org>; Tue, 17 Mar 2015 03:46:36 +0000 (UTC)
Message-ID: <1426563996.18487.24.camel@scientia.net>
From: Christoph Anton Mitterer <calestyo@scientia.net>
To: openpgp@ietf.org
Date: Tue, 17 Mar 2015 04:46:36 +0100
In-Reply-To: <874mppgyez.fsf@vigenere.g10code.de>
References: <878uf2iehi.fsf@vigenere.g10code.de> <1426218768.22326.80.camel@scientia.net> <874mppgyez.fsf@vigenere.g10code.de>
Content-Type: multipart/signed; micalg="sha-512"; protocol="application/x-pkcs7-signature"; boundary="=-vf/jIA8c07ONZM+fYpwK"
X-Mailer: Evolution 3.12.9-1+b1
Mime-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/eX3m1qz5QlksJZQRtRxnXtPeITU>
Subject: Re: [openpgp] How to re-launch the OpenPGP WG
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Mar 2015 03:46:45 -0000

On Fri, 2015-03-13 at 08:16 +0100, Werner Koch wrote:
> > - The WG should consider whether to just bring OpenPGP up to date... or
> >   whether to completely overhaul or even re-design it.
> The please give the thing another name.  Recall the outcry whn I removed
> PGP-2 support from 2.1.
Well I guess it happens very often that one has a very loud minority and
a silent majority.
Removing the support was definitely the right thing, especially since
it's still in the other branches.
All these very old keys are likely lather small (and thus weak) and
shouldn't be used therefore anymore.

IMO, security business can't really afford to always comfort those
living in the past and/or not doing their homework.
This model (leaving legacy stuff in for compatibility reasons) blew up
so often recently (RC4, SSL3, the export cipher suites, problematic CBC
mode usage in e.g. SSH)... these things should have been phased out long
ago, instead, people waited for questionable compatibility reasons way
too long until 5 past 12.

Someone who really wants security should have to suffer because of those
who want to keep old systems/alogs/etc., since the later anyway do not
really want security. 


> We already have this.  You may either use a plain user ID with signed
> attributes to implement this or, better
Well, as I've written before, using the plain UID packets in such ways
should IMHO be given up.

> extend the attribute packet,
> which is currently only used for photo ids, but designed for what you
> want.  You may already start with this using the 100--110 subpacket
> types.
Sure, just no one ever specified it, and thus no one every used it that way


> Regarding the rest of your mail, I think it is better to postpone a
> detailed discussion for now.
Fine,... it's now in the archives for the records =)


Cheers,
Chris.