You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, it's not possible to filter both. If a filtered program call a 32 bits program, it will result in a bad system call. In libseccomp, one can differentiate between the 2 by checking for __X32_SYSCALL_BIT mask on the system call number. It would be very useful for my use case, filtering calls from a sandbox environment that may use 32 bits applications.
The text was updated successfully, but these errors were encountered:
I would also use such a feature. I'm also a bit confused about the current API - does the filter just reject/kill syscalls with a different AUDIT_* arch? This could definitely be better documented.
Looks like this library doesn't handle __X32_SYSCALL_BIT at all, based on a search of the source code. Am I wrong, or does this mean restricted code can potentially set this bit to bypass restrictions?
At the moment, it's not possible to filter both. If a filtered program call a 32 bits program, it will result in a bad system call. In libseccomp, one can differentiate between the 2 by checking for
__X32_SYSCALL_BIT
mask on the system call number. It would be very useful for my use case, filtering calls from a sandbox environment that may use 32 bits applications.The text was updated successfully, but these errors were encountered: