Now gmid doesn't touch anymore the internals of the imsg structs.

Makes parsing and handling of imsgs simpler / clearer. only crypto.c is left as-is.

since proc_forward_imsg() never forwards a file descriptor (it's never called actually) just use -1 there.

There's no much we can do if we resolv an IPv6 address but its support is disabled in the current kernel, so ignore and go ahead. Spotted while testing gmid i n a FreeBSD jail without IPv6.

now that we have a bundled libtls we can actually do this. Retain the knob to disable it "just in case".

The new config_test() fails miserably when the privsep crypto engine is not enabled. As a temporary workaround, forcibly disable it during config_test() as we're not going to run anyway.

Attempt to do also a few more steps that were previously done only at runtime. This can help verifying that the keypairs are matching for example, but also that there are no typos in the path to the root directories. Was requested some time ago by Marian Mizik, thanks for the feature request!

Was requested ages ago by Karl Jeacle, now that there is some better support for configuring the logging there's no excuse to add this. It helps with filtering from syslog.d / syslog.conf.

I think the condensed is better but it'll need to change post 2.0 to accomodate for logging the number of bytes read in the body of a titan request (and it's weird to hardcode a zero there.) 2.0 will ship with the legacy logging style thus.

this revamps the syntax in the configuration to better match httpd(8) (and in general be less weird) and to allow per-location fastcgi configurations. the bare `param' is now deprecated, but for compatibility it acts like `fastcgi param' would do now. Same story for `fastcgi <pathÂ>'.