Not to mention tons of other projects that live outside of the main org, contributions to other projects all over the place, etc.
So much hate for free software.
The “I hate Nvidia because all I know is their driver is proprietary” schtick is old.
They crossed the $1T mark in value solely because of the almost completely open source ecosystem (a large portion of which they directly develop and contribute to) that runs on top of their hardware and (yes, proprietary) driver.
They’re not angels but this position is something out of Slashdot circa 2005.
CUDA. Non-free firmware. Still bad. And Radeon the same, propietary firmware run by the kernel is needed sometimes to even boot the GPU, it just happens Linux-Libre patches it and the Modesetting driver will work fine until you call 3D accelerated calls, when that happens the system may either panic or crash X entirely. That can be fixed by setting RenderAccel to none in the X.org config file.
I'm not acting - I'm genuinely saying, NVIDIA hates Free Software and this isn't a controversial stance. Always have. This is common knowledge and doesn't need sources, citations, etc.
They weakened it recently in Linux again. For over a decade there was a badly bugged PRNG in the Linux kernel, it was discovered and replaced with a more costly one which worked great. Then, only a short time ago, they replaced that with one of... shady provenance. You're better off writing your own PRNG on that platform IMHO.
Jason Donenfeld (author of Wireguard) replaced Linux’s SHA-1 based PRNG (remember, SHA-1 is cryptographically broken) with BLAKE2. What is shady about it?
You can’t get cryptographically secure random numbers without platform support, so it’s really bad to tell people to avoid the kernel CSPRNG.
What are you talking about? Jason Donenfeld is the author of WireGuard, the extraordinarily popular VPN protocol that cannot use NIST cryptography (it does no negotiation, and is built on a version of Noise that uses ChaPoly and 25519). The change that was just described to you was a shift from NIST cryptography to non-NIST cryptography.
Yes: they use, for lack of a better term, DJB cryptography, and like many modern cryptosystems they eschew negotiation, so it's not straightforward to fit NIST algorithms in.
it's entirely straight-forward to substitute AES-256-GCM for ChaCha20/Poly1305 in Wireguard, and the result, while not "wireguard" is substantially faster than Wireguard.
