Commits


don't run the test binaries, compilation status is enough During a cross-compilation we can compile the test binaries but not run in the host machine. Furthermore, the exit status of the test isn't really important for the types of check we have, the compilation status is enough. Reported by Nikolay Korotkiy (@sikmir) on Github, fixes issue #8


free OCSP path when clearing the config was forgotten in ff05125eb81e5bbf2cf05b8434d03bce584936e0


don't list the exact pledge promises It's easy to forgot to update the README after a code change (already happened in the past) and they're easy to discover by reading sandbox.c


use gmid from the repo instead of the system installed one


sync changelog


fix "double slash" in logs gmid ended up printing two slashes between the hostname and the path when logging the request IRI.


master is now 1.8-dev


fmt


typo


update the site for 1.7.5


sync changelog


fmt


Implement OCSP stapling support Currently dogfooding this patch at gemini.sgregoratto.me. To test, run the following command and look for the "OCSP response" header: openssl s_client -connect "gemini.sgregoratto.me:1965" -status


c->req may be NULL now


move bufferevent initialization early in handle_handshake the error path needs an initialized bufferevent too, otherwise it'll crash when trying to write the response. This moves the initialisation early, right after the tls_handshake. Another option would be to initialise it in do_accept, but that may be too early.