this post was submitted on 30 Mar 2024
985 points (98.5% liked)

linuxmemes

21197 readers
217 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
    985
    Debian security amirite? (lemmy.world)
    submitted 7 months ago by Emerald@lemmy.world to c/linuxmemes@lemmy.world
    75 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] shotgun_crab@lemmy.world 49 points 7 months ago* (last edited 7 months ago) (1 children)

    Still paniking, cause the backdoor was apparently targetting Debian servers, it was discovered just by chance and the "mantainer" made commits for 2 years in the same repo

    [–] possiblylinux127@lemmy.zip 11 points 7 months ago (1 children)

    The fact that this was planned is what makes me nervous. Imagine what else is lurking.

    [–] dan@upvote.au 28 points 7 months ago (1 children)

    and it was only discovered accidentally, when someone was profiling some stuff, noticed SSH using a bit too much CPU power when receiving connections even for invalid usernames/passwords, and spent the time to investigate it more deeply. A lot of developers aren't that attentive, and it could have easily snuck through.

    [–] lemmesay@discuss.tchncs.de 4 points 7 months ago (1 children)

    hey Dan, why don't you post blogs now?

    [–] dan@upvote.au 5 points 7 months ago (2 children)

    I've been meaning to start blogging again. It's just been a lack of free time. Need to think of ideas, too.

    [–] lemmesay@discuss.tchncs.de 2 points 7 months ago

    understandable mate, have a nice day!

    [–] possiblylinux127@lemmy.zip 0 points 7 months ago

    I've never read your blogs but I think it would be good for more people to do write ups on the XZ backdoor. There is a lot that can be learned and improved