Skip to content
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

Deterministic library with explicit ABI #5

Open
l0kod opened this issue Jul 25, 2024 · 0 comments
Open

Deterministic library with explicit ABI #5

l0kod opened this issue Jul 25, 2024 · 0 comments

Comments

@l0kod
Copy link

l0kod commented Jul 25, 2024

Hi @Edward-Knight,

First, it's great to see such Python library for Landlock. Thanks!

Libraries for other languages (e.g. Rust, Python) require users to be explicit about the Landlock ABI they want to use, with a best-effort default approach. This enables users to get a deterministic sandboxing useful to avoid potential future too-hermetic sandboxing. Otherwise, the current approach could break application and legitimate use cases (e.g. with an update of the Python library, but without changing the app code, then not testing it with this new version).

I gave a talk at FOSDEM about this kind of issues. Here are related discussions landlock-lsm/rust-landlock#12, and the current Rust library documentation.

I see that landlock_abi_version() is used to check at run time which access rights should be used (e.g. all_file(), all_dir()). A call to Ruleset() uses FSAccess.all, which may be different according to the running kernel.

It would be good to enable users to create deterministic sandboxes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant