[ios] Removed CRLSets usage for WKWebView.

[ios] Removed CRLSets usage for WKWebView.

SecTrust API is used to make load/no-load decision for certs, while
CertVerifier is used to get rejection reason. Using CRLSets to get
rejection reason is impractical, because iOS blacklist is very
different from Chrome blacklist as well as cost to store CRLSets on
disk is very high.

BUG=None

Committed: https://crrev.com/c8fa67cfb0a220dc259cd433c2f5496b6fb80cbc
Cr-Commit-Position: refs/heads/master@{#361212}

[Eugene But (OOO till 7-30), 2015-11-19 17:17:37]

Description was changed from

==========
[ios] Removed CLRSet usage for WKWebView.

SecTrust API is used to make load/no-load decision for certs, while
CertVerifier is used to get rejection reason. Using CLRSet to get
rejection reason is impractical, because iOS blacklist is very
different as well as const to store CRLSet on disk is very high.

BUG=None
==========

to

==========
[ios] Removed CLRSet usage for WKWebView.

SecTrust API is used to make load/no-load decision for certs, while
CertVerifier is used to get rejection reason. Using CLRSet to get
rejection reason is impractical, because iOS blacklist is very
different from Chrome blacklist as well as cost to store CRLSet on
disk is very high.

BUG=None
==========

[Eugene But (OOO till 7-30), 2015-11-19 17:18:50]

eugenebut@chromium.org changed reviewers:
+ rsleevi@chromium.org

[Eugene But (OOO till 7-30), 2015-11-19 17:18:51]

I see your OOO (no review status), but this CL can sit here for a while w/o
review.

[Ryan Sleevi, 2015-11-23 22:25:51]

Description was changed from

==========
[ios] Removed CLRSet usage for WKWebView.

SecTrust API is used to make load/no-load decision for certs, while
CertVerifier is used to get rejection reason. Using CLRSet to get
rejection reason is impractical, because iOS blacklist is very
different from Chrome blacklist as well as cost to store CRLSet on
disk is very high.

BUG=None
==========

to

==========
[ios] Removed CRLSet usage for WKWebView.

SecTrust API is used to make load/no-load decision for certs, while
CertVerifier is used to get rejection reason. Using CRLSet to get
rejection reason is impractical, because iOS blacklist is very
different from Chrome blacklist as well as cost to store CRLSet on
disk is very high.

BUG=None
==========

[Ryan Sleevi, 2015-11-23 22:26:12]

Reworded description to say CRLSets and not CLRSet. LGTM with nit.

https://codereview.chromium.org/1465513002/diff/1/ios/web/net/crw_cert_verifi...
File ios/web/net/crw_cert_verification_controller.mm (right):

https://codereview.chromium.org/1465513002/diff/1/ios/web/net/crw_cert_verifi...
ios/web/net/crw_cert_verification_controller.mm:434: // of low benefits and high
cost of storing CRLSet on the disk.
Reword:
// CRLSets are not used, as the OS is used to make load/no-load decisions, not
the CertVerifier.

[Eugene But (OOO till 7-30), 2015-11-23 22:35:36]

Description was changed from

==========
[ios] Removed CRLSet usage for WKWebView.

SecTrust API is used to make load/no-load decision for certs, while
CertVerifier is used to get rejection reason. Using CRLSet to get
rejection reason is impractical, because iOS blacklist is very
different from Chrome blacklist as well as cost to store CRLSet on
disk is very high.

BUG=None
==========

to

==========
[ios] Removed CRLSets usage for WKWebView.

SecTrust API is used to make load/no-load decision for certs, while
CertVerifier is used to get rejection reason. Using CRLSets to get
rejection reason is impractical, because iOS blacklist is very
different from Chrome blacklist as well as cost to store CRLSets on
disk is very high.

BUG=None
==========

[Eugene But (OOO till 7-30), 2015-11-23 22:36:00]

https://codereview.chromium.org/1465513002/diff/1/ios/web/net/crw_cert_verifi...
File ios/web/net/crw_cert_verification_controller.mm (right):

https://codereview.chromium.org/1465513002/diff/1/ios/web/net/crw_cert_verifi...
ios/web/net/crw_cert_verification_controller.mm:434: // of low benefits and high
cost of storing CRLSet on the disk.
On 2015/11/23 22:26:12, Ryan Sleevi wrote:
> Reword:
> // CRLSets are not used, as the OS is used to make load/no-load decisions, not
> the CertVerifier.

Done.

[Eugene But (OOO till 7-30), 2015-11-23 22:36:08]

The CQ bit was checked by eugenebut@chromium.org

[Eugene But (OOO till 7-30), 2015-11-23 22:36:09]

The patchset sent to the CQ was uploaded after l-g-t-m from rsleevi@chromium.org
Link to the patchset: https://codereview.chromium.org/1465513002/#ps20001
(title: "Updated comments")

[commit-bot: I haz the power, 2015-11-23 22:36:36]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1465513002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1465513002/20001

[commit-bot: I haz the power, 2015-11-23 23:12:37]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-11-23 23:14:03]

Patchset 2 (id:??) landed as
https://crrev.com/c8fa67cfb0a220dc259cd433c2f5496b6fb80cbc
Cr-Commit-Position: refs/heads/master@{#361212}