mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #6696] landlock: cannot rename file or directory inside landlocked path #3339
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#3339
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @osevan on GitHub (Mar 31, 2025).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6696
im sandboxing already with landlock option some daemons especially chrooted daemons,
server daemon starts well but child process like qmgr process exiting.
ofc these folders have write access by landlock itself
when i disable landlock no child process exiting with 1 and everything still now is well.
but, i can run with landlock too, but postfix starting in time period qmgr child processes, than failing:
maybe connected with this patch:
https://lwn.net/Articles/889577/
@kmk3 commented on GitHub (Mar 31, 2025):
Basic debugging information is missing; please follow the bug report template:
@kmk3 commented on GitHub (Mar 31, 2025):
(Offtopic)
Please see the following links for how to format code blocks in markdown:
@rusty-snake commented on GitHub (Mar 31, 2025):
Yeah, no reparenting is a documented
featurelimitation of Landlock ABIv1 that greatly limits application compatibility.@rusty-snake commented on GitHub (Mar 31, 2025):
I even told so in Nov 2023 (shortly after the initial implementation in firejail was merged/pushed): https://github.com/netblue30/firejail/discussions/6065#discussioncomment-7460581 (at the end).
@osevan commented on GitHub (Mar 31, 2025):
Tomorrow I will give more details @kmk3
@osevan commented on GitHub (Apr 1, 2025):
for my landlock postfix daemon tests im using vps root server debian sid. on my 4 notebooks running arch linux
apt install postfix-mysql
replacing postfisc-script with my modified postfix script here, else postfix-script makes trouble and not starting inside firejail sandbox. its a workaround by me.
replace postfix-script here
/usr/lib/postfix/sbin/postfix-script
here is full adjusted script https://gist.github.com/osevan/a0e1f8e1b32897f3cd403acafdfa7bb6
further i setupped virtual mail users this is basic smtp setup with dovecot
here is my magic postfix.profile
https://gist.github.com/osevan/521bb3e4b96ce9e1d5cc05b1ea5b45db
im starting postfix with firejail --debug --profile=/etc/firejail/postfix.profile postfix start
dont forget to mention postfix trying in some time period qmgr rename actions. so error not happen on every startup, only after time period like cronjob, but not figured out where i can adjust.
thanks and
best regards
@kmk3 commented on GitHub (Apr 1, 2025):
@osevan
Landlock support in firejail is currently experimental and targets ABI v1.
Also, currently no upstream profile enforces landlock.
As @rusty-snake mentioned, not being able to rename things inside landlocked
paths is a known limitation of ABI v1.
If that is an issue, then it's recommended to avoid enabling landlock support
in firejail.
To disable landlock, simply remove
landlock.enforcefrom the profile (or useignore landlock.enforcebefore it).@osevan commented on GitHub (Apr 1, 2025):
ok , i can use it ofc, but i thought, maybe someone make a update to latest abi 6