mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3076] Profile Updates #1928
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#1928
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 @FOSSONLY on GitHub (Dec 9, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3076
I would like to suggest a manual or automatic update for profiles. It is noted that there are often problems with the profiles. Especially since not all users use the same versions of different programs, and the profiles per version of Firejail are usually adapted to certain program versions. By automatically updating the profiles directly via git, any adjustments to the profiles could be immediately received by the users. This could prevent typical problems with program updates. What do you think?
@rusty-snake commented on GitHub (Dec 15, 2019):
👍 a way to get profile fixes and enhancements to debian stable for example would be great.
@FOSSONLY commented on GitHub (Dec 15, 2019):
Yeah. I mean, theoretically, anyone could do that quickly by hand. Just install git and download the profiles to "/etc/firejail". The idea was to simplify it and make it easier for beginners.
@rusty-snake commented on GitHub (Dec 15, 2019):
You missed one point, new/changed options does not work with older firejail binaries.
Example: Debian stable has firejail 0.9.58
@Vincent43 commented on GitHub (Dec 16, 2019):
Yes, there is no guarantee that newer profiles will work with older firejail so shipping those separately isn't possible atm.
@ghost commented on GitHub (Jan 16, 2020):
I'm not sure if all distros offer a firejail-git package like the one from AUR, but we could ask packagers to promote that if they do. I like the idea of a 'rolling-release-kind' firejail, it would offer some interesting opportunities (besides unburdening collaborators a bit regarding issues management/small profile fixes). E.g. https://github.com/netblue30/firejail/pull/3150.
@rusty-snake commented on GitHub (May 6, 2020):
If I look now at the relnotes, IMHO it is not possible to use master profile with a stable firejail after some scripts.
@matu3ba commented on GitHub (May 7, 2020):
@FOSSONLY So your proposal wants to fetch one of the release branches and adjust the paths for each distributions, because the distribution package is out of date?
Thats the job of distribution packagers.
Sadly there dont exist programs or scripts that fetch on what distribution you are and adjust the installation paths/rules for the distro accordingly, because the paths are tracked globally different on every distribution with
packet managers.Maybe you can be more specific what you want to do. Doing things for only a subset of the distributions belongs to anothet project.
@rusty-snake commented on GitHub (May 7, 2020):
Every distro I know uses
/etc/firejail, that's not an issue.