Legacy and insecure SSL/TLS features (SSLv2 and SSLv3, SHA1RSA signatures, RC4 and 3DES ciphers, MD5 MAC, export ciphers, non PFS ciphers, <1024 DH parameters) are progressively being disabled by default and/or removed from browsers, and for good reason.Ī separate problem that helpfully flags is that of browser compatibility, in which case a legacy browser in a dedicated VM is probably the most robust solution. Three of the answers presently contributed require lowering the security level of your browser, possibly leaving you open to various attacks if you do this in your primary browser, subsequently use that browser for other web sites, or simply forget to revert this change (or multiple changes). It is not recommended to use these downgrades for normal browsing.
etc/chrome_dev.conf (read the comments in the file for more details) Restart the UI via: sudo restart uiĭo remember this may lower the security state of your browser. Put the device into dev mode so you can get a root shell Modify (If you are using a different named chrome/chromium build, change the Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome -fooĮxit any running instance of chrome. Applications/Utilities/Terminal.app At the command prompt enter: New shortcut to launch chrome with the new command line flags.
\chrome.exe" -foo -bar=2 Double click the Shortcut, and select Properties At the very end of the Target: textīox, add a space and then the desired command line flags. Create a copy of it Right click on the new How to set command line flags on Chrome.Įxit any running-instance of chrome. In Google Chrome, you can use the -ssl-version-max and -ssl-version-min command line flags to select a specific protocol verison.
0 kommentar(er)
