On Fri, Jun 15, 2007 at 10:06:23PM +0200, Pavel Machek wrote: > Yes, you may get some -EPERM during the tree move, but AA has that > problem already, see that "when madly moving trees we sometimes > construct path file never ever had". Pavel, please focus on the current AppArmor implementation. You're remembering a flaw with a previous version of AppArmor. The pathnames constructed with the current version of AppArmor are consistent and correct. Thanks.
Attachment:
pgptVaA4uK1ZH.pgp
Description: PGP signature
- Follow-Ups:
- References:
- [AppArmor 00/45] AppArmor security module overview
- From: [email protected]
- Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching
- From: Andreas Gruenbacher <[email protected]>
- Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching
- From: Greg KH <[email protected]>
- Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching
- From: Crispin Cowan <[email protected]>
- Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching
- From: Greg KH <[email protected]>
- Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching
- From: Pavel Machek <[email protected]>
- [AppArmor 00/45] AppArmor security module overview
- Prev by Date: Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching
- Next by Date: [BUG] Interesting race between cpufreq_ondemand and snd_atiixp
- Previous by thread: Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation,pathname matching
- Next by thread: Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching
- Index(es):
 |