com.brave.Browser VS Flatseal

Currently, the package brave-keyring is responsible for updating the key. However, solutions based on cron and at are not only ugly but also not expected to work in openSUSE Aeon (formerly openSUSE MicroOS Desktop). Someone else has already reported a similar issue with Fedora Silverblue and Fedora CoreOS (https://github.com/brave/brave-release/pull/28). (The preferred alternative for these distros is the Flatpak package, but it doesn't seem that a fully official release will appear quickly https://github.com/flathub/com.brave.Browser/issues/137).

Brave is not in the 22.04 repos, but it has both a flatpak and a snap

If you're not using the flatpak version, does that version have the same problem?

Is that the Flatpak version? I think it's safe. It's from flathub.org (https://flathub.org/apps/details/com.brave.Browser) so it must be curated software.

At times this tool is utilized to grant a flatpak more permissions; to enable a specific use case. For example to enable 'communication' between KeepassXC and Brave/Librewolf for proper browser integration.

netflix should work through your default web browser, if not you may want to try https://flathub.org/apps/details/com.brave.Browser

And not only that, the idea of portals is, IMO, misguided. See this view/bugreport when a flatseal user understands that even though they restricted permissions to access a certain area, the flatpak, itself, can ask to open files there and if OK'd that will be allowed. Their expectation is that with the overrides say "no access" it means "no access even if the flatpak asks very nicely". https://github.com/tchx84/Flatseal/issues/196

Since you installed the programme via Flatpak, you should simply lack the necessary rights (https://docs.flatpak.org/en/latest/sandbox-permissions.html). You can extend the rights quite easily with https://github.com/tchx84/flatseal.

Yes, filed https://github.com/tchx84/Flatseal/issues/196 a while ago, got no joy.

One design feature than can turn into an issue in some scenarios (usually dev tools) is the permissions of a flatpak. In case I need to tweak things, I use Flatseal. I know you can manually do this from the command line but I don’t change permissions that often so I don’t bother learning how to do that.

Does the Flatpak Permissions Settings replace a tool like Flatseal?

What about flatseal then ? https://github.com/tchx84/Flatseal

https://github.com/tchx84/Flatseal (Also on Discover. For security reasons, the Discover store installs apps as sandboxed "flatpak" apps. This one is used to view what each up can do and change the permissions of apps. May be required if the sandboxing breaks something, though usually not required.)

I believe it does. As an example if I try running Godot from the Steam flatpak, it won't be able to see any of the contents of my ~/Projects folder unless I explicitly allow the steam flatpak access to that directory that via flatpak's CLI options or using Flatseal