Skip to content

Issues: openSUSE/libpathrs

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

capi: use pathrs_inroot prefix for Root operations? api/cffi Related to the C-FFI API. ideas welcome An open problem which doesn't have a clear resolution.
#111 opened Nov 13, 2024 by cyphar 0.3.0
root/handle: readdir wrappers? api/handle Related to the handle API. api/root Related to the Root API. api/rust Related to the Rust API.
#110 opened Nov 13, 2024 by cyphar 0.3.0
root: add one-shot open operation api/cffi Related to the C-FFI API. api/root Related to the Root API. api/rust Related to the Rust API. resolver/openat2 Related to the openat2(RESOLVE_IN_ROOT) resolver backend.
#97 opened Oct 24, 2024 by cyphar 0.2.0
root: remove InodeType and switch to dedicated methods? api/rust Related to the Rust API.
#96 opened Oct 24, 2024 by cyphar 0.3.0
go bindings: should we try to use rustgo (no cgo)? ideas welcome An open problem which doesn't have a clear resolution.
#87 opened Oct 10, 2024 by cyphar
helpers: atomic file creation / linking an O_TMPFILE upstream/linux Dependent on upstream kernel work.
#68 opened Sep 20, 2024 by cyphar
errors: figure out if/how to expose ErrorKind api/rust Related to the Rust API.
#61 opened Sep 11, 2024 by cyphar 0.2.0
libpathrs-sys crate? api/cffi Related to the C-FFI API. api/rust Related to the Rust API.
#50 opened Aug 4, 2024 by cyphar 1.0.0
kernel hardening: block magic-link mounts security A security issue or hardening problem. upstream/linux Dependent on upstream kernel work.
#45 opened Jul 28, 2024 by cyphar
cffi: use something nicer to implement the API api/cffi Related to the C-FFI API.
#41 opened Jul 24, 2024 by cyphar
cdylib: symbol versioning api/cffi Related to the C-FFI API.
#38 opened Jul 19, 2024 by cyphar 1.0.0
go: add io/fs.FS implementation for bindings bindings/go Related to the Go bindings.
#32 opened May 6, 2024 by cyphar
capi: add a configuration interface api/cffi Related to the C-FFI API. help wanted Extra attention is needed ideas welcome An open problem which doesn't have a clear resolution.
#21 opened Dec 30, 2019 by cyphar 0.2.0
implement a "hardened" resolver backend ideas welcome An open problem which doesn't have a clear resolution. security A security issue or hardening problem.
#20 opened Dec 29, 2019 by cyphar
allow users to opt-out of fallbacks api/cffi Related to the C-FFI API. api/rust Related to the Rust API. security A security issue or hardening problem.
#19 opened Dec 29, 2019 by cyphar 0.3.0
upstream kernel hardening: pidfd_open("exe") security A security issue or hardening problem. upstream/linux Dependent on upstream kernel work.
#17 opened Dec 29, 2019 by cyphar
upstream kernel hardening: O_EMPTYPATH security A security issue or hardening problem. upstream/linux Dependent on upstream kernel work.
#16 opened Dec 29, 2019 by cyphar
pathrs.h should be auto-generated api/cffi Related to the C-FFI API. ideas welcome An open problem which doesn't have a clear resolution. packaging It's only packaging!
#14 opened Dec 28, 2019 by cyphar
RESOLVE_NO_XDEV support for emulated backend ideas welcome An open problem which doesn't have a clear resolution. resolver/opath Related to the userspace openat(2)-based resolver.
#8 opened Dec 23, 2019 by cyphar
binding-agnostic e2e tests tests Related to the test framework.
#6 opened Dec 23, 2019 by cyphar 0.2.0
ProTip! Updated in the last three days: updated:>2024-11-20.