You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we opt to implement MTA-STS as is, we need to serve HTTPS, as a further enhancement we could add support for WKS (OpenPGP Web Key Service) which would allow users to automagically look up OpenPGP keys of a given e-mail address local to the MTA.
Implementation should be rather straight-forward. WKS key discovery roughly works like that:
For example the URI to lookup the key for Joe.Doe@Example.ORG is:
https://example.org/.well-known/openpgpkey/
hu/iy9q119eutrkn8s1mk4r39qejnbu3n5q
(line has been wrapped for rendering purposes)
which is served simply via a /.well-known URL, where the account (e-mail address) is encoded as follows: z-base-32(SHA1(${address-local_part})).
If we opt to implement MTA-STS as is, we need to serve HTTPS, as a further enhancement we could add support for WKS (OpenPGP Web Key Service) which would allow users to automagically look up OpenPGP keys of a given e-mail address local to the MTA.
Implementation should be rather straight-forward. WKS key discovery roughly works like that:
which is served simply via a
/.well-known
URL, where the account (e-mail address) is encoded as follows:z-base-32(SHA1(${address-local_part}))
.The text was updated successfully, but these errors were encountered: