Cut down /crypto and switch what is left of it to boringssl.

Cut down /crypto and switch what is left of it to boringssl.

This removes almost all of the /crypto code, leaving around:

 - openssl_util
 - random
 - secure_hash
 - sha2

which are used by Mojo.

This also switches the impl of secure_hash to secure_hash_openssl backed by
openssl (in third_party/boring_ssl), as the default one in secure_hash_default
is backed by NSS in /net/third_party/nss (and /net is going away).

BUG=456130
R=abarth@chromium.org

Committed: https://chromium.googlesource.com/external/mojo/+/1722df1e3c68f256a8008df925b1c6bdde40be60

[ppi, 2015-02-18 16:46:48]

ppi@chromium.org changed reviewers:
+ jamesr@chromium.org

[ppi, 2015-02-18 16:48:26]

Hi James,

to be landed after https://codereview.chromium.org/938573005/ . Ptal.

[ppi, 2015-02-18 17:52:00]

ppi@chromium.org changed reviewers:
+ abarth@chromium.org

[ppi, 2015-02-18 17:54:28]

+Adam

the list of the remaining files that we're using is in the commit description.
I'd be happy to take a look at the secure_hash impl you referred to in the
meeting, could you let me know where can I find it?

[ppi, 2015-02-18 17:56:17]

(openssl_util is left only for secure_hash_openssl sake)

[ppi, 2015-02-23 12:37:26]

Hi Adam, please tal.

[abarth-chromium, 2015-02-23 17:12:49]

If all we're using this for is for the app identifiers, we should just switch to
using sha1.  Here's an implementation of sha1 that should be easy to make stand
alone:

http://trac.webkit.org/browser/trunk/Source/WTF/wtf/SHA1.cpp

[ppi, 2015-02-23 17:35:17]

Thanks, Adam! How do you feel about landing this CL as-it-is, and reviewing such
a change separately, as opposed to making the change here?

[abarth-chromium, 2015-02-23 17:36:37]

LGTM

[ppi, 2015-02-24 09:50:14]

Committed patchset #2 (id:20001) manually as
1722df1e3c68f256a8008df925b1c6bdde40be60 (presubmit successful).