• FOSS Is Fun@lemmy.ml
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 year ago

    I’ve tried to combat this a bit with a global Flatpak override that takes unnecessarily broad permissions away by default, like filesystem=home, but apps could easily circumvent it by requesting permissions for specific subdirectories. This cat-and-mouse game could be fixed by allowing a recursive override, such as nofilesystem=home/*.

    But even then, there is still the issue with D-Bus access, which is even more difficult to control …

    I think it is sad that Flatpak finally provides the tool to restrict desktop apps in the same way that mobile apps have been restricted for a decade, but the implementation chooses to be insecure by default and only provides limited options to make it secure by default.

    • TeryVeneno@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      I think the main reason why the implementation is insecure by default is simply because when it started most applications did not use portals and many portals we have today did not exist. You had to poke holes in the sandbox to make anything work cause all applications expected to run unconstrained. In the future as more apps become flatpak aware this should stop being an issue.