IETF Logo Mail Archive

[openpgp] Re: adding validate-userid to the sopv subset

Michael Richardson <mcr@sandelman.ca> Thu, 01 May 2025 14:52 UTC

Return-Path: <mcr@sandelman.ca>
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 6861123A50DA for <openpgp@mail2.ietf.org>; Thu, 1 May 2025 07:52:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.398
X-Spam-Level:
X-Spam-Status: No, score=-4.398 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_MED=-2.3, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_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=sandelman.ca
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 TsVsd3kbtnCi for <openpgp@mail2.ietf.org>; Thu, 1 May 2025 07:52:08 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (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 2B24623A50C4 for <openpgp@ietf.org>; Thu, 1 May 2025 07:52:08 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id CA5C91800E; Thu, 1 May 2025 10:52:07 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id YZ_7vm0SOp6P; Thu, 1 May 2025 10:52:05 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1746111125; bh=wGihbLKfslicU/XuuSy53hHhwjztLs8I+QuZk6bn/j4=; h=From:To:Subject:In-Reply-To:References:Date:From; b=wVDLlTcICRmW7ZF0UDTdFrc2DZqhVPCXbywRsxGfZR2M+bY8V4Tiy85ju2aj9jIEX yHjnYZU2WwiYO1Vc/ItIwLMZylTOFfwUL2zYOJRWnswfTmP3vARHzbxTBp7cFLFmOE GoQ2T0FrGtBnbNr82Y4Rd2U4riLpdjZI0/IwUUJqGg/+navMJDU1G7wEJu70aNIr6w AWGph5LS5WdIjHft4a6eeI60Y63GlE5Ht+HdAQM/jHttIvn/hcDjh49iMW5nFkQJIG ce/Y5jXFZouP4crzzP4t5xF8ZRult3U2EDF/YYRs1eGSGCyC1EFpBlbc518yI1ZmnV Vvh/RRow/57Tg==
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id AE8481800C; Thu, 1 May 2025 10:52:05 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id AADE711E; Thu, 1 May 2025 10:52:05 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, openpgp@ietf.org
In-Reply-To: <87ldrhgqzw.fsf@fifthhorseman.net>
References: <87ldrhgqzw.fsf@fifthhorseman.net>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 01 May 2025 10:52:05 -0400
Message-ID: <17693.1746111125@obiwan.sandelman.ca>
Message-ID-Hash: 4AMOLNHDO5V6SRWWKOB4PRPI4GS4ZVRF
X-Message-ID-Hash: 4AMOLNHDO5V6SRWWKOB4PRPI4GS4ZVRF
X-MailFrom: mcr@sandelman.ca
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [openpgp] Re: adding validate-userid to the sopv subset
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/2vzX3TnyRinHn1cC02GIYo8IvnI>
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>

Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:
    > I'm looking at adding sop's "validate-userid" subcommand (which does
    > simple one-hop User ID validation from a set of fully trusted
    > authorities) to the next revision of the sopv verification-only subset.

So the answers the question: can I (given my current "trust anchors",
e.g. "trust ultimate") validate userid XYZ?

    > My reasoning for this is that the functionality from an OpenPGP
    > perspective is very similar -- it's just a different type of OpenPGP
    > signature being checked.  And, it would make it possible to use a sopv
    > implementation to implement identity-checked signature verification.

Yes, it sounds reasonable, but it does stray into keyring management.
I agree that it fits into stateless, no secret key, etc. though.

Who/when would use it?
Would it be used in, for instance, SBOM verification?

    > There is also a separate request to make "validate-userid" fancier than
    > a simple one-hop validator (See
    > https://gitlab.com/dkg/openpgp-stateless-cli/-/issues/121) but for sopv
    > 1.2 i'm inclined to just keep it at a one-hop mechanism for the moment.

In the olden days, I would use one of the find a path from A->B web sites to
do that... then discover which people I needed to bug to sign some key so
that we'd have a trusted path.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.31.3 | Report a Bug | By Email | System Status