|
|
|
|
|
by jeroenhd
329 days ago
|
|
Firefox sticks to the spec, Chrome makes you type out base64 manually to ignore the spec. The TLS errors that aren't unbypassible by specification (i.e. HSTS, see https://datatracker.ietf.org/doc/html/rfc6797) can be bypassed on Firefox just fine. It's only the ones where the spec says bypassing the error shouldn't be possible where Firefox takes a hard stance. Chrome had to alter their bypass string several times because vendors documented the override rather than fixing their insecure crapware. It makes total sense to me that Firefox does the same. |
|