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

Knowing what DNS names are actually used.

EDIT: that's the flip side of supporting HTTPS that's not well-known among developers - by acquiring a legitimate certificate for your service to enable HTTPS, you also announce to the entire world, through a public log, that your service exists.





I don't really see how this is a flip-side. If you're putting something on the web, presumably you want it to be accessed by others, so this is actually a benefit.

If you didn't want others to access your service, maybe consider putting it in a private space.


There’s usages of https that don’t overlap with "the (public) web".

All of the internal stuff at $employer uses a private CA. I suspect this is fairly universal at places that aren't super tiny.

Problem is a lack of solutions that work at places that are tiny, such as a small company, or a household. This is yet another area of the computing ecosystem that forgets there are other use cases for computers than commerce.



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

Search: