linux-kernel - Re: [PATCH] capabilities/syslog: open code cap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101118142624.GA927@hallyn.com>
Date:	Thu, 18 Nov 2010 08:26:24 -0600
From:	"Serge E. Hallyn" <serge.hallyn@...onical.com>
To:	Eric Paris <eparis@...hat.com>
Cc:	linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org,
	torvalds@...ux-foundation.org, joe@...ches.com,
	drosenberg@...curity.com, mingo@...e.hu, eugeneteo@...nel.org,
	kees.cook@...onical.com, akpm@...ux-foundation.org,
	jmorris@...ei.org, morgan@...nel.org, casey@...aufler-ca.com
Subject: Re: [PATCH] capabilities/syslog: open code cap_syslog logic to fix
 build failure

Quoting Eric Paris (eparis@...hat.com):
> @@ -274,7 +274,20 @@ int do_syslog(int type, char __user *buf, int len, bool from_file)
>  	char c;
>  	int error = 0;
>  
> -	error = security_syslog(type, from_file);
> +	/*
> +	 * If this is from /proc/kmsg we only do the capabilities checks
> +	 * at open time.
> +	 */
> +	if (type == SYSLOG_ACTION_OPEN || !from_file) {
> +		if (dmesg_restrict && !capable(CAP_SYS_ADMIN))

Any chance we could introduce a new capability for this?

thanks,
-serge
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/