3 ms·

> https://www.kylheku.com/cygnal/ https://www.kylheku.com/cygnal/ Your SSL certificate is invalid and your server uses TLS 1.0 which is insecure and disabled b

• kazinator 5y ago
  > your server uses TLS 1.0 That is correct. Basically, the OS upgrades kept breaking my highly customized setup, resulting in downtime and wasted time, so eventually I dropped out of the program. I need to rebuild a new server and migrate everything over. With two small kids now and full-time job, if I have any block of free time (basically late at night or early morning), I prioritize putting it into working on code. It's not just a web server setup and custom things around it, but Postgress databases, e-mail setup and other stuff. Every item could have some issue chewing up hours. > which is insecure Secure/insecure isn't a simple Boolean. It's less secure than newer versions of the protocol, but it's not "insecure" like, say, a plain password sent over telnet. > Your SSL certificate is invalid I don't believe that is the case. Firstly, I've never had an problem connecting to the site using https from any browser. Secondly, most online SSL checking tools do not report a problem other than remarking on it being self-signed. For instance geocerts.com says "The hostname (www.kylheku.com) matches the certificate and the certificate is valid." I found one which doesn't understand wildcard names: it reports that www.kylheku.com doesn't match *.kylheku.com. That's a bug in the checker. One other flags some unspecified issue with the Alternative Names property (which I didn't even specify when generating the cert).