PlexSheep

@PlexSheep@infosec.pub

• ⁨Comment⁩ on ⁨These Linksys routers are likely transmitting cleartext passwords⁩ ⁨⁨5⁩ ⁨months⁩ ago⁩:

  You of course have some valid points, but I think they don’t just apply to OSS, but software in general. Software is often unmaintained, has bugs, and nobody really cares for it, that is true for both OSS and closed source.

  Being OSS is always a boon in my opinion, as it enables people to take a look at it if they want to. There is no audit-duty, people can (within the license) do whatever they want, and that is a very good thing.

  I didn’t really audit OSS, but that’s not the only boon OSS offers. For example, I wrote a rust tool that did something similar to tee so I just went and pulled up the source code of GNU tee. No problem (besides that C code feels so messy)

  Or another example: I develop a lot of rust. In rust, there are a lot of dependencies that offer very nice functionalities. I was developing a library to help make developing cli tools easier, and wanted to make a module for easily creating a repl (think bash but very dumb). There was a repl project that did some things I wanted, so it was no problem to just go and look at their source to see howbI voukd do my things.

  As a result, I stay convinced that OSS is more trustworthy and more approachable for users and developers (Note that this effect is offset by gazillions of corporate money for closed source).

• ⁨Comment⁩ on ⁨These Linksys routers are likely transmitting cleartext passwords⁩ ⁨⁨5⁩ ⁨months⁩ ago⁩:

  That’s not correct.

  1. Even if you don’t read the whole thing now, you might want to check something out later, even if it’s just a small thing.
  2. Being open source is a matter of transparency. If it’s not OSS, it has something to hide. Often that’s not too bad, but being OSS builds trust.
  3. Even if you’re going to use it without thinking at all, someone else can look at the code and do something about it if it’s bad code.

  There is more, but it’s late