Debian 13:

$ uname -r
6.12.88+deb13-amd64

$ snap debug sandbox-features|grep confinement
confinement-options:  classic devmode

$ snap debug confinement
partial

$ aa-enabled
Yes

Ubuntu (24.04):

$ uname -r
6.8.0-117-generic

$ snap debug sandbox-features|grep confinement
confinement-options:  classic devmode strict

$ snap debug confinement
strict

$ aa-enabled
Yes

What does this mean, you ask? Well, basically every Snap package you thought was running isolated in it’s own little sandbox were running unconfined the whole time. The prorpietary app you removed the :home connection from, so it wouldn’t be able to access your home directory? Well, it could have exfiltrated all our private files in the meantime.

How is this not a bigger deal and how are Snaps ever to become mainstream when even today, more than 10 years after the introduction of snaps, you can’t run them sandboxed on a huge portion of Linux distros?

  • Rioting Pacifist@lemmy.world
    link
    fedilink
    arrow-up
    9
    ·
    1 day ago

    Because snaps is a Ubuntu thing, and not particularly widely used on Debian.

    #rank name inst vote old recent no-files

    2 util-linux 4000213 2110588 1172784 345252 371589

    2258 snapd 19307 17314 846 1033 114

    I actually don’t understand what use case snapd on Debian covers better than docker on Debian or snapd on ubuntu