Imagine your friend that does not know anything about linux, don’t you think this would make them not install the firefox flatpak and potentially think that linux is unsafe?

I ask this because I believe we must be careful and make small changes to welcome new users in the future, we have to make them as much comfortable as possible when experimenting with a new O.S

I believe this warning could have a less alarming design, saying something like “This app can use elevated permissions. What does this mean?” with the “What does this mean?” text as a clickable URL that shows the user that this may cause security risks. I mean, is kind of a contradiction to have “verified” on the app and a red warning saying “Potentially unsafe”, the user will think “well, should I trust this or not??”

  • UserMeNever@feddit.nlEnglish
    0·
    5 months ago

    You could but where is fails is when you open one html file that then needs to loads the other files that are needed by the first.

    You can not allow chain loading like this, it would bypass the sandbox.

    One way of working around this would to allow the option of passing a whole folder and sub folders to the program.

    The other and much harder option would be a per program portal filter that can read the html file. then workout what files that html file needs and offer that list of files to the user.

    The lazy work around is allow read access to $HOME and deny access to some files and folders like .ssh

    • Sethayy@sh.itjust.works
      0·
      5 months ago

      Makes sense, but at least this would generally be out of a normal users usage case (multi-file documents), and so the power user could probably just open flatseal.

      For things like bookmarks it’d work fine, and by extension make the sandbox more secure

      • UserMeNever@feddit.nl
        0·
        5 months ago

        Makes sense, but at least this would generally be out of a normal users usage case (multi-file documents), and so the power user could probably just open flatseal.

        I would not be so sure. Firefox has a “save web page as…” option which saves the html page and all other files needed into a sub folder.

        Without better handling of reading and writing files the sandbox will break that builtin function. another way of working around this. would be to change firefox to save the web page into one file. Maybe something a .html+zip file that firefox would know how to open. However that would lock other browsers out without manualy unziping it first.

        Getting sandboxing right with powerful programs is very hard and I feel the tooling is still not here yet.