Not discrediting Open Source Software, but nothing is 100% safe.

225 points

Luckily there are people who do know, and we verify things for our own security and for the community as part of keeping Open Source projects healthy.

permalink
report
reply
103 points

Open source software is safe because somebody knows how to audit it.

permalink
report
parent
reply
45 points
*

And to a large extent, there is automatic software that can audit things like dependencies. This software is also largely open source because hey, nobody’s perfect. But this only works when your source is available.

permalink
report
parent
reply
6 points

Except when people pull off shit like Heartbleed.

permalink
report
parent
reply
20 points

It’s safe because there’s always a loud nerd who will make sure everyone knows if it sucks. They will make it their life mission

permalink
report
parent
reply
5 points

Will that nerd be heard or be buried under the scrutiny?

permalink
report
parent
reply
19 points

Also because those people who can audit it don’t have a financial incentive to hide any flaws they find

permalink
report
parent
reply
12 points

My very obvious rebuttal: Shellshock was introduced into bash in 1989, and found in 2014. It was incredibly trivial to exploit and if you had shell, you had root perms, which is insane.

env x=‘() { :;}; echo vulnerable’ bash -c “echo this is a test”

permalink
report
parent
reply
12 points

Though one of the major issues is that people get comfortable with that idea and assume for every open source project there is some other good Samaritan auditing it

permalink
report
parent
reply

I would argue that even in that scenario it’s still better to have the source available than have it closed.

If nobody has bothered to audit it then the number of people affected by any flaws will likely be minimal anyway. And you can be proactive and audit it yourself or hire someone to before using it in anything critical.

If nobody can audit it that’s a whole different situation though. You pretty much have to assume it is compromised in that case because you have no way of knowing.

permalink
report
parent
reply
4 points

Oh definitely, I fully agree. It’s just a lot of people need to stop approaching open source with an immediate inherent level of trust that they wouldn’t normally give to closed source. It’s only really safer once you know it’s been audited.

permalink
report
parent
reply
5 points

Have you seen the dependency trees of projects in npm? I really doubt most packages are audited on a regular basis.

permalink
report
parent
reply
114 points

The point is not that you can audit it yourself, it’s that SOMEBODY can audit it and then tell everybody about it. Only a single person needs to find an exploit and tell the community about it for that exploit to get closed.

permalink
report
reply
19 points

Exactly! I wait on someone who isn’t an idiot like me to say, “ok, so here’s what’s up guys.”

permalink
report
parent
reply
92 points
*
Deleted by creator
permalink
report
reply
6 points

While I generally agree, the project needs to be big enough that somebody looks through the code. I would argue Microsoft word is safer than some l small abandoned open source software from some Russian developer

permalink
report
parent
reply
12 points
*
Deleted by creator
permalink
report
parent
reply
2 points

That’s true, but I’m not a programmer and on a GitHub project with 3 stars I can’t count on someone else doing it. (Of course this argument doesnt apply to big projects like libre office) With Microsoft I can at least trust that they will be in trouble or at least get bad press when doing something malicious.

permalink
report
parent
reply
7 points
*

Ehmm. if nobody uses it, it kinda doen’t matter if it’s safe. And for this example: I bet more people had a look at the code of LibreOffice than MS Office. And i dont think it sends telemetry home in default settings.

permalink
report
parent
reply
2 points

I think they’re talking about onlyoffice.

permalink
report
parent
reply
61 points

But eventually somebody will look and if they find something, they can just fork the code and remove anything malicious. Anyways, open source to me is not about security, but about the public “owning” the code. If code is public all can benefit from it and we don’t have to redo every single crappy little program until the end of time but can instead just use what is out there.
Especially if we are talking about software payed for by taxes. That stuff has to be out in the open (with exception for some high security stuff - I don’t expect them to open source the software used in a damn tank, a rocket or a fighter jet)

permalink
report
reply
21 points

Fun fact*: the software in the most advanced dildos come from old missile guidance systems the government isn’t using anymore.

*not a fact, but hopefully fun.

permalink
report
parent
reply
17 points

Maybe not a fact but I will still accept it as canon

permalink
report
parent
reply
11 points

No, missle.

permalink
report
parent
reply
2 points

Agreed.

permalink
report
parent
reply
8 points

this was indeed fun

permalink
report
parent
reply
2 points

Thanks 😁

permalink
report
parent
reply
55 points

You can get a good look at a T-bone by sticking your head up a cow’s ass but I’d rather take the butcher’s word for it.

There are people that do audit open source shit quite often. That is openly documented. I’ll take their fully documented word for it. Proprietary shit does not have that benefit.

permalink
report
reply
17 points

And even when problems are found, like the heartbleed bug in OpenSSL, they’re way more likely to just be fixed and update rather than, oh I dunno, ignored and compromise everybody’s security because fixing it would cost more and nobody knows about it anyway. Bodo Moller and Adam Langley fixed the heartbleed bug for free.

permalink
report
parent
reply
1 point

Wasn’t heartbleed in the wild for 2 years though?

permalink
report
parent
reply
1 point

Yeah, but that just happens sometimes. With proprietary software you don’t even have the benefit of being able to audit it to see if the programmers missed something critical, you kinda just have to trust that they’re smarter than a would-be hacker.

permalink
report
parent
reply
1 point

Thanks Callahan!

permalink
report
parent
reply

Memes

!memes@lemmy.ml

Create post

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

Community stats

  • 11K

    Monthly active users

  • 13K

    Posts

  • 287K

    Comments