[openpgp] Re: Proposal: Provider-assisted OpenPGP key disc overy

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============2529198157237595160==
Content-Type: multipart/signed; protocol="application/pgp-signature";
 micalg=pgp-sha512;
 boundary="------49bf8699612ddf538b11f1a77eca99b655ec40d6790978b5ed8c146aee720558";
 charset=utf-8

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--------49bf8699612ddf538b11f1a77eca99b655ec40d6790978b5ed8c146aee720558
Content-Type: multipart/mixed;boundary=---------------------ca56050449f04189501693ea36a80b68

-----------------------ca56050449f04189501693ea36a80b68
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;charset=utf-8

Indeed, I was not referring to Proton as a major ESP, which it is not (yet=
).

-Bart


On Wednesday, July 15th, 2026 at 7:12 PM, Daniel Kahn Gillmor <dkg@fifthho=
rseman.net> wrote:

> On Wed 2026-07-15 10:22:37 +0000, Bart Butler wrote:
>
> > I will point out that getting the major ESPs to use such a registry
> > will absolutely never happen.
>
> Presumably Bart's description of "major e-mail service providers (ESPs)"
> refers to Microsoft and Google, but not to Proton itself. =E2=98=BA
>
> It's entirely possible that users whose e-mail addresses are controlled
> by these major platforms will be unable to make use of the kind of
> automated OpenPGP certificate discovery you're contemplating, due to
> recalcitrance of their ESP.
>
> I think the question for the WG is whether it is sufficient to build a
> mechanism that works for users *not* in that group, given that the WG
> has no control over the business decisions of these entities.
>
> From my perspective, it seems reasonable to do that kind of work, as
> long as we're realistic about the reach.  The goal for e-mail is a
> functioning federated system.
>
>           --dkg
> _______________________________________________
> openpgp mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>
-----------------------ca56050449f04189501693ea36a80b68--

--------49bf8699612ddf538b11f1a77eca99b655ec40d6790978b5ed8c146aee720558
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wrsEARYKAG0FgmpXxxsJEJkFRGXvMx5ERRQAAAAAABwAIHNhbHRAbm90YXRp
b25zLm9wZW5wZ3Bqcy5vcmfNf0TxP0qv6e+BKAwpRiLXyao3A1qtjFLXQzNr
cyVUbxYhBDwVkTeBh+6myif6rJkFRGXvMx5EAAAk8gD+JKJUaRLjuUdZVmBK
1rCDxyqQlClfm4f5Kh3RkoTN4nUA/jDo4vVunSkD5ad/ENcwyGaFhLlmZNBE
i223PSYjhMUG
=9cF3
-----END PGP SIGNATURE-----


--------49bf8699612ddf538b11f1a77eca99b655ec40d6790978b5ed8c146aee720558--


--===============2529198157237595160==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kb3BlbnBncCBt
YWlsaW5nIGxpc3QgLS0gb3BlbnBncEBpZXRmLm9yZwpUbyB1bnN1YnNjcmliZSBzZW5kIGFuIGVt
YWlsIHRvIG9wZW5wZ3AtbGVhdmVAaWV0Zi5vcmcK

--===============2529198157237595160==--