summaryrefslogtreecommitdiff
path: root/README.chromium
diff options
context:
space:
mode:
authordavidben@chromium.org <davidben@chromium.org@4ff67af0-8c30-449e-8e8b-ad334ec8d88c>2014-05-01 23:51:14 +0000
committerdavidben@chromium.org <davidben@chromium.org@4ff67af0-8c30-449e-8e8b-ad334ec8d88c>2014-05-01 23:51:14 +0000
commit55b9eb8eb546355b3d55945cf09a45a434cd796f (patch)
tree8bc82dc55d39d01e1aff42e1d2532da19f82f00b /README.chromium
parent152164bc423807c6945662c94d724554a027eeca (diff)
downloadopenssl-55b9eb8eb546355b3d55945cf09a45a434cd796f.tar.gz
Move ECC SSL extensions to the end in OpenSSL.
WebSphere Application Server 7.0 appears to be intolerant of an empty extension at the end. To that end, also ensure we never send an empty padding extension. BUG=363583 Review URL: https://codereview.chromium.org/241613002 git-svn-id: http://src.chromium.org/svn/trunk/deps/third_party/openssl@267674 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
Diffstat (limited to 'README.chromium')
-rw-r--r--README.chromium7
1 files changed, 6 insertions, 1 deletions
diff --git a/README.chromium b/README.chromium
index 30df8b5..443a75d 100644
--- a/README.chromium
+++ b/README.chromium
@@ -206,7 +206,12 @@ located in patches.chromium/. Currently this consists of:
fix_limit_checks.patch
Fix limit checks in writing extensions. BUF_MEM_grow allocates 4/3 the size
requested, so it doesn't overflow the actual allocation.
-
+
+ reorder_extensions.patch
+ Move the ECC extensions to the end of the ClientHello to work around a
+ server bug. Some servers are intolerant to the last extension being empty.
+ See https://crbug.com/363583
+
**************************************************************************
Adding new Chromium patches: