[lkml]   [2018]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH v3 1/3] ptrace: Provide ___ptrace_may_access() that can be applied on arbitrary tasks
On Tue, 4 Sep 2018, Tim Chen wrote:

> > Current ptrace_may_access() implementation assumes that the 'source' task is
> > always the caller (current).
> >
> > Expose ___ptrace_may_access() that can be used to apply the check on arbitrary
> > tasks.
> Casey recently has proposed putting the decision making of whether to
> do IBPB in the security module.
> That will have the advantage of giving the administrator a more flexibility
> of when to turn on IBPB. The policy is very similar to what you have proposed here
> but I think the security module is a more appropriate place for the security policy.

Yeah, well, honestly, I have a bit hard time buying the "generic
sidechannel prevention security module" idea, given how completely
different in nature all the mitigations have been so far. I don't see that
trying to abstract this somehow provides more clarity.

So if this should be done in LSM, it'd probably have to be written by
someone else than me :) who actually understands how the "sidechannel LSM"
idea works.


Jiri Kosina

 \ /
  Last update: 2018-09-04 19:36    [W:0.118 / U:28.168 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site