mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1049] LTS version missing features and profiles? #712
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#712
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 @ghost on GitHub (Jan 14, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1049
@netblue30 commented on GitHub (Jan 14, 2017):
You will need to move to 0.9.44.x, LTS is frozen at version 0.9.38. There will be no new features added to it.
@SYN-cook commented on GitHub (Jan 14, 2017):
@rekixex Ubuntu has a policy for package updates, and this effectively freezes firejails version at 0.9.38.
At the moment, the easiest path to new firejail versions in Ubuntu is to add this PPA. Alternatively you find fresh packages also on Sourceforge.
If you are only after the profiles, you can just take them from Git and copy them to
~/.config/firejail. This may require manual adjustments in some cases, though.Your question was not pointed at me, please everyone apologize for stepping in.
@SYN-cook commented on GitHub (Jan 15, 2017):
@rekixex Well, that policy is less about version numbers and more about the package contents. In general, distributions with stable release model like Ubuntu tend to be pretty conservative regarding the introduction of new features into a stable release.
But still: You can try you luck and reach out to the Ubuntu package maintainers.... for this, all you need to do is making a request on Ubuntu launchpad.
@Fred-Barclay commented on GitHub (Jan 15, 2017):
@rekixex That script looks pretty good. Here's mine for reference (it clones the github repo as well):
I just update whenever I notice that @netblue30 has commited new changes - usually at least several times a week. Beware that this means you may get code that has bugs!
Oh - since you're using Ubuntu I would do this instead:
That way, apt and dpkg will know about firejail and be able to handle it properly. 😄
Cheers!
Fred
@curiosity-seeker commented on GitHub (Jan 16, 2017):
That's because the whole script is executed with root privileges, but that's not necessary. This is the script I'm using:
It works flawlessly. And note that make deb isn't necessary, IMHO. Until recently I used that script on Ubuntu, and Firejail 0.9.45 was shown in Synaptic.
EDIT: I'm not sure what's the use of the further instructions in your post. They are not necessary - Firejail works just by executing the script.
Btw., I added
https://github.com/netblue30/firejail/commits/master.atomas an RSS feed to Thunderbird so I can always see if there are commits that make an update necessary.
@netblue30 commented on GitHub (Jan 17, 2017):
Let's make it official! Can you guys push the script in contrib directory (https://github.com/netblue30/firejail/tree/master/contrib). All the scripts in this directory are getting installed in /usr/lib/firejail/. Then, I'll add an option in the interface, something like "firejail --update-deb" and call the script directly from firejail to update the thing. Will this work?
@netblue30 commented on GitHub (Feb 9, 2017):
all set, the feature is in: --git-install