mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1332] private-etc with custom files #912
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#912
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 @allo- on GitHub (Jun 11, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1332
Would it be possible to create a private-etc with custom files?
This means not copying
/etc/passwdto the jail, but copying~/firejail/etc/passwdto/etc/passwdin the jail, so you can i.e. hide which users exist outside of the jail and still have a working passwd file with users like root and the user running firejail (even with changed name, i guess only the uid needs to match inside the jail).There is
--bind, but it works only for root. And I do not need to bind the file, copying it is sufficient (and sometimes even preferable).@netblue30 commented on GitHub (Jun 14, 2017):
This will bring in a lot of security problems.
@allo- commented on GitHub (Jun 14, 2017):
I want to copy a file owned by a non-root user into a jail started by a non-root user.
I do not see the security issues, can you give an rough example why this could be a problem?
@netblue30 commented on GitHub (Jun 16, 2017):
All you have to do is to bring in a different /etc/shadow file and su to root after the sandbox started.
@allo- commented on GitHub (Jun 16, 2017):
OK. I need to look more into the infrastructure. Though it uses user mode jails when not run as root.