With the maas 3.2 snap (core20-based) we noticed a difference in behavior when running on a focal and jammy (tested in containers).
The snap has the `home` plug. On focal, an app running as root can read root-owned files in other users' homes, while when running on focal, that's not possible anymore:
With the maas 3.2 snap (core20-based) we noticed a difference in behavior when running on a focal and jammy (tested in containers).
The snap has the `home` plug. On focal, an app running as root can read root-owned files in other users' homes, while when running on focal, that's not possible anymore:
# echo test > /home/ubuntu/ testfile testfile2 testfile2 testfile* testfile testfile2
# echo test > /home/ubuntu/
# chown ubuntu.ubuntu /home/ubuntu/
# ls -l /home/ubuntu/
-rw-rw-r-- 1 ubuntu ubuntu 5 Jul 12 13:44 /home/ubuntu/
-rw-rw-r-- 1 root root 5 Jul 12 13:44 /home/ubuntu/
# snap install maas --channel=3.2
# focal host testfile' testfile: Permission denied testfile2'
root@f:~# snap run --shell maas -c 'cat /home/ubuntu/
cat: /home/ubuntu/
root@f:~# snap run --shell maas -c 'cat /home/ubuntu/
test
# jammy host testfile' testfile: Permission denied testfile2' testfile2: Permission denied
root@j:~# snap run --shell maas -c 'cat /home/ubuntu/
cat: /home/ubuntu/
root@j:~# snap run --shell maas -c 'cat /home/ubuntu/
cat: /home/ubuntu/