My Chrome flags this site as not secure, but it doesnt tell me why which is strange.

EDIT: Looking at it, chrome seems to hide all security info about sites now and only display a generic 'Not Secure' badge for anything. This is a very awkward change and removes lots of convenience when troubleshooting random sites.

Still, the site needs to fix its SSL certificate.

▲ pred_ 2 hours ago | parent | next [-]

The SSL certificate is fine; the site just redirects from https to http for whatever reason, so you end up with no certificate at all. There's no SSL issue for Chrome to report about.

    $ curl -v https://pigshell.com 2>&1 | grep Location
    < Location: http://pigshell.com

	▲	alt227 an hour ago \| parent [-]
		I think it was the fact that by default Chrome hides the protocol from the url, so I could'nt see at a glance it was downgraded. This is exactly what I was talking about when mentioning chrome removing this stuff was hindering troubleshooting. Once I found the setting in chrome to always show the http section, it became clear what was happening.

▲ thesuitonym 2 hours ago | parent | prev | next [-]

This is an HTTP site. There is no SSL certificate. That's why Chrome isn't telling you anything, it's not that the site is insecure, it's just that it's not secure.

▲ thaumaturgy 4 hours ago | parent | prev [-]

Firefox simply loads the page without complaint, just mentions that it's "not secure" and puts a broken lock icon in the addressbar.

Firefox is nice.

▲

alt227 4 hours ago | parent | next [-]

I used Firefox as my daily driver for 15 years. Switched to chrome a couple months ago to see what the fuss was about.

I am shocked at how glitchy chrome is in comparison, with the likes of crashed dev tools panels and tabs that just dont come back properly after being idled being a regular thing.

I will be returning to Firefox before long I am sure of it.

▲

Wowfunhappy 4 hours ago | parent | prev [-]

On the other hand, if a page has HSTS Firefox absolutely won't let you see the page under any circumstances no matter what, whereas Chrome at least has a hidden `thisisunsafe` bypass.

▲

3 hours ago | parent | next [-]

[deleted]

▲

Brian_K_White 3 hours ago | parent | prev [-]

You can do it, and without rebuilding from hacked source, but it's more work than install $anythingelse, use once, uninstall.

When I searched "firefox bypass hsts" I got a years-long thread where a mozilla dev said how to do it.

Just finding and merely reading that post was more work than install foobrowser, search how to use it's bypass method, use once, uninstall.

Since it's possible, seems ripe for a plugin? Is that something plugins can touch? IDK, as before the nuclear option is actually more convenient. Meanwhile the browsers with nerfed plugins actually empower the user more at least on this point.

Proves that monoculture is bad even if it's your favorite that wins. If it was FF that was taking over everything instead of chromium, then it would be chromium proving that monoculture is bad.

▲

Wowfunhappy 2 hours ago | parent [-]

> You can do it, and without rebuilding from hacked source, but it's more work than install $anythingelse, use once, uninstall.

Please share because I was under the impression it was literally impossible and would like to know how to do this.

	▲	Brian_K_White 2 hours ago \| parent [-]
		I did. What happened when you tried 'I searched "firefox bypass hsts"' ? https://kagi.com/search?q=firefox%20bypass%20hsts top result (at least on kagi for me at the moment) -> https://connect.mozilla.org/t5/ideas/allow-firefox-to-bypass... 5th comment still close to the top -> https://connect.mozilla.org/t5/ideas/allow-firefox-to-bypass... (untested by me)