4 ms·
FYI you can get around HSTS errors on Chromium-based browsers by typing thisisunsafe. Source: https://chromium.googlesource.com/chromium/src/+/d8fc089b62cd4f8d
by input_sh 4y ago
FYI you can get around HSTS errors on Chromium-based browsers by typing thisisunsafe.
Source: https://chromium.googlesource.com/chromium/src/+/d8fc089b62cd4f8d907acff6fb3f5ff58f168697 https://chromium.googlesource.com/chromium/src/+/d8fc089b62c...
- d_k_f 4y agoAdditionally, you can remove stored HSTS states using Chrome's chrome://net-internals configuration page.
- forgotmypw17 4y agoNot anymore: >The net-internals events viewer and related functionality has been removed. Please use chrome://net-export to save netlogs and the external netlog_viewer to view them.
- d_k_f 4y agoInteresting (and sad), thanks for the correction. I was using "Kiwi Browser" on mobile to ensure I had the right address, which is a Chrome fork that allows extensions (I think they're forking Chrome instead of "just" Chromium since it looks and feels like regular Chrome otherwise). In here, I still have it available. Might be high time to check for something similar on the desktop.
- kbelder 4y agoDoesn't that page indicate something else? /** * This allows errors to be skippped by typing a secret phrase into the page. * @param {string} e The key that was just pressed. */ function handleKeypress(e) { // HTTPS errors are serious and should not be ignored. For testing purposes, // other approaches are both safer and have fewer side-effects. // See https://goo.gl/ZcZixP for more details. var BYPASS_SEQUENCE = window.atob('dGhpc2lzdW5zYWZl'); if (BYPASS_SEQUENCE.charCodeAt(keyPressState) == e.keyCode) { keyPressState++; if (keyPressState == BYPASS_SEQUENCE.length) { sendCommand(SecurityInterstitialCommandId.CMD_PROCEED); keyPressState = 0; } } else { keyPressState = 0; } }
- wlonkly 4y agowindow.atob('dGhpc2lzdW5zYWZl'); evaluates to thisisunsafe