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] [day] [month] [year] [list]
Date:	Wed, 18 Feb 2009 16:51:11 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Paul Mackerras <paulus@...ba.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perfcounters: allow sysadmin to restrict non-root
	counting of kernel events


* Peter Zijlstra <peterz@...radead.org> wrote:

> On Wed, 2009-02-18 at 21:26 +1100, Paul Mackerras wrote:
> > Impact: security feature
> > 
> > This allows the sysadmin to prevent non-root users from counting
> > hardware events that occur in kernel or hypervisor mode via a sysfs file:
> > 
> > 	/sys/devices/system/cpu/perf_counters/restrict_kernel_events
> > 
> > This defaults to off (0), allowing users to count kernel and hypervisor
> > events, but if the sysadmin writes 1 to that file, any new counters
> > created by non-root users will automatically be set to ignore kernel
> > and hypervisor events.
> > 
> > This could be useful if there is a concern that allowing non-root users
> > to count kernel or hypervisor events might leak sensitive information.
> 
> I would expect it the other way around, don't allow users 
> access to kernel/hv events unless explicitly granted.

i think it's useful to make userspace developers aware of the 
kernel overhead they are causing - while still allowing policy 
settings to override that default.

Maybe the name of the control should be switched around, to 
allow_kernel_events? [with the same functional end result though 
- i.e. default-enabled]

	Ingo
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ