The Rust code isn't closed source, but I'd strongly prefer a coreutils replacement to use GPL over MIT as well.
ParetoOptimalDev
joined 2 years ago
Already fixed, in software that's existed for years and is used by millions. But Oh no, memory issues, let's rewrite that in ! will surely result in a better outcome.
Rsync is great software, but the C language fates it to keep having memory issues in spite of its skilled developers.
Preventing a bug from being possible > fixing a bug.
I fear moving away from GPL that moving to Rust seems to bring, but Rust does fix real memory issues.
Take the recent rsync vulnerabilities for example.
At least this one in a Rust implementation of rsync would have very likely been avoided:
CVE-2024-12085 – A flaw was found in the rsync daemon which could be triggered when rsync compares file checksums. This flaw allows an attacker to manipulate the checksum length (s2length) to cause a comparison between a checksum and uninitialized memory and leak one byte of uninitialized stack data at a time. Info Leak via uninitialized Stack contents defeats ASLR.
I would love this news if it didn't move away from the GPL.
Mass move to MIT is just empowering enshittification by greedy companies.
Sadly I found out yesterday:
Matrix is not a community-based software, it was born [00] in Amdocs [01], a multinational corporation founded in Israel.
https://hackea.org/notas/matrix.html
Many were claiming its impossible to get contributions merged as well.
I would be happy to find out this information is wrong or outdated.
Why not avoid amazon completely or as much as possible?
Mints outdated drivers can definitely cause issues for beginners.