Hacker News Reader

I'd like to know as well. At my work we had to partner with a major bank and they demanded a fully signed (sigh) client certificate for the integration. The way their API works means that we have to do a planned hard-cutover before the certificate expires. There's a 60% chance that we'll have trouble reaching out to the right people when the time comes.

Ugh.

View on HN

This is a common problem in healthcare insurance. API connections will stop working for about 3 weeks every year as each side performs a complicated dance of noticing the expiration and updating the systems to accept a new public certificate.

Seems to be a thing that happens at big companies in general. I add —-no-ssl-verify to everything and it saves my ass every single year.

That's ok if you're not worried about man in the middle attacks, but it does make it a lot less secure.

IMHO, 60% sounds low...

Reply on news.ycombinator.com