Package: firejail
Version: 0.9.62-2
Severity: normal

Dear Maintainer,

In order to access unlocked files and directories encrypted with
fscrypt, their
protectors. which lies under /.fscrypt of root and each FS with this feature
deployed, should also be accessible.

Inside firejail, /.fscrypt could be made accessible with "noblacklist"
statement in profile, but there seems no way to introduce /home/.fscrypt
into firejail, which cause all file and directory in separate /home
encrypted
with fscrypt inaccessible inside it.




-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'testing-proposed-updates'), (500,
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8),
LANGUAGE=zh_CN:zh (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firejail depends on:
ii libapparmor1 2.13.3-7
ii libc6 2.29-7

Versions of packages firejail recommends:
ii firejail-profiles 0.9.62-2
ii iproute2 5.4.0-1
ii iptables 1.8.3-2
ii xauth 1:1.0.10-1
ii xpra 3.0.5+dfsg1-1
ii xserver-xephyr 2:1.20.6-1

firejail suggests no packages.

-- no debconf information

Reply via email to