| 2023-09-27 05:56:06 |
Heinrich Schuchardt |
description |
I have the riscv64 snap fwts V23.09.00 installed on Ubuntu Mantic.
$ sudo /snap/bin/fwts --ebbr
/snap/fwts/904/usr/local/bin/fwts: Cannot open results log 'results' (you may need to remove it to set proper permissions).
Files result and results.log does not exist in the current directory.
In /var/log/kern.log I find this entry:
2023-09-27T07:07:21.435093+02:00 unmatched kernel: [255426.512789] audit: type=1400 audit(1695791241.430:407): apparmor="DENIED" operation="capable" class="cap" profile="snap.fwts.fwts" pid=235742 comm="snapcraft-runne" capability=2 capname="dac_read_search"
$ uname -a
Linux workstation 6.2.0-24-generic #24.1-Ubuntu SMP Fri Jun 23 00:35:17 UTC 2023 riscv64 riscv64 riscv64 GNU/Linux
The current drive is mounted as
/dev/nvme1n1p2 on /home type ext4 (rw,nosuid,relatime)
After
$ sudo touch results.log
I can run fwts.
It does not work with a chmod 66 results.log that is not owned by root.
It seems that the restrictions for the snap are a bit tight. |
I have the riscv64 snap fwts V23.09.00 installed on Ubuntu Mantic.
$ sudo /snap/bin/fwts --ebbr
/snap/fwts/904/usr/local/bin/fwts: Cannot open results log 'results' (you may need to remove it to set proper permissions).
Files result and results.log does not exist in the current directory.
In /var/log/kern.log I find this entry:
2023-09-27T07:07:21.435093+02:00 unmatched kernel: [255426.512789] audit: type=1400 audit(1695791241.430:407): apparmor="DENIED" operation="capable" class="cap" profile="snap.fwts.fwts" pid=235742 comm="snapcraft-runne" capability=2 capname="dac_read_search"
$ uname -a
Linux workstation 6.2.0-24-generic #24.1-Ubuntu SMP Fri Jun 23 00:35:17 UTC 2023 riscv64 riscv64 riscv64 GNU/Linux
The current drive is mounted as
/dev/nvme1n1p2 on /home type ext4 (rw,nosuid,relatime)
After
$ sudo touch results.log
I can run fwts.
It does not work with a chmod 666 results.log that is not owned by root.
It seems that the restrictions for the snap are a bit tight. |
|
