mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2623] /dev/null created with wrong permissions #1664
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#1664
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 @viq on GitHub (Mar 28, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2623
Noticed when trying to start calibre:
and indeed:
Archlinux,
firejail 0.9.58.2-1,@Vincent43 commented on GitHub (Mar 29, 2019):
Interesting, for me it is ok in latest git version:
@rusty-snake commented on GitHub (Mar 30, 2019):
@Vincent43 @viq @SkewedZeppelin Can reproduce with every profile that include
disable-programs.incI have symlinked
.wget-hststo/dev/nullso that wget does not make hsts entries, because since 0.9.58.wget-hstsis blacklisted, blacklisted FJ also /dev/null.@viq have you symlinked something in your HOME to /dev/null? Try
firejail --debug@Vincent43 commented on GitHub (Mar 30, 2019):
@rusty-snake Yes, I remember some issues when I had something in home linked to
/dev/null. As a workaround you may try making file/dir immutable withchattr +i <file>instead of linking to/dev/null.@rusty-snake commented on GitHub (Mar 30, 2019):
@Vincent43 already done ;)
@rusty-snake commented on GitHub (May 11, 2019):
@viq still an issue?
@chiraag-nataraj commented on GitHub (May 21, 2019):
Going to close due to inactivity. @viq, if this is still an issue, please feel free to re-open.