[openpgp] Re: Primary Key Binding sigs on authentication subkeys

Stephan Verbücheln <stephan@verbuecheln.ch> Tue, 28 January 2025 22:51 UTC

Return-Path: <stephan@verbuecheln.ch>
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 58B9EC14F6BC for <openpgp@ietfa.amsl.com>; Tue, 28 Jan 2025 14:51:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.311
X-Spam-Level:
X-Spam-Status: No, score=-1.311 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_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verbuecheln.ch
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id skXIcp4MFbcV for <openpgp@ietfa.amsl.com>; Tue, 28 Jan 2025 14:51:10 -0800 (PST)
Received: from verbuecheln.ch (unknown [51.154.10.84]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 43611C169435 for <openpgp@ietf.org>; Tue, 28 Jan 2025 14:51:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verbuecheln.ch; s=default; t=1738104668; bh=/jwHjIisYp8nxbW+Wuj0/Jx+y9b+8+Qj43eOE+YzMKM=; h=Subject:From:To:Date:In-Reply-To:References:From; b=dSRT9QLCbsjnPUwhCTclAyXH0pDw+robDroHCy3xhPY9/l92BfCsWOTfZEGTHLOSv xp6QNDwaR8dL0sYc9zXJtv0cd1VE59CaK2113ccrlrYX/UXpZTjsI9N2cIzegHiCK7 Rsf2XUmP8TI37EnK3KLHn3hY8VqSOCUaKqOVC1lzB4DOJxmOBblgdJdbk/WNTz5N6z WUPkxdnyIJbcu0R/7mdfkTvik69ML+Oz1uEAXlaMNLMywNb4n2g5r79j6QYQ9pJtzQ Ytt2x6ULX1m9Vwmu0M0KnPGazDEo6Ss03VDKxOMicnsgZD9GfLSInGsOOeYr1Y46c5 KT3iqc0nnzvFg==
Received: from [IPv6:2a04:ee41:3:309c:9dfa:60c1:4986:62d1] (unknown [IPv6:2a04:ee41:3:309c:9dfa:60c1:4986:62d1]) by verbuecheln.ch (Postfix) with ESMTPSA id 871A82BF for <openpgp@ietf.org>; Tue, 28 Jan 2025 23:51:08 +0100 (CET)
Message-ID: <c7ca0acc7298dcccb4f14d8b81a45b5733a93a1b.camel@verbuecheln.ch>
From: Stephan Verbücheln <stephan@verbuecheln.ch>
To: openpgp@ietf.org
Date: Tue, 28 Jan 2025 23:51:06 +0100
In-Reply-To: <LIWr-Fiz5EpXR5DQtFrZRqWCtNc1_ADJN-d8TrWsw0s9auDsh76eXn6jdo0J1d3WTrWkxNnnSufHRlUcuBqsyxYhnReLn3fPR8ZUR4CPSNc=@protonmail.com>
References: <D6B824E8-5559-41FB-8EC4-ACC0C35FAEB0@andrewg.com> <HBqO7fta_A4PuuS2EkZ4W5g6SAnzgN38ZYjpGWqgZJHCFqCQUNQ-BAXEHRqa7pwGU5jI7s6XpvGV2ZYLpa6se9e-SJDujNO6yknALtzlAW8=@protonmail.com> <875xm64wtk.fsf@europ.lan> <LIWr-Fiz5EpXR5DQtFrZRqWCtNc1_ADJN-d8TrWsw0s9auDsh76eXn6jdo0J1d3WTrWkxNnnSufHRlUcuBqsyxYhnReLn3fPR8ZUR4CPSNc=@protonmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.54.3-2
MIME-Version: 1.0
Message-ID-Hash: TDRTENICP6YBUKASLFHNRY4O26LS63R5
X-Message-ID-Hash: TDRTENICP6YBUKASLFHNRY4O26LS63R5
X-MailFrom: stephan@verbuecheln.ch
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: Primary Key Binding sigs on authentication subkeys
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/QH9WVu_gkBE89kBTN1tsGR7rA4I>
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>

On Wed, 2025-01-22 at 17:31 +0000, Daniel Huigens wrote:
> OK, my bad. I wasn't aware that this functionality is used in
> practice.
> Mainly out of curiosity, which services/software support
> authenticating in this way?

Dear Daniel

Please note that PGP is not only used for email. One could even argue
that due to its low adaption among the total number of email users,
other use cases are much more relevant for the privacy and integrity of
the greater Internet-using public, e.g. signing Git commits, tags and
release tarballs.

SSH authentication is another non-email use case, and note that this is
not limited to manual remote shell access by human beings but also Git
clone/pull/push, file transfer via SFTP, backups with rsync and so on.
How the authentication key is used is defined by the SSH protocol, not
by OpenPGP. It does not make sense to invent your own authentication
mechanism in the RFC.

Since you did not even know that PGP auth keys are commonly used for
SSH, maybe you should slow down instead of pushing forward before
breaking everything. This again smells like Proton trying to change PGP
with only their own use case of email in mind, already causing schism
in the PGP community. I am genuinely worried about much more than just
my friends being unable to decrypt my emails with a client of their
choice.

Also note that many PGP use cases require that the users manage their
keys personally. Proton managing PGP keys for their users disqualifies
the PGP key for other use cases such as release signatures. There was a
discussion at Debian to ban Proton for maintainers because of this.

Regards
Stephan