snapd

Oh don't let me get me started on this. I use Firefox on a work machine and I spent a number of hours troubleshooting why it couldn't access the Internet when I was connected on VPN. I suspected it had something to do with snapd, so I downloaded the .tar.gz release of Firefox and it worked. I kept investigating and figured it must have something to do with snap.firefox.firefox apparmor profile because the VPN client was symlinking the /etc/resolv.conf to /opt/.../resolv.conf However, updating the apparmor profile didn't help so I ultimately realized that snap has a hardcoded list of paths that get mounted into the app container [1] and there's no way to change this. There are a number of reasons to hate on snapd, but this almost made me flip the table. Also, as a bonus point, if you look at the apparmor profile I mentioned it has a ton of

That's interesting, since it looks like the issues raised by the SUSE Security audit are not all fixed yet: https://github.com/snapcore/snapd/projects/4

Am I missing something isn't https://github.com/snapcore/snapcraft and https://github.com/snapcore/snapd Free Software under the GPL3. I had seen some discussion before about the server not being open source but I can clearly see the store api there. I'm just looking at the code now and haven't taken any time in testing it out for myself yet. Regarding debian packages and apt as we have seen with the amount of PPAs, there really has to be some solution for that. I like the snap format I believe it's heading in the right direction. It still has some problems with desktop software but that seems to be addressed as it has progressed. There is this strange cold war between Red Hat and Canonical and Red Had seem to have most of the NIH problems if you look at the history. I really don't think Red Hat or some of it's developers possible like re

If you're still interested, I found the link: https://forum.snapcraft.io/t/wip-refresh-app-awareness/10736 and https://github.com/snapcore/snapd/projects/3 It is actively being worked on.

FlatPak is a project initially hosted on freedesktop.org infrastructure with distributed copyright ownership under a copyleft license. It was initially founded by Red Hat employees but has attracted substantial support and contributions by companies such as Endless and Collabora, not to mention volunteer contributors. The sandboxing part was spun off to the bubblewrap project, which has been adopted by the community for other purposes, such as Gnome's Epiphany browser. https://github.com/containers/bubblewrap https://blogs.gnome.org/mcatanzaro/2020/03/11/epiphany-3-36-... SnapCraft on the other hand is a project that requires copyright assignment to Canonical Ltd for contributions, which presumably has the intended effects of keeping non-Canonical contributions close to zero. https://github.com/snapcore/snapd/blob/master/CONTRIBUTING.m...

Seems you're on Debian. ATM, confinement doesn't work there, though they promise to fix it soon (https://github.com/snapcore/snapd/wiki/Distributions#debian).

I don't understand what's with this issue: https://github.com/snapcore/snapd/pull/2236 What does Intel RealSense have to do with any of this? Is it a GitHub bug, showing an issue from another repo?

It's a new package manager that implements existing linux security mechanisms. It will use apparmor to confine the snap to the directories that it is allowed to read and write. By default, $HOME/snap/snap-name/ Then the snap can use interfaces to go out of its confinement and access things that the user has agreed to allow: https://github.com/snapcore/snapd/wiki/Interfaces

Here's the status of support everywhere: https://github.com/snapcore/snapd/wiki/Distributions

Stars are useless and don't mean anything except a lot of people have starred the repo. Anyway, it's not too hard to see why they have so many commits: https://github.com/snapcore/snapd/commits/master?after=Y3Vyc... They're taking "make lots of tiny commits" advice to an almost comical extreme. And they also have terrible commit messages.