On Wed, 28 Nov 2007 16:46:13 GMT, Christoph Hellwig said:Just to clarify - you're OK with the *concept* (a security model that determines whether you can do an I/O based on the content), it's just their code that's ugly? (Note that the concept has interesting implications in the other direction as well - rather than stopping you from reading a file that has malware, you could in theory write an anti-export package that would let you write onto external memory or outbound e-mail, but prevent the write if it was corporate-sensitive data, or whatever. Yes, I *know* a smart attacker can bypass it by simply crypting/compressing it first - but the vast majority of attackers aren't smart, and will just use 'cp' or the GUI equivalent to move the secret design documents onto the USB key... )
| Parag Warudkar | BUG: soft lockup - CPU#1 stuck for 15s! [swapper:0] |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Arjan van de Ven | Re: [GIT]: Networking |
| David Miller | Re: [BUG] New Kernel Bugs |
