[Plants] Re: Higher forgery resistance almost for free?

Andreas Hülsing <ietf@huelsing.net> Mon, 04 May 2026 11:01 UTC

Return-Path: <ietf@huelsing.net>
X-Original-To: plants@mail2.ietf.org
Delivered-To: plants@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 6B9F2E8A5362 for <plants@mail2.ietf.org>; Mon, 4 May 2026 04:01:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777892482; bh=xzUHouyFMC2Vf4WxEkmh+Ako9vziTHSuwfWj2ja53Hs=; h=Date:To:Subject:From; b=H73B7fBMTHYSg0EX2MW56eczyzxwEmLdyM4r8/o3fLRBWyPclcec6cb99q2UffONk ZLeQoKTP2zXBJz7xSX7u2G04jLGvXwNZGbX6IfIDpgn9LX20dDkhljLpwf3Z0nwE8H U3NLzI6oEucII6Q/aDZ6U7yhLKnfkeZrLEN1qrgA=
X-Virus-Scanned: amavisd-new at ietf.org
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, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=huelsing.net
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L8_ARyD98xPf for <plants@mail2.ietf.org>; Mon, 4 May 2026 04:01:21 -0700 (PDT)
Received: from www363.your-server.de (www363.your-server.de [78.46.179.9]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 056FAE8A52A9 for <plants@ietf.org>; Mon, 4 May 2026 04:00:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=huelsing.net; s=default2007; h=Content-Transfer-Encoding:Content-Type:From: Subject:To:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References; bh=8yZEjru624FuD7TSSFCtCwN1vsW7ZVdZ+4zxkR+64Ao=; b=qgNZPp3xZnloCIUt7ipb54DXK5 MmUbsPsuroNQY0MJ9+XC2RInCqhSDjIMQExovS/UYJjgAoPxuCEMjK9O5sMORCilSuJGucmqFJpcF k8WpPCRqIiRnBg08HC0NPXSA1JqBWvpmmkJCKfhDJHbwhqL+IVWtjQ93N+sHXsF9VBT4WSRhBtV1z wsHJGyLVvoRCwDvTgUS2sw9y+HkH+YX5qok5rliLLtps5pS2IkhYp3mbJNgQam7PKRfEbkldGE2oV sBdM1slWkU9YiY1r2RTZn3np7mshv6LJL9KOWtbumEuJ+8ADtmKg+C+ASPhswo1WLkEPmW19EsRjc Bvdbmwcw==;
Received: from sslproxy02.your-server.de ([78.47.166.47]) by www363.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from <ietf@huelsing.net>) id 1wJr2G-0006PC-0T for plants@ietf.org; Mon, 04 May 2026 13:00:24 +0200
Received: from localhost ([127.0.0.1]) by sslproxy02.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <ietf@huelsing.net>) id 1wJr2F-000F7X-2K for plants@ietf.org; Mon, 04 May 2026 13:00:23 +0200
Message-ID: <ec7893de-4ad7-44fc-8be8-a4b4ec9e1e99@huelsing.net>
Date: Mon, 04 May 2026 13:00:23 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: plants@ietf.org
Content-Language: en-US
From: Andreas Hülsing <ietf@huelsing.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: Clear (ClamAV 1.4.3/27991/Mon May 4 08:24:39 2026)
Message-ID-Hash: JDJ5BJAJEH2UJ2GAP3VDXW6PNHE5IK5P
X-Message-ID-Hash: JDJ5BJAJEH2UJ2GAP3VDXW6PNHE5IK5P
X-MailFrom: ietf@huelsing.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Plants] Re: Higher forgery resistance almost for free?
List-Id: "PKI, Logs, And Tree Signatures" <plants.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/plants/xtBcFMKlbcmMpfMIR5mrVlLS8Wk>
List-Archive: <https://mailarchive.ietf.org/arch/browse/plants>
List-Help: <mailto:plants-request@ietf.org?subject=help>
List-Owner: <mailto:plants-owner@ietf.org>
List-Post: <mailto:plants@ietf.org>
List-Subscribe: <mailto:plants-join@ietf.org>
List-Unsubscribe: <mailto:plants-leave@ietf.org>

Hi all,

This sounds like a sensible solution for the case that the attacker is 
an external user, not the CA. In that case, the attack cost behaves 
indeed as discussed in this thread and will require a malicious user to 
do in the order of 2^256 work for a random oracle (or slightly less for 
the case of SHA256 due to the issue with the Antonov attack). As 
correctly pointed out by Victor, this will not help against a malicious 
or corrupted CA (remember DigiNotar) as to them the randomizer cannot 
only be chosen, but it even allows them to freely chose it (which, as 
this value afaikt is not authenticated besides being included in the 
hash, gives the CA a straight-forward degree of freedom to search for 
colliding, meaningful cert hashes).

Cheers,

Andreas