> I submit that the AppArmor model is valid, even if it totally failed allThe model looks valid. I have difficulty constructing many scenarios where its useful but it appears valid providing you can tightly control file renaming, which is very very questionable. There are also some very awkward path based issues around shared file objects (your controlling tty and TIOCSTI for one) that I need to look at the code for once the VFS stuff is sorted and its likely to get merged. Alan -
| 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 |
| Tarkan Erimer | Re: Slow DOWN, please!!! |
git: | |
| Kevin Ballard | Re: git on MacOSX and files with decomposed utf-8 file names |
| Jakub Narebski | Re: VCS comparison table |
| David | User's mailing list? And multiple cherry pick |
| Ken Pratt | pack operation is thrashing my server |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Jiri Olsa | [PATCH] net: fix race in the receive/select |
| Jarek Poplawski | [PATCH take 2] pkt_sched: Protect gen estimators under est_lock. |
| Rick Jones | Re: RFC: Nagle latency tuning |
| Richard Stallman | Real men don't attack straw men |
| list-obsd-misc | Re: low-MHz server |
| Luca Corti | Re: About Xen: maybe a reiterative question but .. |
| Jerome Santos | sshd.config and AllowUsers |
