mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #706] When we use the --private-dev option with the --chroot option, the /dev/log socket is missing #483
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#483
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 @nuxwin on GitHub (Aug 13, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/706
Current behavior
The
/dev/logsocket is missing.Expected behavior
The
/dev/logsocket should be here (as stated in documentation):Additional info
Without the
--private-devoption, result is as follow:With the
--private-devoption, result is as follow:Info about my environment:
Note that the chroot is created with makejail and some internal utilities.
Thank you for your interest.
@nuxwin commented on GitHub (Aug 13, 2016):
Le 13/08/2016 à 04:38, Fred Barclay a écrit :
@Fred-Barclay https://github.com/Fred-Barclay
You've removed your comment but I'll answer you ;)
Works also for me. In such a case, the
/dev/logsocket is present.However, I've clearly mentionned that the problem occurs when using
the
--private-devoption with the ̀--chroot` option (case of a login shellvia FireJail).
Thank you.
Laurent Declercq
iHMS/i-MSCP Project Director
@Fred-Barclay commented on GitHub (Aug 13, 2016):
@nuxwin Right... I hadn't noticed that you used
--chrootas well when I made that reply. 😄 Once I realised it I deleted my comment.@nuxwin commented on GitHub (Aug 13, 2016):
@Fred-Barclay No grave ;)
Anyway, from my point of view, re-mouting /dev/log is something strange. What will be the result if the syslog daemon is restarted ? Normally, We use a proxy (syslogproxyd) but here, it seem that there is no way to tell firejail to not take care of /dev/log.
@netblue30 You're thinking about this?
@netblue30 commented on GitHub (Aug 13, 2016):
Ugly bug!
@nuxwin commented on GitHub (Aug 14, 2016):
@netblue30
Would be great to have a fix as soon as possible. Then, I would be able to release my InstantSSH plugin with FireJail support. I hope that the problem doesn't comes from systemd (they played a lot with syslog and their journal)... I'll try with a distro without systemd to see If I can reproduce.
BTW: No pressure ;)
@nuxwin commented on GitHub (Aug 15, 2016):
@netblue30 Bug found. On latest Debian distro with systemd (such as Jessie),
/dev/logis a symlink to/run/systemd/journal/dev-log. Once I mounted/run/systemd/journal/dev-log(I mounted full rundir in fact) in my chroot, this worked as expected. I'll provide a fix soon. We should avoid mounting full system rundir inside chroot. Thus, I'll see how we can handle that.Note that even without the
--private-devoption this doesn't work in chroot as long as/run/systemd/journal/dev-logis not mounted inside the chroot.@netblue30 commented on GitHub (Aug 15, 2016):
Sure, send a patch. Thanks!