mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1323] Digikam profile #901
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#901
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 @curiosity-seeker on GitHub (May 31, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1323
This is the profile that works for me using Digikam 5.5.0 on Fedora 25. I haven't created a pull request as I'm not sure if the list of allowed syscalls works for other distros or versions. So I ask other users to test that profile before it can possibly be officially added. Note that the 2 noblacklist options are actually not necessary - I just added them to make sure that they won't conflict with possible future additions/changes to disable-common.inc.
@netblue30 commented on GitHub (Jun 1, 2017):
I merged you on mainline: https://github.com/netblue30/firejail/blob/master/etc/digikam.profile
Thanks, it is working fine on Kunbuntu 17.04. For Debian jessie I had to add 3 more syscalls. Also, I disabled private-dev in order to be able to connect to a camera - I'll have to look more into it.
The whitelisted seccomp line is commented out for now, until we get more information from people using other distributions. What you can do is to copy that line uncommented in /etc/firejail/digikam.local - it will have precedence over the regular seccomp line in the profile.
@curiosity-seeker commented on GitHub (Jun 1, 2017):
Thanks, but the profile contains
seccomp
and that prevents digikam from starting. Probably a mistake ...
EDIT: Sorry - correction. Using both seccomp.keep and seccomp works for me. I didn't know that both can be used together. Very interesting!
EDIT2: Nevertheless, seccomp alone doesn't work for me.
@curiosity-seeker commented on GitHub (Jun 25, 2017):
Sorry for coming back to this old issue but I'm still a bit confused. The
seccomp.keepline works for Fedora, Kubuntu and Debian Jessie. There might be other distros for which is doesn't. But shouldn't one expect thatseccompdoesn't work for them even less? So why did you add it?In my understanding
do not provide better security compared to
seccomp.keep whateveralone. Or am I wrong?