mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #877] "firejail --chroot=/" destroys resolv.conf #594
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#594
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 @mcarpenter on GitHub (Oct 27, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/877
This is a silly use case but my broader concern is that this could happen anywhere that
copy_file()has identical paths to source and destination arguments. In this case, the file in question is truncated to zero bytes:@netblue30 commented on GitHub (Oct 27, 2016):
Security problem! I have fixed copy_file(), if the destination already exists it returns an error. I also put code in to reject --chroot=/. This is the commit:
6144229605. Thanks.@mcarpenter commented on GitHub (Oct 27, 2016):
Thanks!