this post was submitted on 07 Jan 2025
624 points (96.8% liked)

linuxmemes

24389 readers
1109 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 users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • 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.
    • 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, no politics, no trolling or ragebaiting.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    •  

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    624
    Kinda sus... (lemmy.world)
    submitted 3 months ago by gigadadz@lemmy.world to c/linuxmemes@lemmy.world
    74 comments fedilink hide all child comments
     

    The NSA, the original primary developer of SELinux, released the first version to the open source development community under the GNU GPL on December 22, 2000.[6] The software was merged into the mainline Linux kernel 2.6.0-test3, released on 8 August 2003. Other significant contributors include Red Hat, Network Associates, Secure Computing Corporation, Tresys Technology, and Trusted Computer Solutions.

    https://en.wikipedia.org/wiki/Security-Enhanced_Linux

    you are viewing a single comment's thread
    view the rest of the comments
    [–] TootSweet@lemmy.world 28 points 3 months ago (4 children)

    So it would be pretty hard for them to hide a backdoor or something??

    It happens, though.

    [–] SnotFlickerman@lemmy.blahaj.zone 26 points 3 months ago (1 children)

    This is also probably the reason why you lost your DARPA funding, they more than likely caught wind of the fact that those backdoors were present and didn't want to create any derivative products based upon the same.

    Though this implies that the Department of Defense doesn't want to use compromised tools, since DARPA is DoD. NSA is also DoD.

    [–] peoplebeproblems@midwest.social 8 points 3 months ago

    They wouldn't want to use or derive any compromised software themselves. They would want any adversaries to have it implemented.

    [–] Badabinski@kbin.earth 9 points 3 months ago

    I did some follow-up research and found that subsequent audits found no backdoors. They're either incredibly sneaky, or the person making these claims wasn't being entirely honest.

    [–] emeralddawn45@discuss.tchncs.de 8 points 3 months ago (1 children)

    Do you know of any good comprehensive followup to this? A quick search shows me lots of outdated info and inconclusive articles. Do you know if they conclusively found anything or if there is a good writeup on the whole situation?

    [–] MajorHavoc@programming.dev 5 points 3 months ago* (last edited 3 months ago)

    I don't have such a source, but the Cybersecurity community throw accusations around easily, and are loathe to ever bless any software as completely innocent - which is a good thing.

    When the accusations stop, the issue has either been addressed (typical outcome), or the product owner was written off by the Cybersecurity community as a lost cause (rare, but it happens).

    [–] where_am_i 8 points 3 months ago (1 children)

    People don't understand that the way a backdoor is usually implemented is not going to be obviously saying "backdoor_here", neither it will look like a some magic code loading a large string and unzipping it on the fly -- that's sus af. What you will see is some "play video" functionality that has a very subtle buffer overflow bug that's also not trivially triggerable.

    This already happened with WhatsApp.

    [–] possiblylinux127@lemmy.zip 3 points 3 months ago

    Honestly I think a lot of backdoors are just unintentionally exploits that are not disclosed