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.

Sign up for GitHub

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

Jump to bottom

secadm_vnode_check_exec calls pax_elf too early #30

Open
fweimer opened this issue Apr 3, 2016 · 0 comments
Open

secadm_vnode_check_exec calls pax_elf too early #30

fweimer opened this issue Apr 3, 2016 · 0 comments

Comments

@fweimer
Copy link

fweimer commented Apr 3, 2016

I'm not completely sure that this is indeed a problem, but it seems to me that secadm_vnode_check_exec is called at a point when execve can still fail. secadm_vnode_check_exec applies the new policy to the current thread with pax_elf, and if execve fails, this affects the running process image, not the new process image, and an unexpected policy is applied to it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fweimer