mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1244] Using --trace to generate initial profiles #848
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#848
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 @reinerh on GitHub (Apr 23, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1244
Petter Reinholdtsen had the idea on the Debian BTS to use the output from the --trace command to generate initial/draft profiles, because it already reports if an application tries to open a file or create a socket.
Maybe an additional tool could parse the trace output and generate a profile out of it.
@netblue30 commented on GitHub (Apr 26, 2017):
I'll add and example in the man page. We'll build an "autoprofiler", at least something to create a starting point for building a profile.
@chiraag-nataraj commented on GitHub (Jul 23, 2018):
We have the
--buildcommand-line argument now, so closing this.