fanotify as syscalls
in [Kernel]
|
Prev: BUG kmalloc-64: Poison overwritten, INFO: Allocated in bdi_alloc_work+0x2b/0x100 age=175 cpu=1 pid=3514
Next: [PATCH 62/72] Blackfin: bf537-stamp: add adp5588 gpio resources
From: hch on 23 Sep 2009 18:00 On Wed, Sep 23, 2009 at 11:51:37AM -0400, Eric Paris wrote: > And users would be left in a situation between choosing an LSM which > actually does in provable ways increase security and using an AV > scanner. Sounds like a good thing, no? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: hch on 23 Sep 2009 18:00
On Wed, Sep 23, 2009 at 08:35:18AM -0700, Davide Libenzi wrote: > The fear is that this becomes a trojan horse (no pun intended) for more > and more hooks and "stuff", driven by we-really-need-this-too and > we-really-need-that-too. And once something it's in, it's harder to say no, > under the pressure of offering a "limited solution". > This ws the reason I threw the syscall tracing thing in, so they have a > low level generic hook, and they cam knock themselves out in their module > (might need a few exports, but that's about it). Replacing idiotify with a saner interface is a good goal. I just don't think we should take the stakes of the snake oil industry too serious in it. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |