I can't bypass certificate warnings anymore (HSTS)
In short, I want to be able to bypass certificate warnings.
Yes, I've seen this: https://support.mozilla.org/en-US/questions/1169632 "When there is HSTS(HTTPS Strict Transport Security) set on the server, you cannot add a exception"
In less short, my case (because one needs to always justify one's methods), I set up a subdomain on a separate IP/host and I'm trying to test some project for which I use a webpage as a small visible part. However, the domain uses HSTS (HSTS == very nice).
However, I'm just casually testing something using a subdomain (or even a fake domain, or a real domain pointing to a new server being prepared, maybe using /etc/hosts) pointing to an external or internal IP on some old computer on my LAN or even on my own computer. And that's not possible anymore.
People should always have the option to bypass a warning, and I'm all for the warnings. If anything, there shouldn't have been a box with the option "always remember" ticked by default. There are other cases where this can be useful, some we don't even know yet.
الحل المُختار
hi, the spec for hsts says users should not be able to bypass certificate errors unfortunately: https://tools.ietf.org/html/rfc6797#section-12.1
Read this answer in context 👍 2All Replies (8)
الحل المُختار
hi, the spec for hsts says users should not be able to bypass certificate errors unfortunately: https://tools.ietf.org/html/rfc6797#section-12.1
Thanks for your reply, you've answered my question. It's sad though as this breaks many use cases.
Very regrettable. As Firefox loses more and more market share to Chrome, it has descended into net nanny mode telling users "you can't visit this site even if you understand and accept the risks of a just-expired SSL certificate". Is google paying you to drive more people to Chrome?
You can edit the SiteSecurityServiceState.txt file in the Firefox profile folder and remove lines that refer to a specific domain. Then you may be able to add an exception on the next visit.
cor-el said
You can edit the SiteSecurityServiceState.txt file in the Firefox profile folder and remove lines that refer to a specific domain. Then you may be able to add an exception on the next visit.
Thanks. This actually can work (while it is a bit of a pain to do).
cor-el said
You can edit the SiteSecurityServiceState.txt file in the Firefox profile folder and remove lines that refer to a specific domain. Then you may be able to add an exception on the next visit.
I'll check it out and let you know. In the meantime I switched to another browser because this SSL block is a false-positive on a site I trust and actually use to build webpages. The other browser allows you to easily toggle on/off that flag and proceed to the blocked site.
Modified by Mozy-zilla
The SiteSecurityServiceState.txt thing doesn't seem to work (unless perhaps I restart FF... I don't want to do that).
This is not a usable solution. :/
cor-el, what is this "other browser" you speak of ?
BatManuel said
cor-el, what is this "other browser" you speak of ?
This is Mozy-zilla, but the other browser is Yandex.