mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1405] Firejail X11 sandboxing unusable with latest xpra #960
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#960
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 @chiraag-nataraj on GitHub (Jul 26, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1405
Piggybacking off of #1016, but now I'm seeing this with every program. It got so bad that I had to write a wrapper script as follows:
I'm using xpra v2.1-r16505.
@chiraag-nataraj commented on GitHub (Jul 28, 2017):
With newer xpra versions, 5 seconds isn't enough delay (at least on my system) - not sure why exactly. Neither is waiting for
/tmp/.X11-unix/<display>. Here is a sample log:@chiraag-nataraj commented on GitHub (Jul 30, 2017):
Wait. @netblue30, couldn't you just call
xpra start --attach=yes? Then,xprawould automatically attach after initializing.[Edit] Just tested this with the
jailscript I posted above and it works. The only thing is that the "Server endpoint" listed in the session info listssocket:/run/xpra/systeminstead of the normal display, but it seems to work as usual.[Edit2] It seems using the
--attachargument starts a proxy. I'm not entirely sure why, but hey...it works.@chiraag-nataraj commented on GitHub (Jul 30, 2017):
@netblue30, I took a crack at trying to implement this. I haven't done much security-focused stuff, so I'm not sure if I'm doing anything dangerous here, but this issue is fixed. As a bonus,
firejailitself has to do much less monitoring since we letxpratake care of that.@chiraag-nataraj commented on GitHub (Jul 31, 2017):
Closing for now.