Hi Marcel, On Tue, Dec 17, 2013, Marcel Holtmann wrote: > The HCI User Channel is an admin operation which enforces CAP_NET_ADMIN > when binding the socket. Problem now is that it then requires also > CAP_NET_RAW when calling into hci_sock_sendmsg. This is not intended > and just an oversight since general HCI sockets (which do not require > special permission to bind) and HCI User Channel share the same code > path here. > > Remove the extra CAP_NET_RAW check for HCI User Channel write operation > since the permission check has already been enforced when binding the > socket. This also makes it possible to open HCI User Channel from a > privileged process and then hand the file descriptor to an unprivilged > process. > > Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> > --- > net/bluetooth/hci_sock.c | 26 ++++++++++++++++---------- > 1 file changed, 16 insertions(+), 10 deletions(-) Applied to bluetooth.git. Thanks. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
