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

Document transitive allowlisting limitations #1328

Open
mlw opened this issue Apr 16, 2024 · 1 comment
Open

Document transitive allowlisting limitations #1328

mlw opened this issue Apr 16, 2024 · 1 comment
Labels
docs Documentation-related issues

Comments

@mlw
Copy link
Contributor

mlw commented Apr 16, 2024

Transitive allowlisting is a powerful feature to allow developers to live in LOCKDOWN mode. However there are certain limitations in the current implementation that developers need to be aware of to ensure the feature can work properly.

This largely means that Santa must be given a (brief) opportunity to create a transitive rule before any resultant binary is executed.

Solving this completely is likely not desirable. It would require a large amount of synchronization between Santa's event stream processing compiler operations and the event stream responsible for authorizing execs. This would require a lot of contention that would likely degrade build performance in unacceptable ways.

@mlw mlw added the docs Documentation-related issues label Apr 16, 2024
@mlw
Copy link
Contributor Author

mlw commented Apr 16, 2024

Related: #1327

See this comment for more details related specifically to the Go toolchain's go run tool: #1327 (comment)

More broadly this would also apply to things like cargo run, but even for tight execution loops, such as clang ./foo.c; ./a.out would be susceptible to the same race.

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

No branches or pull requests

1 participant