this post was submitted on 30 Mar 2024
1567 points (97.7% liked)

linuxmemes

21263 readers
504 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    1567
    Backdoors (lemmy.ml)
    submitted 7 months ago by lemmyreader@lemmy.ml to c/linuxmemes@lemmy.world
    116 comments fedilink hide all child comments
     

    https://wetdry.world/@cyrus/112186279067271067

    you are viewing a single comment's thread
    view the rest of the comments
    [โ€“] CosmicCleric@lemmy.world 1 points 7 months ago (1 children)

    Forgot to ask, but I would love to hear your thoughts on what @5C5C5C@programming.dev has commented about this subject: https://lemmy.world/comment/9003210

    [โ€“] GamingChairModel@lemmy.world 3 points 7 months ago

    In the broader context of that thread, I'm inclined to agree with you: The circumstances by which this particular vulnerability was discovered shows that it took a decent amount of luck to catch it, and one can easily imagine a set of circumstances where this vulnerability would've slipped by the formal review processes that are applied to updates in these types of packages. And while it would be nice if the billion-dollar-companies that rely on certain packages would provide financial support for the open source projects they use, the question remains on how we should handle it when those corporations don't. Do we front it ourselves, or just live with the knowledge that our security posture isn't optimized for safety, because nobody will pay for that improvement?