3 ms·

For me, it's the fact that I'm running code written by some random people. The code could be malicious. I don't know unless I audit it myself and I have no time

by mna_ 11mo ago

For me, it's the fact that I'm running code written by some random people. The code could be malicious. I don't know unless I audit it myself and I have no time for that. Remember the XZ Utils backdoor thing from a few months ago? Well how many backdoors are there in other FOSS stuff?

mbork_pl 11mo ago
How is that specific to FOSS?
- a96 11mo ago
  It's one of the main features, just incoherently rambled and backwards. https://en.wikipedia.org/wiki/The_Free_Software_Definition#The_Four_Essential_Freedoms https://en.wikipedia.org/wiki/The_Free_Software_Definition#T... > The freedom to study how the program works, and change it to make it do what you wish (freedom 1). Access to the source code is a precondition for this. Free software can be audited for backdoors. Closed can not. Their backdoors will stay there indefinitely.
  - fragmede 11mo ago
    disassembler and decompilers exist.
    - goodpoint 11mo ago
      This statement is ridiculous.
      - fragmede 11mo ago
        A music CD installing a stealthed persistent kernel-level rootkit on your Windows PC would also be ridiculous, yet that's exactly what Sony BMG's rootkit in 2005 did. And guess how it was found?
  - int_19h 11mo ago
    Access to source code does not translate to "written by some random people". Many F/OSS projects have a tight circle of contributors, sometimes even outright closed as for e.g. SQLite. That aside, OP was complaining about software written by "random people". Thing is, people working in companies that write proprietary software are equally "random" in that sense. We know that some of them are North Korean agents, for example.