sk-filter: Add ability to lock a socket filter program
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@luffy.cx> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
		
					parent
					
						
							
								5bd30d3987
							
						
					
				
			
			
				commit
				
					
						d59577b6ff
					
				
			
		
					 19 changed files with 53 additions and 2 deletions
				
			
		|  | @ -73,4 +73,6 @@ | |||
| /* Instruct lower device to use last 4-bytes of skb data as FCS */ | ||||
| #define SO_NOFCS		43 | ||||
| 
 | ||||
| #define SO_LOCK_FILTER		44 | ||||
| 
 | ||||
| #endif /* __ASM_GENERIC_SOCKET_H */ | ||||
|  |  | |||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue
	
	 Vincent Bernat
				Vincent Bernat