Re: Leaf 7.2.1 lighthtp certificate missing or invalid

Erich and list,

I apologise to everyone, I discovered that my lighttpd certificate problem
was very long standing and caused by myself. There is no problem with the
leaf distribution. Kp and I discussed this off-list, and I never reported
the resolution of this to the list. Here's a quote from my last message to
kp:

>>
... all I had to do to fix the lighttpd certificate problem was rename
/etc/ssl/private/lighttpd.pem to something else, save, and reboot. Then all
was well, and the correct pem file got copied to two places. This is
embarrassing, but the bad lighttpd.pem file had a timestamp of  April 2
2018!!!!! Yikes! I've been getting that error message for five years!!
>>

Let me add that my (too lazy) method of updating Leaf for many years has
been to copy configdb.lrp and leaf.cfg from my previous working copy. I am
long overdue for a major configdb.lrp cleanup!

Tim




On Tue, Apr 4, 2023 at 4:21 AM Erich Titl <[email protected]> wrote:

> Hi Tim
>
> Am 27.03.2023 um 03:46 schrieb Timothy Wegner:
> > A tiny issue - when I booted LEAF Bering-uClibc 7.2.1 I noticed an error
> > stating that the lighthtp certificate was missing or invalid. Lighthtp
> does
> > work OK though.
>
> A late question. Is the certificate missing or invalid? The certificate
> delivered with the distribution will most certainly be invalid as it
> will hardly ever match the https request. You will need to build your
> own matching certificate to fix this.
>
> ET
>
> ------------------------------------------------------------------------
> leaf-user mailing list: [email protected]
> https://lists.sourceforge.net/lists/listinfo/leaf-user
> Support Request -- http://leaf-project.org/
>

------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/