originally, I have reported this issue on chromium 138.0.7204.49-1~deb12u1
the problem got fixed by upgrading chromium to next version
but now, after upgrading to
Version 140.0.7339.80 the problem is back:
here is my RBAC reporting chromium trying to open files that it has no
business opening:
07:13:43 grsec: (testuser:U:/usr/lib/chromium/chromium) denied access
to hidden file /home/testuser/.ssh by
/usr/lib/chromium/chromium[ThreadPoolForeg:7646] uid/euid:1000/1000
gid/egid:1000/1000, parent /usr/sbin/init[init:1] uid/euid:0/0 gid/egid:0/0
07:13:43 grsec: (testuser:U:/usr/lib/chromium/chromium) denied access
to hidden file /home/testuser/.gnupg by
/usr/lib/chromium/chromium[ThreadPoolForeg:7646] uid/euid:1000/1000
gid/egid:1000/1000, parent /usr/sbin/init[init:1] uid/euid:0/0 gid/egid:0/0
07:13:43 grsec: (testuser:U:/usr/lib/chromium/chromium) denied access
to hidden file /boot by /usr/lib/chromium/chromium[ThreadPoolForeg:7646]
uid/euid:1000/1000 gid/egid:1000/1000, parent /usr/sbin/init[init:1]
uid/euid:0/0 gid/egid:0/0
07:13:43 grsec: (testuser:U:/usr/lib/chromium/chromium) denied access
to hidden file /home/testuser/.dbus by
/usr/lib/chromium/chromium[ThreadPoolForeg:7646] uid/euid:1000/1000
gid/egid:1000/1000, parent /usr/sbin/init[init:1] uid/euid:0/0 gid/egid:0/0
why is chromium doing this, and why does Debian tolerate this behavior ?
