Google Git
Sign in
chromium / chromium / src / 58e90622961327f58056f4ba3b7db6ea307970f1
commit58e90622961327f58056f4ba3b7db6ea307970f1[log] [tgz]
authorwtc@chromium.org <wtc@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>Fri Sep 06 06:40:03 2013
committerwtc@chromium.org <wtc@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>Fri Sep 06 06:40:03 2013
tree95b2d2acd970e96f171fc8b1b6e3ea9f01fba5b9
parente875eb99783735c2ba6a7b453a698e138abbad6e [diff]
Prefer to generate SHA-1 signatures for TLS 1.2 client authentication if
the client private key is a 1024-bit RSA or DSA key.

Older Estonian ID cards with 1024-bit RSA keys cannot sign SHA-256
hashes.

1024-bit DSA keys were formerly specified to be used with SHA-1 only.

R=agl@chromium.org,rsleevi@chromium.org
BUG=278370
TEST=manual testing by someone who has an older Estonian ID card

Review URL: https://chromiumcodereview.appspot.com/23596013

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@221609 0039d316-1c4b-4281-b951-d872f2087c98
4 files changed
tree: 95b2d2acd970e96f171fc8b1b6e3ea9f01fba5b9
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. breakpad/
  6. build/
  7. cc/
  8. chrome/
  9. chrome_frame/
  10. chromeos/
  11. cloud_print/
  12. components/
  13. content/
  14. courgette/
  15. crypto/
  16. dbus/
  17. device/
  18. extensions/
  19. google_apis/
  20. google_update/
  21. gpu/
  22. ios/
  23. ipc/
  24. jingle/
  25. media/
  26. native_client_sdk/
  27. net/
  28. ppapi/
  29. printing/
  30. remoting/
  31. rlz/
  32. sandbox/
  33. sdch/
  34. skia/
  35. sql/
  36. sync/
  37. testing/
  38. third_party/
  39. tools/
  40. ui/
  41. url/
  42. webkit/
  43. win8/
  44. .DEPS.git
  45. .gitignore
  46. .gitmodules
  47. .gn
  48. Android.mk
  49. AUTHORS
  50. codereview.settings
  51. DEPS
  52. LICENSE
  53. LICENSE.chromium_os
  54. OWNERS
  55. PRESUBMIT.py
  56. PRESUBMIT_test.py
  57. WATCHLISTS