| OLD | NEW |
| 1 Name: openssl | 1 Name: openssl |
| 2 URL: http://openssl.org/source/ | 2 URL: http://openssl.org/source/ |
| 3 Version: 1.0.1e | 3 Version: 1.0.1e |
| 4 License: BSDish | 4 License: BSDish |
| 5 License File: openssl/NOTICE | 5 License File: openssl/NOTICE |
| 6 License Android Compatible: yes | 6 License Android Compatible: yes |
| 7 Security Critical: yes | 7 Security Critical: yes |
| 8 | 8 |
| 9 Description: | 9 Description: |
| 10 This is OpenSSL, the standard SSL/TLS library, which is used *only* in | 10 This is OpenSSL, the standard SSL/TLS library, which is used *only* in |
| (...skipping 197 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 208 requested, so it doesn't overflow the actual allocation. | 208 requested, so it doesn't overflow the actual allocation. |
| 209 | 209 |
| 210 reorder_extensions.patch | 210 reorder_extensions.patch |
| 211 Move the ECC extensions to the end of the ClientHello to work around a | 211 Move the ECC extensions to the end of the ClientHello to work around a |
| 212 server bug. Some servers are intolerant to the last extension being empty. | 212 server bug. Some servers are intolerant to the last extension being empty. |
| 213 See https://crbug.com/363583 | 213 See https://crbug.com/363583 |
| 214 | 214 |
| 215 export_certificate_types.patch | 215 export_certificate_types.patch |
| 216 Export the certificate_types field in CertificateRequest. | 216 Export the certificate_types field in CertificateRequest. |
| 217 | 217 |
| 218 send_client_verify_cleanup.patch |
| 219 Clean up ssl3_send_client_verify so the various cases (TLS 1.2, pre-TLS-1.2 |
| 220 cases for each cipher suite) are less intertwined. |
| 221 |
| 218 ************************************************************************** | 222 ************************************************************************** |
| 219 Adding new Chromium patches: | 223 Adding new Chromium patches: |
| 220 | 224 |
| 221 In the event you need to add a new Chromium-specific patch, follow this | 225 In the event you need to add a new Chromium-specific patch, follow this |
| 222 procedure: | 226 procedure: |
| 223 | 227 |
| 224 1) Use the --temp-dir option to download everything to a known directory | 228 1) Use the --temp-dir option to download everything to a known directory |
| 225 (by default, import_from_android.sh downloads everything into a | 229 (by default, import_from_android.sh downloads everything into a |
| 226 temporary directory that is erased when the script exits, even in | 230 temporary directory that is erased when the script exits, even in |
| 227 case of error). | 231 case of error). |
| (...skipping 12 matching lines...) Expand all Loading... |
| 240 (cd /tmp/aaa/build && diff -burN android-openssl.orig android-openssl) > pa
tches.chromium/my-new-change.patch | 244 (cd /tmp/aaa/build && diff -burN android-openssl.orig android-openssl) > pa
tches.chromium/my-new-change.patch |
| 241 | 245 |
| 242 5) Re-run the script: | 246 5) Re-run the script: |
| 243 | 247 |
| 244 ./import_from_android.sh | 248 ./import_from_android.sh |
| 245 | 249 |
| 246 Generally speaking, consider sending your patch directly to the Android | 250 Generally speaking, consider sending your patch directly to the Android |
| 247 open-source review servers too. Once submitted there, you can update | 251 open-source review servers too. Once submitted there, you can update |
| 248 the git commit in openssl-chromium.org and remove your local patch in | 252 the git commit in openssl-chromium.org and remove your local patch in |
| 249 one new CL. | 253 one new CL. |
| OLD | NEW |