WKD makes using cryptography with emails (and files) easier for you and the people you exchange emails and files with.

For the best experience, you need an email client and an email provider that fully provide the functionality to you. As long as you are not there, you can still gain some of the benefits (while doing some work yourself.)

Security by cryptography?

The OpenPGP standard uses asymmetric cryptography, which needs a pair of keys.

So each person needs to have (at least) one pair of keys consisting of a private key and a public key that belong together.

If you want to encrypt something to somebody else, you need that person's OpenPGP public key (pubkey). And that person needs your public key to encrypt something in return.

Looking up public keys of others

You can check your email client if it has the following features (in that order):

If your email client cannot do it, you can still see if the used crypto engine can do a lookup manually.

Making sure others can get my public key.

Check that you email provider can:

If you are your own email provider, look into the methods how to implement WKD on the server side.

Web key service (WKS)

The WKD specification includes a standard way called "Web Key Service" to manage the public key that your email provider offers via WKD. It uses emails, so email clients can implement it.

So in addition to the email provider offering it, your email client can offer:

If your email client does not provide this, you can try some manual methods to create the necessary emails.

Scope: Explain WKD from the user perspective. Show which features to look for with email clients and providers.

WKD/forUsers (last edited 2021-09-28 15:16:49 by bernhard)