this post was submitted on 07 Jul 2023
31 points (94.3% liked)

Memes

44148 readers
2236 users here now

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.

founded 5 years ago
MODERATORS
31
It's Open Source! (lemmy.dbzer0.com)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

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

all 15 comments
sorted by: hot top controversial new old
[–] [email protected] 3 points 1 year ago

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.

[–] [email protected] 3 points 1 year ago

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.

[–] [email protected] 1 points 1 year ago

"given enough eyeballs, all bugs are shallow" ...but sometimes there is a profound lack of eyeballs.

[–] [email protected] 1 points 1 year ago

Did you fabricate that CPU? Did you write that compiler? You gotta trust someone at some point. You can either trust someone because you give them money and it's theoretically not in their interest to screw you (lol) or because they make an effort to be transparent and others (maybe you, maybe not) can verify their claims about what the software is.

[–] [email protected] 1 points 1 year ago

No, but someone knows how and does. If there's something bad, there'll be a big stink.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

IDK why, but this had me imagining someone adding malicious code to a project, but then also being highly proactive with commenting his additions for future developers.

"Here we steal the user's identity and sell it on the black market for a tidy sum. Using these arguments..."

[–] [email protected] 0 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago

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.

[–] [email protected] 0 points 1 year ago (1 children)

Also, recompile the source code yourself if you think the author is pulling a fast one on you.

[–] [email protected] 1 points 11 months ago

is there not a way to check if thw sourvw and releasw arent the same? would be cool if github / gitlab / etc.. produced a version automatically or there was some instant way to check

[–] [email protected] 0 points 1 year ago (1 children)

Completely missing the point. Collective action is what makes open source software accessible to everybody.

You dont NEED to be able to audit yourself. Still safer than proprietary software every way you look at it.

[–] [email protected] 1 points 1 year ago

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