mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #6035] lutris: Ubisoft Connect: Error at hooking API #3164
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#3164
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 @nutta-git on GitHub (Oct 5, 2023).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6035
Description
Ubisoft connect doesn't work with Lutris's default profile.
Steps to Reproduce
ln -s /usr/bin/firejail /usr/local/bin/lutriscp /etc/firejail/lutris.profile ~/.config/firejail/lutris.profile(to a whitelist a single folder)firecfg --fixExpected behavior
Ubisoft Connect should work without throwing an error
Actual behavior
Lutris gave an API error[
]
Behavior without a profile
rm /usr/local/bin/lutrisUbisoft Connect starts fine without Firejail profile
Environment
Checklist
/usr/bin/vlc) "fixes" it).https://github.com/netblue30/firejail/issues/1139)browser-allow-drm yes/browser-disable-u2f noinfirejail.configto allow DRM/U2F in browsers.--profile=PROFILENAMEto set the right profile. (Only relevant for AppImages)Log
Output of
LC_ALL=C firejail /path/to/programOutput of
LC_ALL=C firejail --debug /path/to/programlutris-firejail-debug.txt
@nutta-git commented on GitHub (Oct 6, 2023):
Setting ignore to seccomp !modify_ldt and seccomp.32 !modify_ldt fixes this issue.
Should I close this issue or keep it open?
@ghost commented on GitHub (Oct 6, 2023):
Thank you for reporting. Disabling the seccomp filter like you did might fix your issue, but the lutris sandbox would be more hardened if we could ascertain an improved, working filter. Let's keep this open so people can chime in to try determining such a replacement seccomp filter.
Could you try to find a working seccomp filter? There's more info here.
@nutta-git commented on GitHub (Oct 6, 2023):
@glitsj16
I don't know much about this to offer any help, I sort of found out by trial and error.
I followed the link your provided, and try to find out which seccomp was causing issues.
When I run:
firejail --seccomp-error-action=log /usr/bin/lutrisEverthing works fine, and journalctl doesn't list anything
When I run :
firejail /usr/bin/lutrisI get original issue
@ghost commented on GitHub (Oct 6, 2023):
That's relevant info, thanks!
Anyhing in journalctl when you
--seccomp-error-action=EPERM(the default) and--seccomp-log=yes?@nutta-git commented on GitHub (Oct 6, 2023):
@glitsj16
firejail --seccomp-error-action=EPERM /usr/bin/lutrisI get the original issue and nothing is shown on [journalctl --grep=SECCOMP --follow]
firejail --seccomp-log=yes /usr/bin/lutrisConsole prints out:
Error: invalid --seccomp-log=yes command line optionAnd nothing happens.
@ghost commented on GitHub (Oct 6, 2023):
@nutta-git
Argh, my bad. You'll need to change the default
# seccomp-log notoseccomp-log yesin /etc/firejail/firejail.config... Apologies for the confusion.@nutta-git commented on GitHub (Oct 6, 2023):
@glitsj16
No worries, I edited firejail.config, rebooted and tried again.
Term1)
sudo journalctl --grep=SECCOMP --followTerm2)
firejail --seccomp-error-action=EPERM /usr/bin/lutrisOriginal Issue and nothing was listed on journalctl
I tried:
firejail --seccomp-error-action=log /usr/bin/lutrisagainAnd it seems to work fine, but nothing is being listed in journalctl
@nutta-git commented on GitHub (Oct 6, 2023):
I don't mean to impose, but can you try to reproduce the issue by following the steps found in the First Post.
I feel like this a problem is unique to me. If its not reproducible, then we can close this issue.
@ghost commented on GitHub (Oct 6, 2023):
No problem. I'll try to reproduce over the weekend, although my hardware isn't any good for gaming & wine. We can keep this open for a while. Other collaborators/users might have input.
@rusty-snake commented on GitHub (Oct 7, 2023):
Tried allow-debuggers?
@nutta-git commented on GitHub (Oct 8, 2023):
@rusty-snake
I un-commented allow-debuggers in
.config/firejail/lutris.profileAlso have; seccomp-log yes in
/etc/firejail/firejail.configThen I re-ran the test.
Term1)
sudo journalctl --grep=SECCOMP --followTerm2)
firejail --seccomp-error-action=EPERM /usr/bin/lutrisNow I no longer get the original issue, nothing is listed in journalctl
I tried:
firejail --seccomp-error-action=log /usr/bin/lutrisSame result as the first command, no issue and no journalctl log
@nutta-git commented on GitHub (Oct 24, 2023):
I think I found the right syscalls for this issue: ptrace,clone3 (and optionally) process_vm_readv.
I had
journalctl -f | grep "kernel"running, looking for syscalls lutris was usingI need to whitelist just
ptraceandclone3, journalctl did list forprocess_vm_readywhen a game was running, but it didn't crash the game.seccomp !modify_ldt,!clone3,!ptrace,!process_vm_readvseccomp.32 !modify_ldt@ghost commented on GitHub (Oct 24, 2023):
Nice finds! Please consider opening a PR.