Commits
Commit:
534afd0ddcba7c3d2f8478e89db026010c6190c5
Author:
Omar Polo <op@omarpolo.com>
Date:
Wed Oct 5 15:10:44 2022 UTC
make the various strings in the config fixed-length

will help in future restructuring to have fixed-size objects.
Commit:
d040746a37a2af87b1b4ffe746e2f3b9231576f1
Author:
Omar Polo <op@omarpolo.com>
Date:
Sat Sep 10 13:18:24 2022 UTC
server: inline dispatch_imsg
Commit:
0126d91d1d80d7d8e794b2176556fce969f165cd
Author:
Omar Polo <op@omarpolo.com>
Date:
Wed Sep 7 20:47:33 2022 UTC
add ge: gemini export!
Commit:
760009951357d4c36991c4c6a62db973289b32d9
Author:
Omar Polo <op@omarpolo.com>
Date:
Tue Sep 6 16:40:38 2022 UTC
optionally disable the sandbox on some systems

The FreeBSD and Linux' sandbox can't deal with `fastcgi' and `proxy'
configuration rules: new sockets needs to be opened and it's either
impossible (the former) or a huge pain in the arse (the latter).

The sandbox is still always used in case only static files are served.
Commit:
d29a2ee2246e1b1b0c5222a823820e42422c894e
Author:
Omar Polo <op@omarpolo.com>
Date:
Tue Sep 6 16:11:09 2022 UTC
get rid of the CGI support

I really want to get rid of the `executor' process hack for CGI scripts
and its escalation to allow fastcgi and proxying to work on non-OpenBSD.

This drops the CGI support and the `executor' process entirely and is
the first step towards gmid 2.0. It also allows to have more secure
defaults.

On non-OpenBSD systems this means that the sandbox will be deactivated
as soon as fastcgi or proxying are used: you can't open sockets under
FreeBSD' capsicum(4) and I don't want to go thru the pain of making it
work under linux' seccomp/landlock. Patches are always welcome however.

For folks using CGI scripts (hey, I'm one of you!) not all hope is lost:
fcgiwrap or OpenBSD' slowcgi(8) are ways to run CGI scripts as they were
FastCGI applications.

fixes for the documentation and to the non-OpenBSD sandboxes will
follow.
Commit:
543f4a66fec191b16621ae4f7783782131a3b067
Author:
Omar Polo <op@omarpolo.com>
Date:
Mon Jul 4 14:31:17 2022 UTC
add a trailing / for dirs in the directory index.
Commit:
a555e0d67baef271ffe4a186326ee5f1c16fff75
Author:
Omar Polo <op@omarpolo.com>
Date:
Mon Jul 4 09:48:39 2022 UTC
copyright years
Commit:
f2f8eb35c86c4e1c1d858e782c864deac0511cd3
Author:
Omar Polo <op@omarpolo.com>
Date:
Mon Jul 4 09:31:36 2022 UTC
encode file names in the directory index

Spotted the hard way by cage
Commit:
3bd4a6dea08fc977e314877cefed1c6fdd6b1613
Author:
Omar Polo <op@omarpolo.com>
Date:
Mon Jul 4 08:25:15 2022 UTC
log when it fails to open a file because of permissions
Commit:
ea27eaaa83d61792e75858dc624c58fe1fa13dc9
Author:
Omar Polo <op@omarpolo.com>
Date:
Sun Mar 27 12:52:59 2022 UTC
fix an out-of-bound access in start_cgi

Long time ago, client->req was a static buffer so the memcpy was safe.
However, it's been since moved to a dynamically allocated string, so
it's very often smaller than sizeof(req.buf) (1024), hence the out of
bound access which results in a SIGSEGV very often on OpenBSD thanks to
Otto' malloc.

The situation with the iri parser, client->req and how the request is
forwarded to the other process needs to be improved: this is just a fix
to address the issue quickly, a better one would be to restructure the
iri parser APIs and rethink how the info is forwarded to the ex process.
Commit:
3fdc457c8db0550a6143ab626bfefe3351ab0b93
Author:
Omar Polo <op@omarpolo.com>
Date:
Sat Mar 26 11:32:26 2022 UTC
swap try_client_by_id with client_by_id

i.e. allow client_by_id to fail and return NULL.

Initially I thought it was a good idea to shut down a server process
if we receive an invalid client id as reply from one of our requests
to the executor process. This turned out not to be correct since a
client can (read: will) disconnect in the delay beteewn we acknowledge
their request and the cgi script execution.

The fastcgi and proxy handler already handled this situation, so
they're unaffected.

This allows an attacker to make gmid unresponsible by just making
enough requests until they hit the right timing.
Commit:
d98ae929b23af35e2e837c97b5c20559f48d584b
Author:
Omar Polo <op@omarpolo.com>
Date:
Sat Feb 19 18:11:05 2022 UTC
don't log errno, it's always zero after libtls returns

The libevent error value is much more interesting!
see github issue #13
Commit:
e0f6dc646d6c257869c17f16db977cd064262830
Author:
Omar Polo <op@omarpolo.com>
Date:
Thu Jan 27 09:55:52 2022 UTC
improve proxy error path

properly release everything when during client_close if the request
was managed by a proxy.
Commit:
d28bd963c2450790bdb6bf2193af5670581c0c24
Author:
Omar Polo <op@omarpolo.com>
Date:
Thu Jan 27 09:54:48 2022 UTC
always mark requests as done when their code is != 20
Commit:
b9b77f5344ba6d6116044360feb3a7927778169f
Author:
Omar Polo <op@omarpolo.com>
Date:
Thu Jan 27 09:28:27 2022 UTC
fix comment
Omar Polo