Luminous Landscape Forum

Site & Board Matters => About This Site => Topic started by: KLaban on September 18, 2020, 04:18:42 am

Title: "Insecure Web Source"
Post by: KLaban on September 18, 2020, 04:18:42 am

On going to LuLa I'm getting a message from Kaspersky saying "Certificate not up to date" "Insecure web source". Not sure if this is of any significance: just a gentle heads up.

Title: Re: "Insecure Web Source"
Post by: josh.reichmann on September 18, 2020, 06:22:38 am

Thank you.
Yes, our webmaster is sorting out what needs to be updated.
Apologies for the interruption.

I’ll update or the issue will resolve very shortly.

Thanks again

Josh

Title: Re: "Insecure Web Source"
Post by: Eric Myrvaagnes on September 18, 2020, 10:50:37 am

I got the same thing from Bitdefender this morning.
I hope your webmaster gets it fixed soon.

Title: Re: "Insecure Web Source"
Post by: josh.reichmann on September 18, 2020, 01:13:35 pm

This should be fixed now.
Thanks for everyone’s patience.

Josh

Title: Re: "Insecure Web Source"
Post by: Ethan Hansen on September 18, 2020, 01:45:35 pm

Quote from: josh.reichmann on September 18, 2020, 01:13:35 pm

This should be fixed now.

Sorry, it's not. The LuLa site still presents an SSL certificate that expired Sept. 17, 2020. Browsers will continue to flag the site as "Not secure" until the certificate is updated.

Title: Re: "Insecure Web Source"
Post by: josh.reichmann on September 18, 2020, 02:02:44 pm

Quote from: Ethan Hansen on September 18, 2020, 01:45:35 pm

Sorry, it's not. The LuLa site still presents an SSL certificate that expired Sept. 17, 2020. Browsers will continue to flag the site as "Not secure" until the certificate is updated.

Yes. It’s being updated.
I spoke too soon.
Update imminent.

(All should be restored, many apologies for the log-in issues and temp shut out.)

Thank you

Josh

Title: Re: "Insecure Web Source"
Post by: Ethan Hansen on September 18, 2020, 03:11:07 pm

The new certificate is loaded, but the certificate chain order still presents the old one first. See the Qualys SSL report (https://www.ssllabs.com/ssltest/analyze.html?d=www.luminous-landscape.com) for details. Note: If you are not wedded to supporting 10+ year old versions of Android and IE on Windows 7 and 8, site security can be greatly improved by disabling weak and broken SSL cipher suites.

Title: Re: "Insecure Web Source"
Post by: MDL_SD on September 18, 2020, 04:39:10 pm

It now works to get to the main page, but there is still the error/trap when I go to the Forum page.

Title: Re: "Insecure Web Source"
Post by: paulazevedo on September 18, 2020, 05:50:59 pm

Hello Everyone,

I would like everyone to know that we are working on this issue. Our certificate is being renewed and is currently under review from our ssl provider. I will update the certificate as quickly as I can. Hopefully The certificate can be placed on the site in about an hour, this is how long I am being told the the review will take. I will post an update when the certificate is re implemented. Until then we have secured all access on the forum, but the blog remains unsecured. You can use the forum without worry, but you should be careful entering any personal information on the blog(i.e passwords) until the certificate is updated.

We hope this will be resolved soon.

Paul Azevedo,
Webmaster

Title: Re: "Insecure Web Source"
Post by: paulazevedo on September 18, 2020, 06:02:33 pm

We have finished updating the SSL Certificate, and access is secured throughout the entire site again. We are sorry for the delay and any time the site spent down while this issue was being resolved.

We hope you will continue to enjoy our services.
Paul Azevedo,
Webmaster

Title: Re: "Insecure Web Source"
Post by: Jonathan Cross on September 19, 2020, 06:24:48 pm

I got the not secure message today, 19 Sept, on my Mac running Catalina.

Jonathan

Title: Re: "Insecure Web Source"
Post by: Les Sparks on September 20, 2020, 03:05:24 pm

Microsoft Edge on up to date windows 10 gives site not secure on 9/20/2020 On main forum page it's OK but at least on the Insecure web source thread it give the site insecure notice