Commit Briefs
gg: exit with the gemini response code
0 is still used for 2X replies, and "external" failures (e.g. network, tls, ...) are still using exit code 1. Gemini non-2x replies now get their response code reported as-is as status code.
tweak gemexp logs
gemexp is meant for local testing so I'm not too worried about changing its log format if it makes sense to do so.
regress: change naming scheme for certs, add GENCERT_FLAGS knob
Call the certificates .pem and the keys .key; use contrib/gencert to generate the certificates and provide a GENCERT_FLAGS knob so that regress can be run with EC keys (GENCERT_FLAGS=-e). Still no automatic way of testing with both RSA and EC keys.
gemexp: change the naming scheme for the certificates
Using what the manpage advertised. The regress adaptations will follow. The directory will also change (and the key type too.)
log ip address and port when tls_handshake fails
These connection are not otherwise logged and it could be helpful to track down the bad ip.
tweak log_request() comment
gg -> gemexp and better wording.
don't let crypto_dispatch_server handle IMSG_CRYPTO_ECDSA_SIGN
in this codepath. otherwise we end up with a mismatch where we expect a request but were sent a response.