mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #525] --read-only=~ does not work and does not fail-fast #372
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#372
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 @vn971 on GitHub (May 18, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/525
The command-line argument
--read-only=~is being accepted byfirejailbut seemingly has no effect on the sandbox. Should it?I'm not sure about the implementation details for this, but from the UX point of view, there should be some error. Thoughts?
@netblue30 commented on GitHub (May 18, 2016):
Bug! I just put a fix int, thanks!
@vn971 commented on GitHub (May 18, 2016):
Cool!
// for history, commit:
2a57a24561@netblue30 BTW, offtopic. If you want, you can close issues automatically by including "fix GH-525" or "fix #525" into your commit message. The issue will automatically be closed with a reference to the commit.
@netblue30 commented on GitHub (May 20, 2016):
Thanks!