[openpgp] Representing an OpenPGP key set in a JWK

Phillip Hallam-Baker <phill@hallambaker.com> Fri, 11 April 2025 20:00 UTC

MIME-Version: 1.0
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Fri, 11 Apr 2025 16:00:03 -0400
Message-ID: <CAMm+Lwi8pmue69ULwRJM3tkV18ZpHE8M+fb1vyCsxj_j91RpbQ@mail.gmail.com>
To: jose@ietf.org, IETF OpenPGP <openpgp@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000b42b70632862762"
Message-ID-Hash: AFWPFB72UMPW2ZU3S6G7LGOKWFEJ323Y
Precedence: list
Subject: [openpgp] Representing an OpenPGP key set in a JWK
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/y0Tb4Fipcyqec2hDrSQoyp2UDBc>

After discussions with people in JMAP/CALEX people I am looking to add JWKs
to JSContact.

Previously JSContact followed vCard in representing keys as URIs,
frequently data URIs. This is really a bit of a pain if you are wanting to
use a JSContact to launch an application with the key material relevant to
it.

In particular, it is a real pain for OpenPGP because we don't just use
OpenPGP for encrypting emails. It is also used for signing git commits and
many other things. And in those contexts, it is not enough to have a raw
key, you (may) need the key/subkey chain.

I am not an OpenPGP expert or a Git expert so looking for ideas on this.

I think we can all agree that it would be rather nice if Alice can join an
Open Source development effort by providing them with a single identifier
that is descriptive of all the credentials related to their coding work,
commit signing, SSH, code signing etc. etc.

[openpgp] Representing an OpenPGP key set in a JWK Phillip Hallam-Baker