I’m especially concerned about it being somehow broken, unwieldy, insecure or privacy-invasive.

Case in point; at times I have to rely on a Chromium-based browser if a website decides to misbehave on a Firefox-based browser. Out of the available options I gravitate towards Brave as it seems like the least bad out of the bunch.

Unfortunately, their RPM-package leaves a lot to be desired and has multiple times just been awful to deal with. So much so that I have been using another Chromium-based browser instead that’s available directly from my distro’s repos. But…, I would still switch to Brave in an instant if Brave was found in my distro’s repos. A quick search on repology.org reveals that an up-to-date Brave is packaged in the AUR (unsurprisingly), Manjaro and Homebrew. I don’t feel like changing distros for the sake of a single program, but adding Homebrew to my arsenal of universal package managers doesn’t sound that bad. But, not all universal package managers are created equal, therefore I was interested to know how Homebrew fares compared to the others and if it handles the packaging of the browser without blemishing the capabilities of the browser’s sandbox.


P.S. I expect people to recommend me Distrobox instead. Don’t worry, I have been a staunch user of Distrobox for quite a while now. I have also run Brave through an Arch-distrobox in the past. But due to some concerns I’ve had, I chose to discontinue this. Btw, its Flatpak package ain’t bad either. But unfortunately it’s not official, so I choose to not make use of it for that reason.

  • alt@lemmy.mlOP
    link
    fedilink
    arrow-up
    3
    arrow-down
    7
    ·
    1 year ago

    You already use an arch container that has access to the AUR, which has literally every package, available on linux.

    Call me paranoid if you will.

    if anything, flatpaks are THE official (universal) packaging format for Linux

    I don’t deny that, I make good use of a ton of flatpaks on my system. I also believe that it’s the best we have. And I would literally switch to Brave as a flatpak if it would satisfy the following:

    • Be official and thus maintained by Brave itself.
    • Not having to forego its own more powerful sandbox due to (hopefully) current restrictions of Flatpak. Yes, you read that correctly; while flatpaks are arguably the safest way to consume most applications, this doesn’t apply to apps that actually have stronger sandboxes which had to be ‘slimmed down’ when packaged as a flatpak. Thus, currently, for maximum protection, one simply can’t rely on flatpaks for their Chromium-based browsers. If you choose to do so and it has worked out for you wonderfully; that’s awesome, I’ve been there and enjoyed the experience as well. But, I can’t justify it for myself any longer.
    • Presi300@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 year ago

      I rely on flatpaks for all non-firefox browsers and haven’t had any issues with them, I’ve used the brave flatpaks specifically for almost a year now and no issues…

      • zwekihoyy@lemmy.ml
        link
        fedilink
        arrow-up
        3
        arrow-down
        1
        ·
        1 year ago

        it’s still factual that flatpaks sandbox is weak by default, especially compared to what chromium provides on its own.

          • alt@lemmy.mlOP
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            1 year ago

            Would you mind elaborating? First time hearing this and a quick search didn’t resolve it.

              • alt@lemmy.mlOP
                link
                fedilink
                arrow-up
                1
                ·
                1 year ago

                I am thankful that zypak exists so that Chromium-based browsers and Electron apps don’t have to explicitly flag --no-sandbox to continue functioning. However, it doesn’t undermine the fact that native Chromium’s sandbox is more powerful than Flatpak’s sandbox. As such, if one desires security, then one should gravitate towards the native installed one.

                It lets Chromium use flatpak sub-sandboxes

                Are you sure that’s the case?

                • AProfessional@lemmy.world
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  ·
                  1 year ago

                  The sandbox is not weakened meaningfully. It’s in a different namespace, no filesystem, no network, no GPU, seccomp rules still applied.

                  • alt@lemmy.mlOP
                    link
                    fedilink
                    arrow-up
                    1
                    arrow-down
                    1
                    ·
                    edit-2
                    1 year ago

                    Unfortunately, you didn’t -to my knowledge- support nor retract your claim on Chromium using flatpak sub-sandboxes. Therefore, I find it hard to continue taking your words at face value.

                    I have enjoyed these interactions, so don’t get me wrong; but if I (possibly) catch you on spreading misinformation (even if unintentional), then I find it hard to keep engagement up as there’s no guarantee that anything else coming from you is actually correct.

                    I would love to be corrected on this though, so please feel free if I have misunderstood you or anything else that would revive this conversation. If not, then I would still like to thank you from the bottom of my heart for this friendly interaction we’ve had. Take care!

      • alt@lemmy.mlOP
        link
        fedilink
        arrow-up
        1
        arrow-down
        2
        ·
        1 year ago

        I think I already addressed that point with

        If you choose to do so and it has worked out for you wonderfully; that’s awesome, I’ve been there and enjoyed the experience as well. But, I can’t justify it for myself any longer.

        If you meant something else, then please feel free to correct me.

    • Pantherina@feddit.de
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Officially supported doesnt mean its more stable. They can just take binaries, add dependenciesy tadaa.

      Bubblewrap is not insecure. But I am not an expert

      • alt@lemmy.mlOP
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Officially supported doesnt mean its more stable.

        Never implied that anyways. Official merely ensures that the amount of trusted parties can be minimized.

        Bubblewrap is not insecure.

        Bubblewrap, when properly applied is indeed excellent; perhaps the best utility to sandbox applications on Linux. I’m thankful that flatpaks makes use of bubblewrap, namespaces and seccomp to offer relatively safe/secure apps/binaries, I’m unaware of any other ‘(universal) package manager’ within the Linux-space that offers similar feats in that regard. Unfortunately, Chromium-based browsers just happen to have an even stronger sandbox -if properly configured- than flatpaks are currently capable of.

        • Pantherina@feddit.de
          link
          fedilink
          arrow-up
          3
          ·
          1 year ago

          Okay true. I am not so much into this Browser sandbox thing and dont really get it. Its a different way than bubblewrap, as from Firefox RPM for example I can open any file and save anywhere. But its process isolation right?

          • alt@lemmy.mlOP
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            as from Firefox RPM for example I can open any file and save anywhere. But its process isolation right?

            For Firefox, the verdict on its native sandbox vs Flatpak’s native sandbox doesn’t seem conclusive. With -assumingly- knowledgeable peeps on both sides of the argument, which indeed does raise the question how knowledgeable they actually are. Nonetheless, for myself, I’ve accepted Flatpak’s sandbox to not be inferior to Firefox’ native one. Thus, I don’t see any problem with using its flatpak.

            • Pantherina@feddit.de
              link
              fedilink
              arrow-up
              2
              ·
              1 year ago

              Apart from having all the nice KDE integration and things like Keepass integration, Fido2 keys, drag and drop and some more things…

              Also afaik the Fedora Firefox has a good SELinux profile and it runs damn fast. I did a speed test and it was best, along with Mozillas all-together-binary.

              • alt@lemmy.mlOP
                link
                fedilink
                arrow-up
                1
                ·
                1 year ago

                Apart from having all the nice KDE integration

                I’m a sucker for GNOME :P , but I’ll keep it in mind.

                things like Keepass integration

                The flatpak does allow integration, but isn’t built-in unfortunately; so one has to fiddle a bit themselves to set it up.

                Fido2 keys

                I should rely more on those. Do you have any recommendations? I’ve been hearing good things about Nitropad and Yubico, but I honestly don’t know if they’re actually good and how they would fare amongst eachother.

                drag and drop

                Overrated anyways /s :P .

                Also afaik the Fedora Firefox has a good SELinux profile

                It’s probably better configured with the native package than the flatpak one indeed. I wonder if this will change as Fedora is interested to ship Firefox as a flatpak by default on Silverblue (and variants).

                it runs damn fast. I did a speed test and it was best

                I haven’t had the best internet speeds since I’ve been relying on free VPN. But that’s on me :P .

                • Pantherina@feddit.de
                  link
                  fedilink
                  arrow-up
                  2
                  ·
                  1 year ago

                  Fedora packages a Flatpak Firefox themselves, based off the RPM. So its good too, but lacks codecs with currently no way to enable them so yeah. They would need am extension of some sort hosted on Flathub. So simply using Firefox Flatpak from Flathub makes more sense.

                  I got a Nitrokey for Heads but for some reason it never arrived? I can say these things are very expensive. And Heads uses PGP and not others.

                  • alt@lemmy.mlOP
                    link
                    fedilink
                    arrow-up
                    1
                    ·
                    1 year ago

                    I somehow forgot that Fedora also had Firefox in their flatpak repos.

                    I got a Nitrokey for Heads

                    You know what’s good, fam.

                    but for some reason it never arrived

                    That’s messed up, though.