lkml.org 
[lkml]   [2008]   [Aug]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [malware-list] [RFC 0/5] [TALPA] Intro to alinuxinterfaceforon access scanning
    > This "permitted to execute" is what I feel is the wrong aproach with
    > respect to malware. If you simply allow everything to 'execute', I think
    > that untrusted programs may still be used for usefull things, but without
    > the potential do do malice. If you start from the point where everything
    > both trusted and untrusted is permitted to be executed, you could make it
    > the job of SELinux or any other LSM to make untrusted code run without
    > doing malice, but with the possibility to still run and do usefull non
    > malicious stuff. This might require some aditional hooks in LSM though I
    > could imagine.

    SELinux is quite happy to apply different rules to content labelled in
    different ways. WHat specific things do you need that it can't do ?


    \
     
     \ /
      Last update: 2008-08-15 16:39    [W:0.018 / U:0.400 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site