Switch Linux and CrOS to BoringSSL.

Switch Linux and CrOS to BoringSSL.

This is a reland of https://codereview.chromium.org/1210073014/ with fixes to
Linux expected shared library dependencies per
http://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Linux%20x64/builds/2784/steps/compile/logs/stdio

On the dpkg side, the inferred minimum NSS version goes down because we no
longer use PK11_SignWithSymKey. (The actual version is still overwritten in
build.sh.)

On the rpm side, we no longer use any function from libplc4.so (there used to
be a PL_strdup call), so the linker prunes it.

If this causes problems, please revert first and ask questions
later.

BUG=462040
TBR=rsleevi@chromium.org,thakis@chromium.org

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

[davidben, 2015-07-14 20:55:58]

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

[davidben, 2015-07-14 20:55:59]

mmoss for chrome/installer/*. See commit message for why dependencies changed.

TBR rsleevi and thakis as this is otherwise the exact same CL you reviewed
previously.

[davidben, 2015-07-14 21:00:16]

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

[davidben, 2015-07-14 21:00:17]

+thestig for chrome/installer/linux since mmoss seems to be OOO.

[Lei Zhang, 2015-07-14 22:22:35]

On 2015/07/14 21:00:17, David Benjamin wrote:
> +thestig for chrome/installer/linux since mmoss seems to be OOO.

lgtm

[davidben, 2015-07-14 22:28:46]

The CQ bit was checked by davidben@chromium.org

[commit-bot: I haz the power, 2015-07-14 22:30:10]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1231723003/1

[commit-bot: I haz the power, 2015-07-14 23:56:14]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-07-14 23:57:25]

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

[Matt Giuca, 2015-07-21 04:36:51]

Just looking at the sizes bot on chromium-rel-linux-64 [1], it seems this patch
introduced a size regression of about 900 kB. Doesn't necessarily need a revert;
depends on whether this is preventable. http://crbug.com/512322.

[Ryan Sleevi, 2015-07-21 04:41:55]

On 2015/07/21 04:36:51, Matt Giuca wrote:
> Just looking at the sizes bot on chromium-rel-linux-64 [1], it seems this
patch
> introduced a size regression of about 900 kB. Doesn't necessarily need a
revert;
> depends on whether this is preventable. http://crbug.com/512322.

Yeah, this is to be expected. We are now statically linked in BoringSSL, whereas
previously (well, technically, still) we dynamically link in the (system) NSS.

The size hit is expected, and we're still trimming down the BoringSSL bits (NSS
is ~4.5MB, the BoringSSL optimized crypto and paths are around 100K alone, w/o
any SSL bits)