From: Maciej Żenczykowski <redacted>
Date: Wed, 19 Oct 2011 21:31:06 -0700
quoted
A process with CAP_NET_RAW can spit whatever crap they want onto the
network, and receive all packets with impunity.
Agreed. But it can do so via raw sockets, it cannot do so via normal
udp/tcp/ip sockets.
That's why I'd like to relax the permissions check on being able to
switch a socket
into transparent mode. A process with CAP_NET_RAW can already pretty
much emulate
that behaviour by using raw sockets - it just can't do that using the
higher level, often more
usable/useful socket/protocol apis.
quoted
I can't see what this buys us at all, sorry.
See above.
Ok, I'm convinced, send me that patch without the warning messages.
Thanks.