Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The problem with the, "was it signed by a trusted authority?" concept is that you generally can't automated the 3rd party since they're not under your control. Also, they typically charge every time you request a new certificate (even if client-only).

The solution to that is to run your own CA but then it won't be 3rd party anymore. It's sort of the catch-22 with SSL/TLS: Either you use a 3rd party or you get to automate things. There doesn't appear to be any middle ground.

Why is there no middle ground? Because if the 3rd party CA is doing their job they're investigating every single request for a new certificate. That means you can't just get a new client-side certificate on demand, instantaneously whenever the need arises.



"client developer not properly verifying the server certificate" makes it sound possible, but I think I understand the problem now maybe.

The 3rd party CA may have issued a cert to malicious party that issued another cert to their man in the middle.

You can't be sure unless you are your own CA, but then you aren't a 3rd party anymore.


> Either you use a 3rd party or you get to automate things. There doesn't appear to be any middle ground.

Have you seen Let's Encrypt?

https://letsencrypt.org/




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: