This CL tweaks the roller scripts to ensure they can roll again with
the changes to //zircon/third_party/ulib/boringssl.

Bug: 42672
Change-Id: I26cf882c4444916289b3780eb8193f05c9274893

This CL removes some ununsed files and extracts the source lists needed
by the Zircon build into a 'zircon.gni' file. This allows the upstream
code and the source lists to be updated atomically.

Bug: 41904
Change-Id: Ibc61ba48424a620ed62e47e40aa9a6c1e673fa49

This CL restricts the fuzzed versions of libcrypto and libssl to only
be available to the fuzzers. It also tries to more gracefully handle
the name collision between the fuzzers_package template and the
generated .gni file.

Change-Id: I849c2406c1e574f34c591cbfc41a12a08ce02d8a

fxr/279893 introduced a typo that wasn't caught by CQ. The parameter in
question is deprecated, so this change removes it entirely.

Change-Id: I4de236d605e9b1e191a84e8f20df6f49bd064771

This is part of the "soft" transition from fuzz_target to fuzzer.

Change-Id: I14b328a9d9d7cef36ab543663baf5007ab2f967c

Change-Id: I965e61a4bd21c6b440d91edfb72935203d2c05dd

BUG: SEC-310

Preflight to ensure introduction of the new ambient replace_as_executable
job policy restrictions.

Change-Id: Iedd3c9c13b58c996c763ee95991c9526fe1ee580

Change-Id: I7176f4605718ca4c737a04862e53d7531606f131

Change-Id: Ie91972c98cac95e64165957ff1ab024ba8747305

This CL removes the optional corpora veriable from the fuzz_targets
ahead of its removal from the template.

SEC-225

Change-Id: Ic4c8aae124fb53219483e8c9cbaca1455017a176

This is an autogenerated roll of BoringSSL from upstream.

Test: fx run-test boringssl_tests
Change-Id: I878c47f02de2ae1df87d2d3ce33e1004f9a34e5d

This CL updates the roller scripts to incorporate two major changes to
the Fuchsia project:
 1. Jiri manifests have been moved to an internal integration repo.
 2. The "stem", including zircon and garnet has been made monorepo.

The result of both of these changes is that roll_boringssl.go script can
no longer update manifests, and thus no longer needs to make commits
automatically (which was previously error-prone).  Updating the internal
manifests is now a manual step. A 'check-integration' script is added to
make it simple, and the README.fuchsia has been updated with current
instructions.

Change-Id: I906ce9da89758a2e05887da54cd96dd7078a8c44

Change-Id: I24bb8c9957803f7ef206795d1e187ec88b3f5ae9

zxcpp is deprecated and superfluous with static libc++.

Bug: ZX-1751 #comment Removed boringssl users of zxcpp
Test: CQ
Change-Id: I5fb147ec5fa236c8d7ef4551c072208c073bbc41

Bug: None
Tests: None
Change-Id: Icd8d33863f2177c208ef8869f3a9d930f0477d65

googletest renamed some API functions, but BoringSSL hasn't moved
forward. Rather than fork the BoringSSL code for such a small reason
(TEST_CASE->TEST_SUITE), just disable that warning (in test code only)
for now.

INTK-682 #comment [googletest] Suppress -Wdeprecated-declarations in tests

Test: CQ
Change-Id: I079b6c42123d9a52d1b9c581fa5e31c761c2a23c

Test: successfully built
Bug: DX-690
Change-Id: I5272dd2c8ffbcec6b551dde7dc98a7693f5ccbc6

This CL adds the upstream fuzzers into BUILD.gn

SEC-44 #comment Use BoringSSL as an example

Tests: Manually ran fuzzers

Change-Id: I903a5640378e58d648da438221bfce0f79ef6dfb

This CL condenses the CPU and OS detection and pulls it out of the
libcrypto rule.  There's only three supported cases and enumerating
them makes them much clearer.

SEC-44 #comment Using boringssl as an example

Change-Id: I993103699f506163a2de907460d41e36ed9e639a
Tests: Garnet's boringssl_tests

ZX-2801

Tests: Zircon's utest/crypto, Garnet's boringssl_tests, manual curling

Change-Id: If9e03ac87633499fc4a4e3427e495806c55f57bb

ZX-2902

Tests: Zircon's utest/crypto, Garnet's boringssl_tests, manual curling

Change-Id: Iafd967d278b8443a6b24fe1776e78df1e1806410

This CL removes the checks for customized files.  It's the other half
of https://fuchsia-review.googlesource.com/c/zircon/+/205023.

Change-Id: I41bd88a115fb52b4e35ca3ca01bff1bcad2cb03c
Tests: Rolled boringssl

Test: built SDK archive.
Bug: DX-416
Change-Id: I445122b494997ba580c0ea9aa1a307a30cc8c0d1

Change-Id: I493a043521a14ca4d73d47258a85930d0561548e

- Add "PKCS5_PBKDF2_" to the list of prefixes added by bindgen

SEC-100

Test: Tested //garnet/public/rust/crates/mundane-crypto
Change-Id: Ia93218ec74817d58bf822ffafd77b563bd6874c2

Change-Id: Ib71bbc0607ef2376841e0c5696286a9cd2b650ca

SEC-98

Change-Id: Iad5a189afd02bed0baa88c068dbab27af487a276

- Add "RAND_" to the list of prefixes added by bindgen

SEC-97

Test: Tested //garnet/public/rust/crates/mundane-crypto
Change-Id: I58f68d100590e4a76c7e7ea602ca96ab30265fc2

- LICENSE.MPLv2 file was used for Mozilla root certificates, which
  are no longer stored in this repo

Change-Id: I0d6dd229b62de5a0928f86efe8330b23431375c8

Change-Id: I9e464efd4e74cf212bce179f7fe7e1fca392f1db

- Add "HMAC_" to the list of prefixes added by bindgen

SEC-93

Test: Tested //garnet/public/rust/crates/mundane-crypto
Change-Id: I5748088c692ce3fefd71a2fd6ffc8fef307f82a6

SEC-88

Test: Manually tested:
- new roll_boringssl.go
- compiled/tested rust/boringssl-sys
- compiled //garnet/public/rust/crates/mundane-crypto, which
  depends on these bindings

Change-Id: I2804a88d19e7755ff43e17ca75e4180e73417158

Previously, we were linking boringssl dynamically against libc++.so.
Because we include boringssl in the SDK, we want to not link against
libc++.so.

In order for the C++ language to work, we need to link against some
library that provides a few basic symbols. This CL obtains those symbols
by statically linking against zxcpp, which is how we normally get those
symbols without libc++.

Test: SDK compiles
Change-Id: I43e4220a62ea1baae1a172f21b781a496842db44

Change-Id: I7c152391fbf411b18aeefadfa414f1c25e0b740b
Tested: affected tests ran successfully out of pkgfs
Bug: PKG-46

Change-Id: I1c5a19fb9e8588bfb2f9a8b5cd152c47bbd3cbd7

Change-Id: I9949af29befa9d22ef3e402c17e9732ba1def443

Change-Id: Idb682397009edd2e9c2ee3f9495f884ab1a303ab

DX-89

Change-Id: I914a2fa1374c390305c366e3b7570339015a800a

gtest is an old version that predates the googletest and googlemock
merger, all tests should be using the newer googletest that's being
kept in sync with the upstream version.

Change-Id: If98c73b258d8d118bd226045af583f8125ed1950

Change-Id: Ic214d63f65fb3812a70469611971db7b5256f5bf