Upgrade openssl to release 1.0.1c.

Upgrade openssl to release 1.0.1c.

This is the DEPS roll corresponding to the following patch:
https://chromiumcodereview.appspot.com/10911247/

This has been tested by:

- Rebuilding chromium and flip_in_mem_edsm_server for Linux/x64,
  the latter links openssl statically.

- Rebuilding everything for Android/ARM, which uses OpenSSL to implement
  SSL/TLS and some aspects of certificate verification.

- Back-porting this change to internal Chrome on Android tree, and
  verifying that net_unittests still pass after it. Also launched
  the browser and check that it can still visit a few HTTPS web
  pages.

BUG=137071
NOTRY=true

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=166429

[digit1, 2012-11-05 13:44:53]

For the record, I also wanted to test the experimental Linux + openssl build for
Ryan, but it is currently broken due to NaCL code that calls NSS initialization
function directly. I'll try to provide a patch to fix this later.

[Ryan Sleevi, 2012-11-05 13:55:33]

Lgtm
On Nov 5, 2012 8:44 AM, <digit@chromium.org> wrote:

> Reviewers: Ryan Sleevi, agl, joth, bulach, pliard, darin,
>
> Message:
> For the record, I also wanted to test the experimental Linux + openssl
> build for
> Ryan, but it is currently broken due to NaCL code that calls NSS
> initialization
> function directly. I'll try to provide a patch to fix this later.
>
> Description:
> Upgrade openssl to release 1.0.1c.
>
> This is the DEPS roll corresponding to the following patch:
>
https://chromiumcodereview.**appspot.com/10911247/<https://chromiumcodereview...
>
> This has been tested by:
>
> - Rebuilding chromium and flip_in_mem_edsm_server for Linux/x64,
>   the latter links openssl statically.
>
> - Rebuilding everything for Android/ARM, which uses OpenSSL to implement
>   SSL/TLS and some aspects of certificate verification.
>
> - Back-porting this change to internal Chrome on Android tree, and
>   verifying that net_unittests still pass after it. Also launched
>   the browser and check that it can still visit a few HTTPS web
>   pages.
>
> BUG=137071
>
>
> Please review this at
https://chromiumcodereview.**appspot.com/11363080/<https://chromiumcodereview...
>
> SVN Base:
http://git.chromium.org/**chromium/src.git@master<http://git.chromium.org/chr...
>
> Affected files:
>   M DEPS
>
>
> Index: DEPS
> diff --git a/DEPS b/DEPS
> index c87224e79f2b4e3adda4ab064a58d8**2abc305edc..**
> df6919e76dc2831c188d4f7507bd2e**921e3f7bc5 100644
> --- a/DEPS
> +++ b/DEPS
> @@ -517,7 +517,7 @@ deps_os = {
>         Var("lss_revision")),
>
>      "src/third_party/openssl":
> -      "/trunk/deps/third_party/**openssl@157142",
> +      "/trunk/deps/third_party/**openssl@164645",
>
>      "src/third_party/WebKit/Tools/**gdb":
>        Var("webkit_trunk") + "/Tools/gdb@" + Var("webkit_revision"),
>
>
>

[digit1, 2012-11-07 08:59:33]

I've checked with other Clank engineers that the android_dbg_triggered_test
failure, while related to the TLS implementation, doesn't come from this patch
itself.

The test should probably be disabled for Android at that point, in all cases,
trying to commit this patch now.

[commit-bot: I haz the power, 2012-11-07 08:59:59]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/digit@chromium.org/11363080/1

[commit-bot: I haz the power, 2012-11-07 10:28:48]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/digit@chromium.org/11363080/13001

[digit1, 2012-11-07 10:34:17]

Setting NOTRY=true manually. Unfortunately, there is a pending patch to disable
the bad Android test that can't make it for now.

[commit-bot: I haz the power, 2012-11-07 13:45:22]

The commit queue went berserk retrying too often for a
seemingly flaky test. Builder is android_dbg, revision is HEAD

[commit-bot: I haz the power, 2012-11-07 14:46:34]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/digit@chromium.org/11363080/13001

[commit-bot: I haz the power, 2012-11-07 15:17:00]

Change committed as 166429