Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1425221
| From | Daniel Micay <danielmicay@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [kernel-hardening] Re: [PATCH 2/2] security,perf: Allow further restriction of perf_event_open |
| Date | 2016-06-17 17:30 +0200 |
| Message-ID | <rL3Sx-8fe-17@gated-at.bofh.it> (permalink) |
| References | <qPMzU-4ae-19@gated-at.bofh.it> <qPMzU-4ae-17@gated-at.bofh.it> <rKUYV-2vY-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
> As a debian user, is this a good place to complain? Because it does > get > it the way. It would be relevant to whether or not it should be set to 3 by default in the kernel without explicit configuration, but there's no proposal to do that. Debian has to pick a trade-off beyond security and a tiny roadblock for developers. It's not always the case though. In Android, there's userspace integration allowing it to be toggled by the Android Debugging Bridge shell user so profiling tools are being taught to automatically toggle it. Enabling ADB and then using it for profiling is an implicit opt-in.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH 2/2] security,perf: Allow further restriction of perf_event_open Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-06-17 08:00 +0200 Re: [PATCH 2/2] security,perf: Allow further restriction of perf_event_open Ben Hutchings <ben@decadent.org.uk> - 2016-06-17 14:20 +0200 Re: [kernel-hardening] Re: [PATCH 2/2] security,perf: Allow further restriction of perf_event_open Daniel Micay <danielmicay@gmail.com> - 2016-06-17 17:30 +0200
csiph-web