RFC netlink check sender
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 patches 17 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | netlink check senderinclude/ net/ | +22 | 4 replies | |
| 2/3 | netlink check sender, auditkernel/ | +16 | 13 replies | |
| 3/3 | netlink check sender, rtnetlinknet/ | +27 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC][PATCH 0/3] netlink check sender
The following patches are for comment. They introduce a new callback to enable netlink messages to be validated in the sender's context, and then convert a couple kernel netlink receivers to use this callback. This eliminates the need to copy the sender's effective capabilities into the netlink control buffer. It also allows the audit system to manage the loginuid in the kernel without adding more fields to netlink_skb_parms or requiring special case netlink code. I think this would obsolete the security_netlink_recv hook, and simplify the security_netlink_send hook.
Currently I've only hooked the unicast messages, because I didn't think any of the kernel netlink input functions would be processing broadcast messages (perhaps I missed something).
I didn't move the logic that simply ignores messages (e.g. type < RTM_BASE), but I did move the logic that looks for invalid messages (e.g. type > RTM_MAX) to the check_sender callback.
Thoughts?
thanks,
-chris
Signature · 1 line
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net