Switch NaCl to use_byte_certs.

Switch NaCl to use_byte_certs.

The NaCl build (used by //remoting) doesn't actually process
certificates, so we can switch them easily. (They configure
SSLClientSocket to allow only a single certificate and run some other
authenticator over the channel.)

Sadly, this doesn't buy the binary size wins yet. It looks like this is
because they pull in WebRTC. But it means that once this and the Android
switch sticks, we can tidy up USE_OPENSSL_CERTS.

BUG=671420
Review-Url: https://codereview.chromium.org/2861813002
Cr-Commit-Position: refs/heads/master@{#469213}
Committed: https://chromium.googlesource.com/chromium/src/+/7c97df67012325269eaf4a3f627e442f47266bbb

[davidben, 2017-05-03 18:10:34]

The CQ bit was checked by davidben@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-05-03 18:11:12]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[davidben, 2017-05-03 19:35:14]

davidben@chromium.org changed reviewers:
+ mattm@chromium.org

[mattm, 2017-05-03 19:53:21]

lgtm

[davidben, 2017-05-03 19:59:57]

The CQ bit was checked by davidben@chromium.org

[davidben, 2017-05-03 20:00:00]

The CQ bit was unchecked by davidben@chromium.org

[davidben, 2017-05-04 00:11:23]

The CQ bit was checked by davidben@chromium.org

[commit-bot: I haz the power, 2017-05-04 00:12:10]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-05-04 00:20:31]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1493856683190110, "parent_rev":
"070b9d4999b7617e092b3f47ef4f936446f9612b", "commit_rev":
"7c97df67012325269eaf4a3f627e442f47266bbb"}

[commit-bot: I haz the power, 2017-05-04 00:22:01]

Description was changed from

==========
Switch NaCl to use_byte_certs.

The NaCl build (used by //remoting) doesn't actually process
certificates, so we can switch them easily. (They configure
SSLClientSocket to allow only a single certificate and run some other
authenticator over the channel.)

Sadly, this doesn't buy the binary size wins yet. It looks like this is
because they pull in WebRTC. But it means that once this and the Android
switch sticks, we can tidy up USE_OPENSSL_CERTS.

BUG=671420
==========

to

==========
Switch NaCl to use_byte_certs.

The NaCl build (used by //remoting) doesn't actually process
certificates, so we can switch them easily. (They configure
SSLClientSocket to allow only a single certificate and run some other
authenticator over the channel.)

Sadly, this doesn't buy the binary size wins yet. It looks like this is
because they pull in WebRTC. But it means that once this and the Android
switch sticks, we can tidy up USE_OPENSSL_CERTS.

BUG=671420

Review-Url: https://codereview.chromium.org/2861813002
Cr-Commit-Position: refs/heads/master@{#469213}
Committed:
https://chromium.googlesource.com/chromium/src/+/7c97df67012325269eaf4a3f627e...
==========

[commit-bot: I haz the power, 2017-05-04 00:22:02]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/7c97df67012325269eaf4a3f627e...