3 ms·
That seems a bit harsh, it's a wildcard cert on onelogin.com and they have a 'catch all' DNS on there which will break ssl for anything above that: https://mas
by cyberpunk 10y ago
That seems a bit harsh, it's a wildcard cert on onelogin.com and they have a 'catch all' DNS on there which will break ssl for anything above that:
https://massive.bag.of.dicks.pinterest.onelogin.com https://massive.bag.of.dicks.pinterest.onelogin.com
Is www.pt.ol.com linked from anywhere?
- chris_wot 10y agoThe fact they have a "catch all" DNS resolver for an SSL-based website that is an interface for admins and end users alike that is guaranteed to fail says a lot about their ability to sell a secure product.
- cyberpunk 10y agoAnd how else would you let your users have a subdomain login url? Why bother generating specific certs and dns for each when you can just use the HOST header for the login and use a wildcard? This is totally common and used in a lot of places.. I mean: https://bigger.bag.of.dicks.signin.aws.amazon.com/ https://bigger.bag.of.dicks.signin.aws.amazon.com/
- chris_wot 10y agoBecause those Certs weren't designed for this scenario. The fact that you can create that domain name to resolve is funny. I can think of a few phishing schemes I could use with this, if I were so inclined.
- cyberpunk 10y agoThis was designed for exactly that sort of scenario. If you're runnin a SAAS then this is totally common practice, it's used by at least AWS, Slack, and GitHub off the top of my head.. Are you saying these companies are doing something stupid? How could you phish github or aws by using their dns/cert setup as they intended it to be used?