this post was submitted on 07 Jul 2023
66 points (90.2% liked)

Memes

45423 readers
1301 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
66
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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 0 points 1 year ago (1 children)

That's exactly the problem with many open source projects.

I recently experienced this first hand when submitting some pull requests to Jerboa and following the devs: As long as there is no money funding the project the devs are trying to support the project in their free time which means little to no time for quality control. Mistakes happen... most of them are uncritical but as long as there's little to no time and expertise to audit code meaningfully and systematically, there will be bugs and these bugs may be critical and security relevant.

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

Even when you do have time. There have been “researchers” submitting malicious prs and when caught just act like it’s no big deal. Even had an entire institution banned from submitting prs to the Linux kernel.

https://www.bleepingcomputer.com/news/security/linux-bans-university-of-minnesota-for-committing-malicious-code/

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

Well, i think in most of those big incidents, people got caught. That means the concept kinda works well?

Regarding the earlier comment: I think companies just started to figure that out. They/You can't just take free libraries databases etc... If you're big tech company you better pay a few developers or an audit to make those libraries safe. This is your way of contributing. Otherwise your big platform will get hacked because you just took some 15 year olds open source code.

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

Selection bias though. We don't know how many have not yet been caught.

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

agree. Hell i wouldnt be shocked if some corporations or even nation-state (ie: NSA) actors do this, in a much better/more professional manner to ensure things like....backdoor access.

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

Yeha that was my though. But more a dedicated program to do similar with large FOSS projects.

They also have hardware/supply chain intercept programs to install back doors in closed source appliances (ie: Cisco firewalls)

So something similar but dedicated to open source PRs.

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

Yeah. I think the discussion is kind of nonsensical and a tautology. Nothing in life is 100% safe, if foss or not. And we don't know what we don't know. We got a few cases where we know something got intercepted after people tried to do malicious PRs or intercepted network equipment.

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

I think the more interesting question has long been: what's (or who is) your threat? Against a sufficiently motivated and resourced adversary, there are few real obstacles. Conversely, some people are just not interesting because there's little or nothing to gain from attacking them.

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

Exactly. I just wanted to point out that most of the people here honestly have no idea what they're talking about.

If people had read the articles about that 'study' if malicious pull requests got accepted... and the aftermath... If they had read the articles how the NSA(?) helped(?!) with the mathematical constants of elliptic curve encryption... How cisco networking equipment got intercepted... If you knew how the internet and freedom worked... You'd know it's not that easy. Every 'simple' answer is just plain wrong. It depends... What is the thread model, what are you able and willing to invest, what are you trying to achieve? Sometimes you don't even know who's friend or foe.

Idk why people want to piss on open source software. It's a fact that one can have a look at open source software and not at closed source. And don't tell me nobody does, because i know i do. And millions of github users contribute code and read some code here and there. And i know a few tech blogs who like to check apps and see if they respect privacy and so on. ... And that's not everything as we pointed out earlier. If this helps you, depends on your own goals and thread model.

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

I really enjoy the discussion here. Refreshing! Most of the time I as a relative non-expert have no idea what I'm doing, but I do read things as much as I can. Otherwise I'm a fallen sysadmin who got a job managing cyber because bills need to be paid.

Open, closed, it's all object code in the end which can be examined in disassembly, or the behaviours observed during runtime. Open makes some processes easier in this area. I think the real strengths in this have been beyond security, to enhance cooperation and reuse so we don't waste time constantly reinventing.