Implementing a WKS solution

[Dashamir Hoxha]

On Mon, Feb 22, 2021 at 11:08 AM Bernhard Reiter <bernhard at intevation.de> wrote:
> Help is always appreciated and it is a wiki, so you can just go ahead.
> Coordinate here, do not just replace stuff or call it official, but rather
> mark it or link additional information.

Wiki is good, but a documentation system based on git flow (with merge
requests, reviews, etc.) might be better.
Anyway, I tried to register and login, but I failed.

I have just published a WebKey server which can be integrated with a
mail server as an external component, in order to provide WKD+WKS
support for it:
- https://gitlab.com/docker-scripts/webkey
If I try to update the WKS docs I will use this one as a reference for
the configurations, commands etc:
- https://gitlab.com/docker-scripts/webkey/-/blob/master/scripts/setup.sh

Basically I would recommend (or do) these changes:
- Remove the instructions about Installing GnuPG from the source code,
since this should be explained somewhere else; assume that the users
can easily install GnuPG from a package.
- Update the instructions for building a WKD and add the configuration
of Apache2.
- Update the instructions for building a WKS and replace procmail with maildrop.
- Update the instructions for testing WKD/WKS and add some details
about testing with Thunderbird+Enigmail.
- Update the list of WKD/WKS solutions and add there
https://gitlab.com/docker-scripts/webkey

> The hint with procmail is certainly a good one, it would be useful to
> have a tested recipie without it, which is simple.

I am testing this maildrop recipe and it seems to work well:
- https://gitlab.com/docker-scripts/webkey/-/blob/master/scripts/setup.sh#L121-137

By the way, using the header 'X-WKS-Loop' with 'gpg-wks-server' seems
superfluous to me, since 'gpg-wks-server' already adds automatically
the header 'Wks-Phase', which should be sufficient for detecting a
loop. Am I missing something?

Regards,
Dashamir