[ZendTo] Web site certificate expiration

[jules at zend.to]

Hi folks!

Don't worry, I'm still alive. :-)
And not even been in hospital (apart from the odd scan so they can keep 
an eye on me) :-O

Just been super-busy at work.

Sorry about the website cert, just fixed it.

And yes, I must fix the broken apt repo. Think I'm better off deleting 
it altogether and creating a new one, rather than trying to resurrect 
the existing one as lots of things appear to have changed over the 
years. Anyone know any good guides on constructing an apt repo from 
scratch if you've already got a GPG key? That would help speed things up 
a lot...

Thanks!
Jules.

On 22/04/2025 6:51 pm, Matthew Fey via ZendTo wrote:
>
> I haven’t seen anything from him since the mailing list in November, 
> but 6.15-7 was released on Feb 11, so it appears he was active up 
> until then at least, assuming he’s the one releasing the updates.
>
> *From:*ZendTo <zendto-bounces at zend.to> *On Behalf Of *Scott Silva via 
> ZendTo
> *Sent:* April 22, 2025 12:44 PM
> *To:* ZendTo Users <zendto at zend.to>
> *Cc:* Scott Silva <ssilva at sgvwater.com>
> *Subject:* Re: [ZendTo] Web site certificate expiration
>
> I know thru the years Jules has had health problems. Maybe he is in 
> the hospital again?
>
> I have been involved with his work since way back in the Mailscanner days…
>
> *From:*ZendTo <zendto-bounces at zend.to> *On Behalf Of *John Thurston 
> via ZendTo
> *Sent:* Tuesday, April 22, 2025 10:29 AM
> *To:* ZendTo List <zendto at zend.to>
> *Cc:* John Thurston <john.thurston at alaska.gov>
> *Subject:* [ZendTo] Web site certificate expiration
>
> From my perspective, the cert at zend.to (port 443) is expired. It 
> appears to have been a Let's Encrypt cert, so should have been 
> scripted to auto-renew. My read of this is no one has been watching 
> the server error-logs for a coup
>
> *External sender*<zendto at zend.to>
> Make sure you trust this sender before taking any actions.
>
> From my perspective, the cert at zend.to (port 443) is expired. It 
> appears to have been a Let's Encrypt cert, so should have been 
> scripted to auto-renew. My read of this is no one has been watching 
> the server error-logs for a couple of months.
>
>     Certificate chain
>      0 s:CN=zend.to
>        i:C=US, O=Let's Encrypt, CN=E5
>        a:PKEY: id-ecPublicKey, 256 (bit); sigalg: ecdsa-with-SHA384
>        v:NotBefore: Jan 22 14:45:30 2025 GMT; NotAfter: Apr 22
>     14:45:29 2025 GMT
>
> Will it come back?
> Has anyone heard from Jules in the last three months?
>
> -- 
> --
> Do things because you should, not just because you can.
> John Thurston    907-465-8591
> John.Thurston at alaska.gov
> Department of Administration
> State of Alaska
>
> This email transmission, and any documents, files or previous e-mail 
> messages attached to it, may contain confidential, privileged and/or 
> proprietary information for the sole use of the intended recipient(s). 
> If you are not an intended recipient or a person responsible for 
> delivering it to an intended recipient, any disclosure, copying, 
> distribution or use of any of the information contained in or attached 
> to this transmission is strictly prohibited. If you have received this 
> transmission in error, please: (1) immediately notify me by reply 
> e-mail; and (2) destroy the original (and any copies) of this 
> transmission and its attachments without reading or saving in any manner.
>
>
> _______________________________________________
> ZendTo mailing list
> ZendTo at zend.to
> http://jul.es/mailman/listinfo/zendto

Jules

-- 
Julian Field MEng CEng CITP MBCS MIEEE

'Teach a man to reason, and he will think for a lifetime.' - Phil Plait

www.Zend.To

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20250423/c251744f/attachment-0001.html>