Andre tried to access our demo WKS with:
gpg-wks-client --supported firstname.lastname@example.org
(using 2.1.16-beta328, git master)
It aborted with an error:
TLS handshake failed: The server name sent was not recognized (alert 112)
This happened due to a missing ServerName on the web server, but as
"SSLStrictSNIVHostCheck off" was set (Default in Apache 2.4), this should not
have caused an abort.
"gnutls-cli testkolab.intevation.de" conntected fine, but reported a warning:
- Non fatal error: A TLS warning alert has been received.
- Received alert : The server name sent was not recognized"
curl had the same problem in the past, see e.g.:
Adding a ServerName configuration to the web server helped working around this
problem (and is the right thing to do anyway), but gpg-wks-client (and maybe
other parts of gnupg that access TLS servers) should not abort here.