should i be worried installing these two? what does it mean though?

(these are captured from Pop! OS software manager)

  • Mactan@lemmy.ml
    link
    fedilink
    arrow-up
    9
    ·
    4 months ago

    a curse upon these distros for alarming people with such messages. they are meaningless and technically apply to every flatpak

    • Possibly linux@lemmy.zip
      link
      fedilink
      English
      arrow-up
      10
      ·
      4 months ago

      They mean that the app has that permission. It is good that they let the user know the apps capabilities

      • The_Terrible_Humbaba@slrpnk.net
        link
        fedilink
        arrow-up
        4
        ·
        4 months ago

        Not for the average/casual user, which is why this post exists.

        The average person will look at that and see the ‘!’ in a triangle and became scared of what it can do to their system, even though it has no more permissions than a system package. Alternatively, they will become desensitized and learn to ignore it, resulting in installing flatpacks from untrusted and unverified sources.

        Overall, I just think the idea around having to sandbox all flatpaks is not a good idea. To give a concrete example, Librewolf is marked as “potentially unsafe” because it has access to the download folder, but if I want to use it to open a file that isn’t in “downloads” I have to use flatseal to give it extra permissions - it’s the worst of both worlds! Trying so hard to comply with flatpak guidelines that it gets in the way of doing things, and still not being considered safe enough.

      • unwarlikeExtortion@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        4 months ago

        I don’t know why a journaling app needs full system access and access to system settings, and the permission Flatseal requests is a dangerous one if you pay attention to these things. Looks like they’re doing their job to me.

        Xournal seems pretty trustworthy to me, so I assume it’s for code simplicity (or age) or not being made with Flatpak in mind - just ‘open any file/full filesystem access’’ (for basic functions like opening files) and ‘change system settings’ for probably only a few features that change system settings.

        I agree the permissions are dangerous and I commend Flatpak for incentivizing developers to use granular permissions.

        As others (and you yourself have said), Flatseal’s entire purpose is to edit Flatpak lermissions, so that one shouldn’t be alarming.