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

Script execution control on Linux #1388

Open
l0kod opened this issue Sep 27, 2024 · 2 comments
Open

Script execution control on Linux #1388

l0kod opened this issue Sep 27, 2024 · 2 comments

Comments

@l0kod
Copy link

l0kod commented Sep 27, 2024

This is a recap of yesterday's meeting (see #1382) about script execution control on Linux, and how it compares to #1364 (see nodejs/node#54364). @RafaelGSS, @mhdawson, @rdw-msft, and I were attending.

LWN published an article about this new feature: Restricting execution of scripts — the third approach

I gave a talk last week that explains the goal, the challenges, and the current approach: Closing the script execution control gap

The changes required for Node.js would be:

  • To check all files containing code with execveat(2) + AT_CHECK
  • To restrict according to 2 complementary securebits: SECBIT_EXEC_RESTRICT_FILE and SECBIT_EXEC_DENY_INTERACTIVE

Here is a proof of concept for Python (using the original securebits): zooba/spython#12

Latest kernel patch series: https://lore.kernel.org/all/20240704190137.696169-1-mic@digikod.net/

I'll update this issue with the next patches (which will include an enlighten toy script interpreter).

@mhdawson
Copy link
Member

mhdawson commented Oct 1, 2024

@l0kod thanks for createing the issue and the links to additional info.

Copy link
Contributor

This issue has been inactive for 90 days. It will be closed in 14 days unless there is further activity or the stale label is taken off.

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

No branches or pull requests

3 participants