Parsing non-sendable cmsg in SendMsg syscall should fail
arthurpi opened this issue · comments
Description
Some control messages can't be sent (only received). For example, IP_RECVERR or IP_RECVORIGDSTADDR.
In the syscall implementation of SendMsg in sentry, we call control.Parse on the raw cmsg bytes. This function should refuse non-sendable control messages.
Steps to reproduce
No response
runsc version
No response
docker version (if using docker)
No response
uname
No response
kubectl (if using Kubernetes)
No response
repo state (if built from source)
No response
runsc debug logs (if available)
No response
Hey, @arthurpi can I pick this issue. And can you give me some hints on where to start looking for making this change?
A friendly reminder that this issue had no activity for 120 days.