mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #6114] Release Notes and/or Wiki 0.9.58.* & 0.9.56-LTS inconsistencies #3187
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#3187
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 @peter-lyons-kehl on GitHub (Dec 2, 2023).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6114
The above >
firejail (0.9.56-LTS) baseline; urgency=lowreads: "command line options removed:" ..."--rlimit*". However, https://github.com/netblue30/firejail/wiki/Comparison-of-firejail-and-systemd's-hardening-options#resource-limits still lists "rlimit*".Please clarify if "--rlimit*" and other removals apply to LTS only, or to any newer version.
@rusty-snake commented on GitHub (Dec 2, 2023):
2/3. https://web.archive.org/web/20220317053525/https://firejail.wordpress.com/
@kmk3 commented on GitHub (Dec 2, 2023):
To add to that: The "LTSbase" branch hasn't been updated since commit
c06212591("0.9.56.2 released", 2019-06-05), which is also where the "0.9.56.2" tag
points to.
And since commit
d1acb31c9("compile time: enable LTS", 2021-02-28) / version0.9.66 there is the
--enable-ltsconfigure option.So presumably the aforementioned replacement would be to build from the current
stable version (currently 0.9.72; see SECURITY.md) with
--enable-lts.@peter-lyons-kehl commented on GitHub (Dec 2, 2023):
As a want-to-be user, I come across https://firejail.wordpress.com/download-2/release-notes and https://firejailtools.wordpress.com/release-notes and the facts number 1. - 3. reported in the 1st comment here, and I'm confused as to
0.9.58is released after a higher version0.9.58.2, with no comment about this. As it turns out,0.9.58.2has two release entries there.@rusty-snake commented on GitHub (Dec 2, 2023):
Because it got retired and therefore removed from the website.
Because @netblue30 is the only person with write rights on WordPress.
Likely it got copied to the wrong file.
Maybe on GH too.Nope, only WP.This is something that could be fixed.
@peter-lyons-kehl commented on GitHub (Dec 2, 2023):
As a workaround, would it be OK to append "(unstable feature)" or "(work-in-pogress feature)" (or whatever you suggest) to non-LTS features mentioned in Wiki? I'm willing to append those in my clone of the Wiki.
Any other such features other than
chroot|overlay|rlimit|cgroup|private-bin|private-lib?grep -r -i -E "chroot|overlay|rlimit|cgroup|private-bin|private-lib"reports them mostly/most standing out in https://github.com/netblue30/firejail/wiki/Comparison-of-firejail-and-systemd's-hardening-options#resource-limits and https://github.com/netblue30/firejail/wiki/Frequently-Asked-Questions.@rusty-snake commented on GitHub (Dec 3, 2023):
Workaround for what? Wrong release notes?
They are neither unstable nor wip nor anything else. They are just rarely used.
IDK why you talk about the wiki all the time. Imho the manpages are a much more important source of information.
What you be ok imho and is actable by use.
@rusty-snake commented on GitHub (Dec 23, 2023):
db09546f29