[lkml]   [2011]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRE: [PATCH] Smack: Use secureexec with SMACK64EXEC
> -----Original Message-----
> bprm->unsafe isn't private to your security module, unlike e.g.
> bprm->cred->security. And it isn't intended to indicate that a
> secureexec is being performed, but instead as an indicator that a
> credential-changing exec may be unsafe. Which you presently ignore.
> Defining and setting a new flag in it will have interesting side effects,
> e.g. consider cap_bprm_secureexec, not to mention being a layering
> violation and a source of future conflicts.
> Why can't your bprm_secureexec hook just test isp->smk_task directly?
> It can reach it from the bprm. Or if you don't like testing it twice,
> then you could always add a flag to your struct referenced by
> bprm->cred->security, i.e. the smack_task struct.
> BTW, there is a lot more to do if you want SMACK64EXEC to be safe.

Thanks for the feedback Stephen. Could you be more detailed on what else you feel needs to be in place to make SMACK64EXEC safe?


 \ /
  Last update: 2011-09-22 05:37    [W:0.062 / U:3.156 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site