Your message dated Sat, 1 Jun 2024 13:40:36 -0400 with message-id <ZltdFEbiij4dsO2V@xps13> and subject line Bug#1034586: fixed in lighttpd 1.4.76-1 has caused the Debian Bug report #1034586, regarding always reports inactive/expired certificate on armhf to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1034586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034586 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: lighttpd Version: 1.4.69-1 Severity: normal I am using the latest openssl and lighttpd packages on an armhf (with an arm64 kernel) and an amd64 system, and only on the armhf system I always get this warning at startup even just after having created a Let's Encrypt certificate. Apr 19 01:23:31 omitted.mi.bofh.it lighttpd[8876]: 2023-04-19 01:23:30: (mod_openssl.c.1335) SSL: inactive/expired X509 certificate '/var/lib/dehydrated/certs/omitted.mi.bofh.it/fullchain.pem' # openssl x509 -noout -text -in /var/lib/dehydrated/certs/bokassa.mi.bofh.it/fullchain.pem | grep -A2 Validity Validity Not Before: Apr 18 22:13:45 2023 GMT Not After : Jul 17 22:13:44 2023 GMT After looking at https://github.com/lighttpd/lighttpd1.4/blob/fdb7ffed88b9dfe09a51e7fb58e5ddfe938c1ec9/src/mod_openssl.c#L1284 I wonder if this is common on all 32 bit systems instead. -- ciao, Marco
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Source: lighttpd Source-Version: 1.4.76-1 Done: Glenn Strauss <[email protected]> We believe that the bug you reported is fixed in the latest version of lighttpd, which is due to be installed in the Debian FTP archive.
--- End Message ---
