Explicitly mention SHA-1 as a possible cause in the weak cert signature interstitial.

Explicitly mention SHA-1 as a possible cause in the weak cert signature interstitial.

In the near future (starting in Chrome 56), this error will most often be triggered by the deprecation of SHA-1 signed certs. Explicitly mentioning SHA-1 in the advanced details gives a strong hint about the likely cause to anyone who does not know the ins and outs of the SHA-1 deprecation, but has heard about it.

BUG=653691
Committed: https://crrev.com/f3f60a5708505a97dd7761b60f39eac3f78a54dd
Cr-Commit-Position: refs/heads/master@{#433388}

[lgarron, 2016-11-17 07:52:56]

Patchset #1 (id:1) has been deleted

[lgarron, 2016-11-17 07:53:23]

Description was changed from

==========
Explicitly mention SHA-1 as a possible cause in the weak cert signature
interstitial.

BUG=
==========

to

==========
Explicitly mention SHA-1 as a possible cause in the weak cert signature
interstitial.

In the near future (starting in Chrome 56), this error will most often be
triggered by the deprecation of SHA-1 signed certs. Explicitly mentioning SHA-1
in the advanced details gives a strong hint about the likely cause to anyone who
does not know the ins and outs of the SHA-1 deprecation.

BUG=653691
==========

[lgarron, 2016-11-17 07:54:35]

lgarron@chromium.org changed reviewers:
+ meacer@chromium.org

[lgarron, 2016-11-17 07:54:36]

meacer@, could you review?

[lgarron, 2016-11-17 07:55:33]

Description was changed from

==========
Explicitly mention SHA-1 as a possible cause in the weak cert signature
interstitial.

In the near future (starting in Chrome 56), this error will most often be
triggered by the deprecation of SHA-1 signed certs. Explicitly mentioning SHA-1
in the advanced details gives a strong hint about the likely cause to anyone who
does not know the ins and outs of the SHA-1 deprecation.

BUG=653691
==========

to

==========
Explicitly mention SHA-1 as a possible cause in the weak cert signature
interstitial.

In the near future (starting in Chrome 56), this error will most often be
triggered by the deprecation of SHA-1 signed certs. Explicitly mentioning SHA-1
in the advanced details gives a strong hint about the likely cause to anyone who
does not know the ins and outs of the SHA-1 deprecation, but has heard about it.

BUG=653691
==========

[meacer, 2016-11-17 20:06:56]

Lgtm, as long as the string is approved by UI.

[lgarron, 2016-11-19 02:37:21]

The CQ bit was checked by lgarron@chromium.org

[commit-bot: I haz the power, 2016-11-19 02:37:55]

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, 2016-11-19 03:25:31]

Committed patchset #1 (id:20001)

[commit-bot: I haz the power, 2016-11-19 03:28:01]

Description was changed from

==========
Explicitly mention SHA-1 as a possible cause in the weak cert signature
interstitial.

In the near future (starting in Chrome 56), this error will most often be
triggered by the deprecation of SHA-1 signed certs. Explicitly mentioning SHA-1
in the advanced details gives a strong hint about the likely cause to anyone who
does not know the ins and outs of the SHA-1 deprecation, but has heard about it.

BUG=653691
==========

to

==========
Explicitly mention SHA-1 as a possible cause in the weak cert signature
interstitial.

In the near future (starting in Chrome 56), this error will most often be
triggered by the deprecation of SHA-1 signed certs. Explicitly mentioning SHA-1
in the advanced details gives a strong hint about the likely cause to anyone who
does not know the ins and outs of the SHA-1 deprecation, but has heard about it.

BUG=653691

Committed: https://crrev.com/f3f60a5708505a97dd7761b60f39eac3f78a54dd
Cr-Commit-Position: refs/heads/master@{#433388}
==========

[commit-bot: I haz the power, 2016-11-19 03:28:01]

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