Commits


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.


gc FILE_EXECUTABLE


gc sandbox_executor_process


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.


count ran/failed tests number


sync


call tzset(3) to fix times in logs reported by Karl Jeacle, thanks!


mention Anna' patch too


mention the removal of the rc file


mention the 1.8.4 release


sync


don't set d_reclen It's not actually used and doesn't seem to be available on DragonflyBSD (at least) judging from the patching in dports: https://github.com/DragonFlyBSD/DPorts/commit/f66bf875f75335ff63e0cad2f817a1c6e7106045


don't hardcode urls; use TREE 'macro'


include contrib/ in dist


remove the OpenBSD' rc file now that gmid is packaged on OpenBSD the rc file is maintained in the ports tree.