- Nov 04, 2019
-
-
Georg Koppen authored
-
boklm authored
-
- Nov 01, 2019
-
-
Georg Koppen authored
Changelog update and versions bump
-
-
- Oct 31, 2019
-
-
Georg Koppen authored
This fixes #21004 and #27307 on our side.
-
- Oct 24, 2019
-
-
When checking our .mar and .exe files for signing errors we keep the checked files around until the whole check is done. This essentially leads to doubling the amount of disk space for them during that time, which could make the difference between someone being able to check them successfully or not. There is actually no need, though, to keep all the binaries until the whole signature check is done and we remove the checked bundle from now on immediately after a particular check finished.
-
- Oct 18, 2019
-
-
Georg Koppen authored
-
Georg Koppen authored
-
- Oct 17, 2019
-
-
Georg Koppen authored
Changelog update and versions bump
-
- Oct 15, 2019
-
-
- Oct 13, 2019
-
-
Georg Koppen authored
-
- Oct 12, 2019
-
-
Georg Koppen authored
-
Georg Koppen authored
-
Georg Koppen authored
Changelog update and versions bump
-
- Oct 11, 2019
-
-
-
Georg Koppen authored
-
-
- Oct 10, 2019
-
-
boklm authored
-
- Oct 09, 2019
-
-
- Oct 08, 2019
-
-
boklm authored
We use /proc/cpuinfo to check for SSE2 support, however on some systems it isn't readable by ordinary users, so we just assume that SSE2 is available in this case.
-
-
Georg Koppen authored
-
- Oct 07, 2019
-
-
If you don't take this approach with unicode curly quotes, shellcheck thinks that maybe you meant to use "" instead.
-
Fixes bug 24755.
-
-
- Oct 05, 2019
- Oct 04, 2019
-
-
Georg Koppen authored
Thanks cypherpunk.
-
- Oct 03, 2019
-
-
Alex Catarineu authored
-
- Oct 02, 2019
-
-
boklm authored
-
- Oct 01, 2019
-
-
Georg Koppen authored
-
Georg Koppen authored
-
- Sep 27, 2019
-
-
Georg Koppen authored
Changelog update and versions bump
-
Georg Koppen authored
-
boklm authored
-
- Sep 26, 2019
-
-
Georg Koppen authored
-
boklm authored
With the linux-generic64 target the build is broken if we don't add the no-asm option: https://github.com/openssl/openssl/issues/9839 We fix that by switching to the linux-x86_64 target. At the same time we also switch the linux-generic32 target to linux-x86.
-
boklm authored
The default OPENSSLDIR on Windows builds contain spaces and parenthesis, which break the build as the unquoted path is used in several places. We fix this by escaping the spaces and parenthesis. This is fixing part of the issues mentioned in: https://github.com/openssl/openssl/issues/9520
-
boklm authored
This is fixing CVE-2019-1552: http://cve.circl.lu/cve/CVE-2019-1552 In oder to avoid changing the OPENSSLDIR to a directory that might be writable on the user system, we don't set the --prefix/--openssldir option anymore and use DESTDIR to select the packaging installation directory.
-