I have been thinking about self-hosting my personal photos on my linux server. After the recent backdoor was detected I’m more hesitant to do so especially because i’m no security expert and don’t have the time and knowledge to audit my server. All I’ve done so far is disabling password logins and changing the ssh port. I’m wondering if there are more backdoors and if new ones are made I can’t respond in time. Appreciate your thoughts on this for an ordinary user.

  • rotopenguin@infosec.pub
    link
    fedilink
    English
    arrow-up
    66
    arrow-down
    2
    ·
    edit-2
    9 months ago

    How do you know there isn’t a logic bug that spills server secrets through an uninitialized buffer? How do you know there isn’t an enterprise login token signing key that accidentally works for any account in-or-out of that enterprise (hard mode: logging costs more than your org makes all year)? How do you know that your processor doesn’t leak information across security contexts? How do you know that your NAS appliance doesn’t have a master login?

    This was a really, really close one that was averted by two things. A total fucking nerd looked way too hard into a trivial performance problem, and saw something a bit hinky. And, just as importantly, the systemd devs had no idea that anything was going on, but somebody got an itchy feeling about the size of systemd’s dependencies and decided to clean it up. This completely blew up the attacker’s timetable. Jia Tan had to ship too fast, with code that wasn’t quite bulletproof (5.6.0 is what was detected, 5.6.1 would have gotten away with it).

    • rotopenguin@infosec.pub
      link
      fedilink
      English
      arrow-up
      30
      ·
      edit-2
      9 months ago

      In the coming weeks, you will know if this attacker recycled any techniques in other attacks. People have furiously ripped this attack apart, and are on the hunt for anything else like it out there. If Jia has other naughty projects out here and didn’t make them 100% from scratch, everything is going to get burned.

      • rotopenguin@infosec.pub
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        9 months ago

        I think the best assurance is - even spies have to obey certain realities about what they do. Developing this backdoor costs money and manpower (but we don’t care about the money, we can just print more lol). If you’re a spy, you want to know somebody else’s secrets. But what you really want, what makes those secrets really valuable, is if the other guy thinks that their secret is still a secret. You can use this tool too much, and at some point it’s going to “break”. It’s going to get caught in the act, or somebody is going to connect enough dots to realize that their software is acting wrong, or some other spying-operational failure. Unlike any other piece of software, this espionage software wears out. If you keep on using it until it “breaks”, you don’t just lose the ability to steal future secrets. Anybody that you already stole secrets from gets to find out that “their secrets are no longer secret”, too.

        Anyways, I think that the “I know, and you don’t know that I know” aspect of espionage is one of those things that makes spooks, even when they have a God Exploit, be very cautious about where they use it. So, this isn’t the sort of thing that you’re likely to see.

        What you will see is the “commercial” world of cyberattacks, which is just an endless deluge of cryptolockers until the end of time.

  • MangoPenguin@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    54
    ·
    9 months ago

    Self hosting personal photos doesn’t generally require opening anything up to the internet, so most backdoors would not be accessible by anyone but you.

  • Count Regal Inkwell@pawb.social
    link
    fedilink
    arrow-up
    46
    arrow-down
    2
    ·
    9 months ago

    Cheeky answer:

    Actual answer:
    Theoretically anyway, open source software’s guarantee of “no backdoor” is that the code is auditable, and you could study it and know if it has any holes and where. Of course, that presumes that you have the knowledge AND time to actually go and study thousands of lines of code. Unrealistic.
    Slightly less guaranteed but still good enough to calm my mind, is the idea that there is a whole-ass community of people who do know their shit and who are constantly checking this.

    Do note that like. Closed source software is known to be backdoored, only, the backdoors are mostly meant for either the owners of the software (check the fine print folks) or worse, the governments.

    The biggest thing that you should note is that: It is unlikely that you (or I or most of the people here) are interesting enough that anyone will actually exploit those vulnerabilities to personally fuck you over. Your photos aren’t interesting enough except as part of a mass database (which is why Google/Facebook want them). Same for your personal work data and shit.

    Unless those backdoors could be used to turn your machine into a zombie for some money-making scheme (crypto or whatever) OR you’re connected to people in power OR you personally piss off someone who is a hacker – it is very unlikely you’ll get screwed over due to those vulnerabilities :P

    • bigmclargehuge@lemmy.world
      link
      fedilink
      arrow-up
      19
      arrow-down
      1
      ·
      9 months ago

      Just a point to add: this backdoor was (likely) planned years in advance; it took ONE guy a couple weeks (after the malicious code was released) to find it because he had nothing else going on that evening.

      I’m relatively confident that the FOSS community has enough of that type of person that if there are more incidents like this one, there’s a decent chance it’ll be found quickly, especially now that this has happened and gotten so much attention.

      • Tlaloc_Temporal@lemmy.ca
        link
        fedilink
        arrow-up
        2
        ·
        9 months ago

        Even better: there are also backdoors in closed-source software that will never be found. There may be fewer backdoors inserted, but the ones that get in there are far more likely to stay undiscovered.

  • Lmaydev@programming.dev
    link
    fedilink
    arrow-up
    45
    arrow-down
    1
    ·
    9 months ago

    You don’t. Hackers often exploit things like this for ages before they are found. Every bit of non simple software also has bugs.

    But chances are you won’t be the target.

    Just keep everything updated and you should be alright.

  • arisunz@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    36
    ·
    9 months ago

    That’s the neat part, we don’t!

    …but, we at least can have a shot of finding them.

    In the meantime, I’d advise you to keep an eye out and maybe look into threat models. As people said in this thread already, bad actors probably don’t care about your personal photos.

    • dylanmorgan@slrpnk.net
      link
      fedilink
      arrow-up
      13
      arrow-down
      1
      ·
      9 months ago

      Unless OP is a celebrity or politician. Or knows they have an enemy with the resources to find and exploit potential backdoors.

  • shortwavesurfer@monero.town
    link
    fedilink
    English
    arrow-up
    34
    arrow-down
    1
    ·
    9 months ago

    I would say you can’t, but if you are using open source software, then somebody can and will find them eventually and they will be patched. Unlike with closed source software, you will never know if it has a backdoor or not. This whole episode shows both the problems with open source, being lack of funding for security audits, and the beauty of open source, being that eventually it will be detected and removed.

  • thingsiplay@beehaw.org
    link
    fedilink
    arrow-up
    29
    ·
    9 months ago

    We can’t know. If we would know, those weren’t undetected backdoors at all. It’s not possible to know something you don’t know. So the question in itself is a paradox. :D The question is not if there are backdoors, but if the most critical software is infected? At least what I ask myself.

    Do you backups man, do not install too many stuff, do not trust everyone, use multiple mail accounts and passwords and 2 factor authentication. We can only try to minimize the effects of when something horrible happens. Maybe support the projects you like, so that more people can help and have more eyes on it. Governments and corporations with money could do that as well, if they care.

  • fxdave@lemmy.ml
    link
    fedilink
    arrow-up
    29
    arrow-down
    2
    ·
    9 months ago

    Afaik, most phones are backdoored that can be abused using tools like “pegasus” which led to a huge indignation in Hungary. I don’t belive PCs are exceptions. Intel ME is a proprietary software inside the CPU, often considered as a backdoor in Intel. AMD isn’t an exception. It’s even weirder that Intel produces chips with ME disabled for governments only.

    • Richard@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 months ago

      They are not produced for governments only, almost every consumer-grade CPU can have its ME disabled or at least scuttled, thanks to efforts like me_cleaner!

  • delirious_owl@discuss.online
    link
    fedilink
    arrow-up
    24
    arrow-down
    1
    ·
    9 months ago

    Check the source or pay someone to do it.

    If you’re using closed source software, its best to assume it has backdoors and there’s no way to check.

  • Avid Amoeba@lemmy.ca
    link
    fedilink
    arrow-up
    20
    ·
    edit-2
    9 months ago

    We don’t. That’s why we use multiple layers of security. For example keeping all services accessible only via VPN and using a major OS that a lot of production workloads depend on such as Debian, Ubuntu LTS or any of the RHEL copycats. This is a huge plus of the free tier of Ubuntu Pro BTW. It’s commercial level security support for $0. Using any of these OSes means that the time between a vulnerability being discovered, patched and deployed is as short as possible. Of course you have to have automatic security updates turned on, unattended-upgrades in Debian-speak.