[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20130117.033334.409124726853704397.davem@davemloft.net>
Date: Thu, 17 Jan 2013 03:33:34 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: bernat@...fy.cx
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH net-next] sk-filter: Add ability to lock a socket
filter program
From: Vincent Bernat <bernat@...fy.cx>
Date: Wed, 16 Jan 2013 22:55:49 +0100
> While a privileged program can open a raw socket, attach some
> restrictive filter and drop its privileges (or send the socket to an
> unprivileged program through some Unix socket), the filter can still
> be removed or modified by the unprivileged program. This commit adds a
> socket option to lock the filter (SO_LOCK_FILTER) preventing any
> modification of a socket filter program.
>
> This is similar to OpenBSD BIOCLOCK ioctl on bpf sockets, except even
> root is not allowed change/drop the filter.
>
> The state of the lock can be read with getsockopt(). No error is
> triggered if the state is not changed. -EPERM is returned when a user
> tries to remove the lock or to change/remove the filter while the lock
> is active. The check is done directly in sk_attach_filter() and
> sk_detach_filter() and does not affect only setsockopt() syscall.
>
> Signed-off-by: Vincent Bernat <bernat@...fy.cx>
Looks good, applied, thanks Vincent.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists