summaryrefslogtreecommitdiffstats
path: root/components/ssl_config
Commit message (Collapse)AuthorAgeFilesLines
* Remove the RC4 field trial.davidben2016-03-071-11/+1
| | | | | | | | | | | | | The removal has survived a release cycle without needing the field trial. This can probably be removed now. The rc4_enabled field in SSLConfig still needs to remain for a little while longer; the admin policy has a few more release cycles on it. BUG=375342 Review URL: https://codereview.chromium.org/1771923002 Cr-Commit-Position: refs/heads/master@{#379628}
* Disable the TLS version fallback.davidben2016-02-243-2/+68
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This sets the default minimum TLS fallback version to TLS 1.2. The code is retained for now to support a resurrected SSLVersionFallbackMin admin policy. The policy is set to expire in Chrome 53, matching the timeline for the previous fallback removal. As an escape hatch (but I don't expect to need it), it's also connected to a field trial. This also tweaks the fallback code. The TLS 1.0 fallback leg is now completely gone (the admin policy expired) and ERR_SSL_FALLBACK_BEYOND_MINIMUM_VERSION hits have leveled off (see Net.ErrorCodesForMainFrame3), cap the fallback code to TLS 1.1. We will no longer even try TLS 1.0 ClientHellos for the purposes of showing the error code. This will decrease the amount of time it takes to show an error page in some cases. The ssl_version_fallback_min toggle is also tweaked to reject all values below TLS 1.1, so that the resurrected admin policy cannot be used to set the value at TLS 1.0 again. (Though it would be moot due to the above change.) We'll also want to add a link to some to-be-written Help Center article on the error page, but that'll be done separately after chatting with UI folks. BUG=536200,583787 Review URL: https://codereview.chromium.org/1682623002 Cr-Commit-Position: refs/heads/master@{#377352}
* Update components for new prefs location.brettw2016-02-013-5/+6
| | | | | | | | | | | | | | | | This is a search-and-replace update for includes with "base/prefs" -> "components/prefs" and the headers re-sorted. DEPS files were updated to allow the components in question to depend on components/prefs. This should be a no-op from a build perspective. BUG=583034 Review URL: https://codereview.chromium.org/1651203002 Cr-Commit-Position: refs/heads/master@{#372780}
* Update GN build files for new prefs location.brettw2016-01-301-2/+2
| | | | | | | | | | Updates references from //base:prefs to //components/prefs/ TBR=jam@chromium.org Review URL: https://codereview.chromium.org/1652573002 Cr-Commit-Position: refs/heads/master@{#372540}
* Switch to standard integer types in components/, part 3 of 4.avi2015-12-251-12/+14
| | | | | | | | | BUG=138542 TBR=blundell@chromium.org Review URL: https://codereview.chromium.org/1551433002 Cr-Commit-Position: refs/heads/master@{#366874}
* Add more components to "gn check"brettw2015-11-271-0/+3
| | | | | | | | | | | | | | | | | | | | | | omnibox search_engines search_provider_logos security_interstitials service_tab_launcher session_manager sessions signin ssl_config ssl_errors This also moves net/test/test_certificate_data.h from net_unittests to net_test_support in both the GYP and the GN builds, because it is being used in a bunch of places outside of net. TBR=dpranke (random GN) TBR=bnc (net) Review URL: https://codereview.chromium.org/1479093002 Cr-Commit-Position: refs/heads/master@{#362027}
* Remove RC4 by default.davidben2015-10-303-0/+20
| | | | | | | | | | | | | | | | | | | | RC4 may still be re-enabled via the RC4Enabled administrative policy, until sometime around September. Also control it via a field trial so we still have an escape hatch should something catastrophic happen. Keep the deprecated cipher suite fallback around (rename the parameter since I got the naming convention wrong) since it's still got the IIS AES-GCM workaround in it, and it will be used in not too long for DHE_RSA instead. BUG=375342 TEST=Loading https://rc4.badssl.com/ fails with ERR_SSL_VERSION_OR_CIPHER_MISMATCH Relaunching Chrome with --force-fieldtrials=RC4Ciphers/Enabled/ makes that page succeed. Relaunching Chrome after setting the RC4Enabled polcy to true makes that page succeed. (Note: press refresh when loading the site to make sure it's not cached.) Review URL: https://codereview.chromium.org/1422293002 Cr-Commit-Position: refs/heads/master@{#357114}
* Remove unused constant.davidben2015-10-272-2/+0
| | | | | | | | | | | https://codereview.chromium.org/1320533007/ was rebased incorrectly and restored a removed preference. BUG=none Review URL: https://codereview.chromium.org/1405253006 Cr-Commit-Position: refs/heads/master@{#356384}
* Componentize ssl_config_service_manager_pref.ccabhishek.a212015-10-2010-0/+657
. Removed not needed notifications. . Created new switches and prefs for ssl_config. . Using SingleThreadTaskRunner over BrowserThread to remove content dependencies. BUG=517014 TBR=jochen Review URL: https://codereview.chromium.org/1320533007 Cr-Commit-Position: refs/heads/master@{#355038}