tobias.jakobi.compleo added more details in https://redmine.lighttpd.net/issues/3244
The issue appears to be lighttpd being built with 64-bit time_t, but the underlying openssl library being built with 32-bit time_t *and* exposing an API interface using time_t. The result is that lighttpd might issue error trace that a certificate is expired when the certificate is not expired. There should be no other ill-effect besides the error trace at startup. However, some distros have startup scripts which check config syntax, and will treat `lighttpd -f /etc/lighttpd/lighttpd.conf -tt` as an error if there is error trace, even if the lighttpd command exits 0 (success) that the syntax is valid. --- Most OS distros have migrated or are in the process of migrating to 64-bit time_t. However, lighttpd 1.4.75 will contain a workaround for older systems to address this issue with older libraries on armhf.
