| ▲ | The difficulty of making sure your website is broken(letsencrypt.org) | ||||||||||||||||
| 28 points by mcpherrinm 3 hours ago | 9 comments | |||||||||||||||||
| ▲ | paulirish 2 hours ago | parent | next [-] | ||||||||||||||||
https://badssl.com/ also offers several test subdomains in the same vein. | |||||||||||||||||
| ▲ | ipython an hour ago | parent | prev | next [-] | ||||||||||||||||
Interesting. Chrome (146, macOS) shows no error messages on the revoked cert pages, but Firefox does (also macOS). | |||||||||||||||||
| |||||||||||||||||
| ▲ | lifis an hour ago | parent | prev | next [-] | ||||||||||||||||
Vanadium, Chrome and Firefox (all for Android) all accept all the revoked certificates... But revoked.badssl.com is considered revoked | |||||||||||||||||
| |||||||||||||||||
| ▲ | bullen 2 hours ago | parent | prev [-] | ||||||||||||||||
Meanwhile HTTP keeps working just fine and is decentralized. Just "add your own crypto" on top, which is the ONLY thing a sane person would do. 3... 2... 1... banned? | |||||||||||||||||
| |||||||||||||||||