[openpgp] Re: Signing-only primary keys

Wiktor Kwapisiewicz <wiktor@metacode.biz> Mon, 05 May 2025 11:31 UTC

Return-Path: <wiktor@metacode.biz>
X-Original-To: openpgp@mail2.ietf.org
Delivered-To: openpgp@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id CDC8624C7AD4 for <openpgp@mail2.ietf.org>; Mon, 5 May 2025 04:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 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_DNSWL_LOW=-0.7, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=metacode.biz
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 W-dVBJJ6lSKL for <openpgp@mail2.ietf.org>; Mon, 5 May 2025 04:31:11 -0700 (PDT)
Received: from out-180.mta0.migadu.com (out-180.mta0.migadu.com [91.218.175.180]) (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 4367E24C7ACF for <openpgp@ietf.org>; Mon, 5 May 2025 04:31:11 -0700 (PDT)
Message-ID: <8f93b706-40e2-406b-8e9a-c987cdde82a4@metacode.biz>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metacode.biz; s=key1; t=1746444669; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=umEcoxcdKFh2iCzd/n925UPTQ9L4LhKRQeR50X2DCxA=; b=NDNTmvOU64I42m4TXNbgBDFHkWI3PCkL3sSyepjBp9LRSBXzCZ9R2GJAy4QRcDueD26euU Dw5kRBtI3gZLjoG17F5D2TEOLeDXA8REA+wkp4OKzlg1DbcSi2zreCTZNRDRGfIdN6R4KA tO6UFd+s5Cc51d/JOI4luMIV0jxWwCE=
Date: Mon, 05 May 2025 13:31:05 +0200
MIME-Version: 1.0
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
References: <7d94d70b-fd18-4a0f-b656-d2936aa09578@metacode.biz> <87r019grt9.fsf@fifthhorseman.net>
Content-Language: en-US, pl-PL
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
From: Wiktor Kwapisiewicz <wiktor@metacode.biz>
Organization: Metacode
In-Reply-To: <87r019grt9.fsf@fifthhorseman.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Migadu-Flow: FLOW_OUT
Message-ID-Hash: GGK4PX2JJSSFCCHVHFWQX4DINS5AVKDV
X-Message-ID-Hash: GGK4PX2JJSSFCCHVHFWQX4DINS5AVKDV
X-MailFrom: wiktor@metacode.biz
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-openpgp.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "openpgp@ietf.org" <openpgp@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [openpgp] Re: Signing-only primary keys
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/gKJcA8ujfOq5UpBuPD0ndi4RykA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Owner: <mailto:openpgp-owner@ietf.org>
List-Post: <mailto:openpgp@ietf.org>
List-Subscribe: <mailto:openpgp-join@ietf.org>
List-Unsubscribe: <mailto:openpgp-leave@ietf.org>

Hi,

On 1.05.2025 01:20, Daniel Kahn Gillmor wrote:
> Andrew Gallagher opened a request for a new test like that here:
> 
>     https://gitlab.com/sequoia-pgp/openpgp-interoperability-test-suite/-/issues/160
> 
> Maybe someone wants to nudge the interop test suite in that direction?
> It should be pretty easily discoverable with `sop validate-userid`.

Thanks for the link. I was not aware there's already something.

I think there are at least two tests that could be added:
   - check if `sop validate-userid` takes into account presence or 
absence of the C flag
   - check if `sop verify` works even if the C flag is absent on the 
primary key

I'd like to add these but, as usual, time constraints are tight :( We'll 
see.

Kind regards,
Wiktor