mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #426] Possibility to use files that aren't in /etc for --private-etc #312
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#312
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 @kadogo on GitHub (Apr 12, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/426
Hello, I think it would be nice if we can use files that aren't in /etc for --private-etc options.
Cheers.
@netblue30 commented on GitHub (Apr 12, 2016):
This will create a lot of security problems. I can let only existing files in /etc.
@kadogo commented on GitHub (Apr 13, 2016):
You have maybe a solution when I will use a file in etc but that I have modify ?
Exemple, I will test some repo with yum but I not will modify my yum.conf in /etc so I think to modify it before and pass it to firajail.
@netblue30 commented on GitHub (Apr 13, 2016):
Some of the files there are very dangerous, for example the user can modify /etc/shadow and put a new root password there.
If you are running as root, you could use "firejail --bind" and replace your /etc directory with a totally new one.
@kadogo commented on GitHub (Apr 13, 2016):
I will give a chance at the --bind option.
I would ask too if --chroot option will himself create /proc and /dev in the futur (or if there is some security issue too ?)
@netblue30 commented on GitHub (Apr 14, 2016):
chroot mount under /dev the real /dev directory, it just needs a directory defined for the mount point. /proc is mounted with the special /proc from the namespace.