I'd have guessed that the default paranoia-first policy would be "drop everything; verify what you need" which would include AF_ALG.
share and enjoy!
I'd have guessed that the default paranoia-first policy would be "drop everything; verify what you need" which would include AF_ALG.
share and enjoy!
How do you propose to implement that "drop everything except what you need" policy? Do your containers come with a detailed list of which OS services and syscalls are required? Your proposal has the same issue as what held back the adoption of selinux: many developers think that having to enumerate their application's behaviour like that is an undue burden.
A compounding issue is that using AF_ALG doesn't require a separate syscall: it's just using SYS_socket with the first argument set to 38. Your container behaviour specification needs to be specific enough to not only enumerate allowed syscalls, but the allowed values for each syscall parameter.