| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent d94010b commit a64217c
207 files changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -28,12 +28,44 @@ breaking changes, and mappings for the large list of deprecated functions. | |||
| 28 | 28 | ||
| 29 | 29 | [Migration guide]: https://github.com/openssl/openssl/tree/master/doc/man7/migration_guide.pod | |
| 30 | 30 | ||
| 31 | - ### Changes between 3.0.10 and 3.0.10+quic [1 Aug 2023] | ||
| 31 | + ### Changes between 3.0.12 and 3.0.12+quic [24 Oct 2023] | ||
| 32 | 32 | ||
| 33 | 33 | * Add QUIC API support from BoringSSL | |
| 34 | 34 | ||
| 35 | 35 | *Todd Short* | |
| 36 | 36 | ||
| 37 | + ### Changes between 3.0.11 and 3.0.12 [24 Oct 2023] | ||
| 38 | + | ||
| 39 | + * Fix incorrect key and IV resizing issues when calling EVP_EncryptInit_ex2(), | ||
| 40 | + EVP_DecryptInit_ex2() or EVP_CipherInit_ex2() with OSSL_PARAM parameters | ||
| 41 | + that alter the key or IV length ([CVE-2023-5363]). | ||
| 42 | + | ||
| 43 | + *Paul Dale* | ||
| 44 | + | ||
| 45 | + ### Changes between 3.0.10 and 3.0.11 [19 Sep 2023] | ||
| 46 | + | ||
| 47 | + * Fix POLY1305 MAC implementation corrupting XMM registers on Windows. | ||
| 48 | + | ||
| 49 | + The POLY1305 MAC (message authentication code) implementation in OpenSSL | ||
| 50 | + does not save the contents of non-volatile XMM registers on Windows 64 | ||
| 51 | + platform when calculating the MAC of data larger than 64 bytes. Before | ||
| 52 | + returning to the caller all the XMM registers are set to zero rather than | ||
| 53 | + restoring their previous content. The vulnerable code is used only on newer | ||
| 54 | + x86_64 processors supporting the AVX512-IFMA instructions. | ||
| 55 | + | ||
| 56 | + The consequences of this kind of internal application state corruption can | ||
| 57 | + be various - from no consequences, if the calling application does not | ||
| 58 | + depend on the contents of non-volatile XMM registers at all, to the worst | ||
| 59 | + consequences, where the attacker could get complete control of the | ||
| 60 | + application process. However given the contents of the registers are just | ||
| 61 | + zeroized so the attacker cannot put arbitrary values inside, the most likely | ||
| 62 | + consequence, if any, would be an incorrect result of some application | ||
| 63 | + dependent calculations or a crash leading to a denial of service. | ||
| 64 | + | ||
| 65 | + ([CVE-2023-4807]) | ||
| 66 | + | ||
| 67 | + *Bernd Edlinger* | ||
| 68 | + | ||
| 37 | 69 | ### Changes between 3.0.9 and 3.0.10 [1 Aug 2023] | |
| 38 | 70 | ||
| 39 | 71 | * Fix excessive time spent checking DH q parameter value. | |
@@ -19714,6 +19746,8 @@ ndif | |||
| 19714 | 19746 | ||
| 19715 | 19747 | <!-- Links --> | |
| 19716 | 19748 | ||
| 19749 | + [CVE-2023-5363]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-5363 | ||
| 19750 | + [CVE-2023-4807]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-4807 | ||
| 19717 | 19751 | [CVE-2023-3817]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-3817 | |
| 19718 | 19752 | [CVE-2023-3446]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-3446 | |
| 19719 | 19753 | [CVE-2023-2975]: https://www.openssl.org/news/vulnerabilities.html#CVE-2023-2975 | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -9,19 +9,22 @@ sub vc_win64a_info { | |||
| 9 | 9 | $vc_win64a_info = { AS => "nasm", | |
| 10 | 10 | ASFLAGS => "-g", | |
| 11 | 11 | asflags => "-Ox -f win64 -DNEAR", | |
| 12 | - asoutflag => "-o " }; | ||
| 12 | + asoutflag => "-o ", | ||
| 13 | + perlasm_scheme => "nasm" }; | ||
| 13 | 14 | } elsif ($disabled{asm}) { | |
| 14 | 15 | # assembler is still used to compile uplink shim | |
| 15 | 16 | $vc_win64a_info = { AS => "ml64", | |
| 16 | 17 | ASFLAGS => "/nologo /Zi", | |
| 17 | 18 | asflags => "/c /Cp /Cx", | |
| 18 | - asoutflag => "/Fo" }; | ||
| 19 | + asoutflag => "/Fo", | ||
| 20 | + perlasm_scheme => "masm" }; | ||
| 19 | 21 | } else { | |
| 20 | 22 | $die->("NASM not found - make sure it's installed and available on %PATH%\n"); | |
| 21 | 23 | $vc_win64a_info = { AS => "{unknown}", | |
| 22 | 24 | ASFLAGS => "", | |
| 23 | 25 | asflags => "", | |
| 24 | - asoutflag => "" }; | ||
| 26 | + asoutflag => "", | ||
| 27 | + perlasm_scheme => "auto" }; | ||
| 25 | 28 | } | |
| 26 | 29 | } | |
| 27 | 30 | return $vc_win64a_info; | |
@@ -1416,7 +1419,7 @@ my %targets = ( | |||
| 1416 | 1419 | sys_id => "WIN64A", | |
| 1417 | 1420 | uplink_arch => 'x86_64', | |
| 1418 | 1421 | asm_arch => 'x86_64', | |
| 1419 | - perlasm_scheme => "auto", | ||
| 1422 | + perlasm_scheme => sub { vc_win64a_info()->{perlasm_scheme} }, | ||
| 1420 | 1423 | multilib => "-x64", | |
| 1421 | 1424 | }, | |
| 1422 | 1425 | "VC-WIN32" => { | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -233,8 +233,14 @@ In each table entry, the following keys are significant: | |||
| 233 | 233 | is ILP32; | |
| 234 | 234 | RC4_CHAR RC4 key schedule is made | |
| 235 | 235 | up of 'unsigned char's; | |
| 236 | + Note: should not be used | ||
| 237 | + for new configuration | ||
| 238 | + targets | ||
| 236 | 239 | RC4_INT RC4 key schedule is made | |
| 237 | 240 | up of 'unsigned int's; | |
| 241 | + Note: should not be used | ||
| 242 | + for new configuration | ||
| 243 | + targets | ||
| 238 | 244 | ||
| 239 | 245 | [1] as part of the target configuration, one can have a key called | |
| 240 | 246 | `inherit_from` that indicates what other configurations to inherit | |
| Back | FazBrowse Home | New Git URL |
0 commit comments