Bug#1034586: always reports inactive/expired certificate on armhf

2024-03-06 Thread Glenn Strauss
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

Bug#1034586: always reports inactive/expired certificate on armhf

2023-09-10 Thread gs-bugs . debian . org
Marco, please review my previous messages and try to help provide additional information. Thank you. Glenn

Bug#1034586: always reports inactive/expired certificate on armhf

2023-05-11 Thread gs-bugs . debian . org
Macro, please review my previous messages and try to help provide additional information. Thank you. Glenn

Bug#1034586: always reports inactive/expired certificate on armhf

2023-05-02 Thread gs-debian . org
On Tue, May 02, 2023 at 02:35:05AM -0400, gs-debian@gluelogic.com wrote: > On Fri, Apr 21, 2023 at 01:47:22PM -0400, gs-debian@gluelogic.com wrote: > > On Fri, Apr 21, 2023 at 06:14:25PM +0200, Marco d'Itri wrote: > > > On Apr 21, gs-debian@gluelogic.com wrote: > > > > > > > I

Bug#1034586: always reports inactive/expired certificate on armhf

2023-05-02 Thread gs-debian . org
On Fri, Apr 21, 2023 at 01:47:22PM -0400, gs-debian@gluelogic.com wrote: > On Fri, Apr 21, 2023 at 06:14:25PM +0200, Marco d'Itri wrote: > > On Apr 21, gs-debian@gluelogic.com wrote: > > > > > I probably should have started with the most basic thing: > > > > > > What is the date on your

Bug#1034586: always reports inactive/expired certificate on armhf

2023-04-21 Thread gs-debian . org
On Fri, Apr 21, 2023 at 06:14:25PM +0200, Marco d'Itri wrote: > On Apr 21, gs-debian@gluelogic.com wrote: > > > I probably should have started with the most basic thing: > > > > What is the date on your device? > NTP-accurate. Perhaps there is something amiss in the Debian 32-bit build of

Bug#1034586: always reports inactive/expired certificate on armhf

2023-04-21 Thread Marco d'Itri
On Apr 21, gs-debian@gluelogic.com wrote: > I probably should have started with the most basic thing: > > What is the date on your device? NTP-accurate. -- ciao, Marco signature.asc Description: PGP signature

Bug#1034586: always reports inactive/expired certificate on armhf

2023-04-21 Thread gs-debian . org
On Fri, Apr 21, 2023 at 09:38:31AM +0200, Marco d'Itri wrote: > On Apr 21, gs-debian@gluelogic.com wrote: > > > What your `uname -a` ? > Linux omitted.mi.bofh.it 6.1.0-7-arm64 #1 SMP Debian 6.1.20-2 (2023-04-08) > aarch64 GNU/Linux > > > What is the output of the following for you? > > $

Bug#1034586: always reports inactive/expired certificate on armhf

2023-04-21 Thread Marco d'Itri
On Apr 21, gs-debian@gluelogic.com wrote: > What your `uname -a` ? Linux omitted.mi.bofh.it 6.1.0-7-arm64 #1 SMP Debian 6.1.20-2 (2023-04-08) aarch64 GNU/Linux > What is the output of the following for you? > $ lighttpd -V | grep "Y2038 support" > + Y2038 support Same. Thank you for

Bug#1034586: always reports inactive/expired certificate on armhf

2023-04-21 Thread gs-debian . org
On Fri, Apr 21, 2023 at 07:41:13AM +0200, Marco d'Itri wrote: > On Apr 21, gs-debian@gluelogic.com wrote: > > > Please confirm you are running an arm64 kernel, as you posted above. > Confirmed. What your `uname -a` ? What is the output of the following for you? $ lighttpd -V | grep "Y2038

Bug#1034586: always reports inactive/expired certificate on armhf

2023-04-20 Thread Marco d'Itri
On Apr 21, gs-debian@gluelogic.com wrote: > Please confirm you are running an arm64 kernel, as you posted above. Confirmed. > What lighttpd package (from which architecture) do you have installed? > $ file /usr/sbin/lighttpd root@omitted:~# /usr/sbin/lighttpd -f /etc/lighttpd/lighttpd.conf

Bug#1034586: always reports inactive/expired certificate on armhf

2023-04-20 Thread gs-debian . org
On Wed, Apr 19, 2023 at 01:39:02AM +0200, Marco d'Itri wrote: > 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

Bug#1034586: always reports inactive/expired certificate on armhf

2023-04-18 Thread Marco d'Itri
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