• Bizzle@lemmy.world
    link
    fedilink
    English
    arrow-up
    23
    arrow-down
    1
    ·
    4 months ago

    My understanding is that flatpaks run in a sandbox, so although there is a risk- especially for what you give permissions to- it’s not exactly the same. The AUR is basically “curl | bash”, it’s a miracle this hasn’t happened before. If you’re worried about it I think flatseal can look at the permissions and such, but you’re probably fine.

      • hirihit640@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        6
        ·
        4 months ago

        Just check the permissions of an app before installing. Bazaar has a gauge for how “safe” an app is based on permissions. If it doesn’t request internet, filesystem access, and other powerful permissions, it’ll be marked as the safest.

        Really it’s the same as docker. It’s secure most of the time, but don’t come crying about getting hacked if you give all your containers access to /dev, host networking, etc

      • Billegh@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        4 months ago

        Pretty much. Snap is the only one with a semblance of anything appearing to be security, and nearly every container requires you to turn it off to run.

      • Bizzle@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        4 months ago

        Ha! That sucks. I appreciate that article but now I’m having a little bit of an existential crisis.

    • Bluefruit@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      4 months ago

      While they are sandboxed, there is still potential for them to cause harm. Its in theory a safer system, but nothing is full proof. I’d agree that its likely fine but best to be cautious

      • PieMePlenty@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        4 months ago

        The problem is trust. Sandboxing is all well and good, but what of the data I give the app directly and the resources it has access to?
        If a person installs the Steam client from FlatHub and logs in to it with their account credentials, how will they know the app wasn’t actually published by a third party who modified it to act as a man in the middle to steal account credentials. They’d need to be vigilant and follow a flathub link provided by Valve themselves. The app could also be a crypto miner, capped to use 10% CPU to avoid suspicion… now I’m searching the internet why steam is constantly using 10% of my CPU…

        I don’t actually know if flathub does checks or anything so this isn’t a jab at them specifically. I personally distrust all package distribution platforms by default and don’t use sandboxed packages on any of my installs.

        I guess we all have to define where the lines are and how far we’re prepared to go. Technically, you should read the actual source code fetched from AUR and only build once you’ve confirmed it does what you expect it to… for every thing you install and for every update. Maybe thats good for Richard Stallman, but the general populace will look for trust outside of only trusting themselves.