mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2696] O_PATH undeclared (CentOS 6) #1697
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#1697
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 @chargrnv on GitHub (May 14, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2696
OS: CentOS 6.10
Version: 0.9.56-LTS (and newer)
I believe this would be provided by the kernel, but on CentOS 6 the kernel is too old.
http://man7.org/linux/man-pages/man2/open.2.html
O_PATH (since Linux 2.6.39)
0.9.54 builds OK under centos 6.
Is it possible for configure to check for the feature and have it optionally enabled/disabled?
I thought I had seen a patch posted previously, but I dont find any issues filed against this when searching for O_PATH.
@Vincent43 commented on GitHub (May 15, 2019):
Centos 6.10 is near end-of-life with only crucial security updates support. Is there a reason you didn't migrated to 7.x yet and/or you need firejail 0.9.56+ there?
@chargrnv commented on GitHub (May 15, 2019):
Moving to CentOS 7, but still have a lot of CentOS 6 and try and keep new versions of tools available. Thought LTS was "long term support" and would support older OSs.
@Vincent43 commented on GitHub (May 15, 2019):
Yes, however there are limits how old things it supports. Your kernel was released almost 10 years ago. This a time span of enterprise class support rather than what is expected from most community projects. I'm not saying support for it won't be added but it can't be taken for granted.
@smitsohu commented on GitHub (May 16, 2019):
Vanilla kernels older than 3.6 are unsupported currently, because of (from
man 2 open)But the patched CentOS/RedHat kernel seems to be fine, providing O_PATH is all we need to do.
@Vincent43 commented on GitHub (May 17, 2019):
Fixed by
203e34db60@chargrnv commented on GitHub (May 17, 2019):
Thanks!