May cause weird errors (status=216/GROUP) on some distros, and running as root is already the default, so remove the two lines. Reported by and debugged together with leandro del Flug, thanks!

Various techniques used by gmid are effective only when the daemon is started as root. Strongly suggest to do so by switching the sample configuration. This way, provided that a local user is created as well, the chroot configuration will work out-of-the-box and the TLS certificates can be readable only by root.

with the privsep rework the config dumping was unadvertitely broken, it prints the content of the key itself.

the previous -Werror triggers too easily: on NixOS for example the FORTIFY_SOURCE #warning about a missing optimization level breaks all the checks when using -O0 (which is the default for non-release builds).

include stddef.h for size_t

We should open the log file inside the chroot; missed in 4acf495f41d2c26136e99072293ca8b9bff91dc0. See https://github.com/omar-polo/gmid/issues/24

we actually should open the log file in the chroot, the bug is in the code.