mirror of
https://github.com/reactos/reactos.git
synced 2024-11-18 13:01:40 +00:00
26a3f98df7
Today 2022-10-25 was the day, when I spotted the first URL in rapps that is not longer happy with just having ECDSA_P256 but now needs even ECDSA_P384 to make the rapps download succeed. *eye-rolling* It was https://bitbucket.org/Swyter/tld-downloads/downloads/diabloiidemo.exe that failed the rapps download with fixme:(dll/win32/bcrypt/bcrypt_main.c:359) algorithm L"ECDSA_P384" not supported err:(win32ss/user/user32/windows/messagebox.c:1048) MessageBox: L"Paket konnte nicht geladen werden! Pr\00fcfen Sie Ihre Internetverbindung!" So I have no choice but to follow the totally stupid crypto-rat-race and add the missing structs and handlers in BCryptOpenAlgorithmProvider(). When will the world ever learn that the new cryptos do outdate faster than the new shit even can be implemented in time everywhere? Each additional crypto algorithm effectively enlarges the attack surface of the end-points instead of making stuff more secure. The world is rushing towards totally breaking backward compatibility to older systems. This is built-in obsolescence. For which gain? This race can never be won. Each crypto-iteration just intensifies the existing chaos. Enough ranting... fix picked from 0.4.15-dev-3662-g |
||
---|---|---|
.. | ||
3rdparty | ||
apisets | ||
appcompat | ||
cpl | ||
directx | ||
keyboard | ||
nls | ||
np | ||
ntdll | ||
opengl | ||
shellext | ||
win32 | ||
CMakeLists.txt |