mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1659] Profile needed for MasterPDFeditor #1120
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#1120
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 @frank-github on GitHub (Nov 26, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1659
Hi,
need a profile for Master PDF Editor for Linux
https://code-industry.net/free-pdf-editor/
tried it myself by copying and changing qpdfview.profile
but program is not started for any reason if this one items are included (like qpdfview)
do I need this? No security problem, if I did not using this both lines?
any hint/tips are welcome :-)
Frank
@smitsohu commented on GitHub (Nov 28, 2017):
Hi @frank-github, it is a common experience that applications don't tolerate all available sandbox features. Especially
memory-deny-write-executecauses trouble in many cases.Just try to confine the editor as tight as possible, while keeping everything working that is important to you. When the application fails to even start, that's kind of a hard boundary.
If you want you can experiment with some additional profile options like
@smitsohu commented on GitHub (Nov 28, 2017):
Just skimming through the handbook... chances are slim but it might be possible to keep
memory-deny-write-executeif you disable JavaScript in the settings.