Permissions Prompting: A Deep Dive
discourse.ubuntu.com
My name is Oliver Calder and I am part of the Snapd team at Canonical. In this post, I’m excited to share some more information about a project I’ve been working on over several years with a talented group of people across the AppArmor, Desktop, Design, and Snapd teams: Permissions Prompting. Permissions Prompting is a new layer of user-defined security which empowers users to control at runtime the level of access applications have to the host system. There was an excellent post from around t...
  • jdr@lemmy.ml
    18 days

    Are they still trying to make snap happen?

    It’s not going to happen.

    • Wilmo@lemmy.mlEnglish
      18 days

      Its also for my experience the worst way to use apps.

      The fact that I can’t “update” my software without closing it first.

      Why can I do that with all other package formats? I get it won’t be the new version until I reopen the app but still. Its unnecessary friction.

      Also with the prompting last I used it Firefox couldn’t download anything with it enabled.

      Like you ship Ubuntu with like 4 major snaps including the security center and it hasn’t or hadn’t worked with your shipped snaps for at least a year?

      • atzanteol@sh.itjust.worksEnglish
        18 days

        The fact that I can’t “update” my software without closing it first.

        Why can I do that with all other package formats? I get it won’t be the new version until I reopen the app

        Asked and answered.

        • Wilmo@lemmy.mlEnglish
          17 days

          Not really though? Or rather - then answer the other half. Why are flatpaks, deb, rpm, arch, etc. ALL able to update in place? But with snaps we need that sucker closed? It sucks to use like that.

          • atzanteol@sh.itjust.worksEnglish
            17 days

            Because the app isn’t updated until it’s restarted.

            Do you think you applied that Firefox security update because you updated the flatpak? Because you haven’t if you left your browser running.

            • Wilmo@lemmy.mlEnglish
              16 days

              Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good.

              I don’t care if Firefox isn’t updated until I restart it. I just don’t want that terrible workflow:

              Click update all. Firefox is open, therefore won’t update until you close it and click update again.

              Every other package manager: Click update. All apps update. When I am ready to close Firefox it’ll be updated next time I use it.

              • atzanteol@sh.itjust.worksEnglish
                16 days

                Did I explicitly state that I was aware of how this worked in my original comment? I did? Oh good.

                Hence my “asked and answered” response. 🙄

                • itslilith@lemmy.blahaj.zone
                  15 days

                  the question asked was “why can’t snap do this thing, that every other package manager can”

                  stop being obtuse on purpose.

            • brax@sh.itjust.works
              17 days

              The problem is that you have to break your workflow to update shit, or you have to do updates multiple times to work around the things you’re doing.

    • thingsiplay@lemmy.ml
      18 days

      Snap is already a big part of Ubuntu since years. So what do you mean by “its not going to happen”?

    • lengau@midwest.social
      16 days

      They have been trying to work with the Flatpak people to make it a standard everyone could share. After half a decade of frustration I think they just gave up and decided to do it themselves.