Hacker News Reader

What is shocking is that they still haven't found the way to properly fix it after 3 days.

I updated some SSL certificates last week (which even required contortions such as moving to a new issuer since some legacy software requires old-style SHA-1 signed ones which our current one doesn't provide), and it didn't take more than one (long) day of work.

View on HN

At this point, changing out a cert takes me about 15 minutes (typically for multiple servers). 10 of those is figuring out the order in which to include intermediate certs. I really should script that part out.

It's just embarrassing.

I can only assume the sysop is on holiday.

Checking their about page, they have 3 web developers, one of which wrote that post. That's worrying.

The available web developers may not have access to either the SSL vendor or where the certificate is stored. None of the front-end devs I work with have access to either of those things.

The first problem is solved by getting a new vendor. The second, well someone has to have access to that.

Reply on news.ycombinator.com