4 ms·

The problem is in the unknowns. The "unknowns" in a C implementation means arbitrary code execution and all kinds of nasty. The unknowns in a Rust implementatio

The problem is in the unknowns. The "unknowns" in a C implementation means arbitrary code execution and all kinds of nasty. The unknowns in a Rust implementation means a crash/denial of service. I know which I prefer.

yjftsjthsd-h 10mo ago
> The "unknowns" in a C implementation means arbitrary code execution and all kinds of nasty. In Fil-C?
- lucyjojo 10mo ago
  isnt it x86_64 exclusive?
  - yjftsjthsd-h 10mo ago
    https://github.com/pizlonator/fil-c?tab=readme-ov-file#requirements https://github.com/pizlonator/fil-c?tab=readme-ov-file#requi... says that the current implementation only targets Linux+x86_64 but that they see no reason it couldn't be portable. But you're in the wrong (sub)thread; this (sub)thread is about whether it's safe.
    - lucyjojo 10mo ago
      ah, sorry about that and thanks for the link
stefan_ 10mo ago
There is no "arbitrary code execution and all kinds of nasty" in the Fil-C version and it profits from the decades spent fixing all the logic bugs, races, environment variable mess in coreutils. Meanwhile, the Rust version of course is vulnerable to all of those: https://ubuntu.com/security/notices/USN-7867-1 https://ubuntu.com/security/notices/USN-7867-1