Re: [openpgp] v5 in the crypto-refresh draft

Nickolay Olshevsky <o.nickolay@gmail.com> Mon, 07 June 2021 10:14 UTC

Return-Path: <o.nickolay@gmail.com>
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 466383A0D27 for <openpgp@ietfa.amsl.com>; Mon, 7 Jun 2021 03:14:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 YK6wUFSqx2r2 for <openpgp@ietfa.amsl.com>; Mon, 7 Jun 2021 03:13:56 -0700 (PDT)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFBA63A0D20 for <openpgp@ietf.org>; Mon, 7 Jun 2021 03:13:55 -0700 (PDT)
Received: by mail-lj1-x22a.google.com with SMTP id bn21so21438401ljb.1 for <openpgp@ietf.org>; Mon, 07 Jun 2021 03:13:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:references:from:subject:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=T1QErvhhmFMyo2ryqqk6xvw71icH+mUCUwlKiVerGs4=; b=U30UN2Op7Qi7QJUDaNEHEFwYzVgLf6tbxwHFraMcfJy71vlKWJPHLNYncNkdTglH5j S2/m79Mtxp4/+8aHVzFzZJdZjX6NqNBSZOuzAFfOriETdIViCs+sYddqfLjeiOdI48q8 iZz+cGw5zuq4il0U2EtbEA17TKqHQ3K50iIsgyV6Y2EkvpJgWltEtmvv6DmOybOT1D3m d6ZE9lmOnJe9gZb77RargGfM4yX9x5eLP4gYBv+Mot0iHLAIA1iIAhdtnneM7KCwTIAG NsgIgdg+zMkhOIBOgwLGfUpiy8Z6bbMTuuc0iMr2OkKOgVTx3zVxV4KbTqz/EXu1ZreJ Andg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:references:from:subject:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=T1QErvhhmFMyo2ryqqk6xvw71icH+mUCUwlKiVerGs4=; b=Af96tQ7nMutLUBE3Y1gEyj5N0Zxhb0rHb/uNL+4ew1FbXAEg2bDWCq8rToocqthwxx JRfBfrZqOxgM+464JrarFOascPolh8nRzsUU5USrdGCIheXhYwEJXOYZzeUHfDOCXwSK Qg4BCjGy/07EuAyML41vnVQnOkyLFKjvuB9LSwx75SXW7E92IIIhatmELKLnZ+9dOMBj ZvSGvosEVEuBEYd5UlaQN7sdF7p30U7HmS3njYB3TStb9eeyp3C0T8KPhXhjVmDoFJAA tzRHzOT1B1rdCKrvNvMlDXItCUKJiBgKQTettT58+A1CuwdS7MOWfpNEqssw+vpqIbaH 5IjA==
X-Gm-Message-State: AOAM530QeBHiDZ15VsDKifyTXV9OwUmAONwmLrh3w9GTsxy3ecoUYm5M YJ9SvgzXYVV1aWmKLUCWZIt5ZOB+w1DomQ==
X-Google-Smtp-Source: ABdhPJx8HQ+YM3sU0ix97EJ+Ts1CLKsELHyhcyLpVGe1XiCi+QhZlJQ/qrUiv98TtwhMUigqJ7fzZA==
X-Received: by 2002:a2e:870d:: with SMTP id m13mr14590061lji.250.1623060831769; Mon, 07 Jun 2021 03:13:51 -0700 (PDT)
Received: from Inf-Mb2020.local ([46.229.60.172]) by smtp.gmail.com with ESMTPSA id w15sm681844lfq.94.2021.06.07.03.13.50 for <openpgp@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 07 Jun 2021 03:13:51 -0700 (PDT)
To: openpgp@ietf.org
References: <87lf7q6sh0.fsf@fifthhorseman.net>
From: Nickolay Olshevsky <o.nickolay@gmail.com>
Message-ID: <2e2495e8-6f4c-f842-3886-61cd696a6483@gmail.com>
Date: Mon, 7 Jun 2021 13:13:50 +0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.10.2
MIME-Version: 1.0
In-Reply-To: <87lf7q6sh0.fsf@fifthhorseman.net>
Content-Type: multipart/alternative; boundary="------------9246AB38880EF3EA0321DA93"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/e17eTbjEpzfB4cLLxBvazkwOzmo>
Subject: Re: [openpgp] v5 in the crypto-refresh draft
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Jun 2021 10:14:00 -0000

Hi,

It's slightly out of the original questions, but still related to the v5 
keys/sigs.

Basically, given that year 2038 will come in 17 years, and previous RFC 
4880 is already 14 years old without any replacement (yet), why v5 keys 
and signatures still have 32-bit creation time?

Or did I miss some discussion regarding this?


On 04.06.2021 09:42, Daniel Kahn Gillmor wrote:
> I've been reviewing the changes in draft-ietf-openpgp-crypto-refresh-03.
> I have concerns about most of the "v5" features currently incorporated.
>
> ...
>
> Regards,
>
>          --dkg
>
> _______________________________________________
> openpgp mailing list
> openpgp@ietf.org
> https://www.ietf.org/mailman/listinfo/openpgp

-- 
   Best regards,
   Nickolay Olshevsky
   o.nickolay@gmail.com