Bug#1003158: [pkg-apparmor] Bug#1003158: apparmor: tunables/home seems to have wrong order of variables

2022-01-06 Thread Seth Arnold
On Thu, Jan 06, 2022 at 08:38:32PM +0100, Christian Boltz wrote: > Am Mittwoch, 5. Januar 2022, 23:09:01 CET schrieb Karsten Hilbert: > > Unless I misunderstand apparmor profile logic it is not > > purely cosmetic. It excludes "/home/*/" from @{HOME}. > > That's the difference between a human

Bug#1003158: [pkg-apparmor] Bug#1003158: apparmor: tunables/home seems to have wrong order of variables

2022-01-06 Thread Christian Boltz
Hello, Am Mittwoch, 5. Januar 2022, 23:09:01 CET schrieb Karsten Hilbert: > Unless I misunderstand apparmor profile logic it is not > purely cosmetic. It excludes "/home/*/" from @{HOME}. That's the difference between a human parser (you) and apparmor_parser ;-) - you think of the profile as

Bug#1003158: [pkg-apparmor] Bug#1003158: apparmor: tunables/home seems to have wrong order of variables

2022-01-05 Thread Karsten Hilbert
Am Wed, Jan 05, 2022 at 09:13:12PM +0100 schrieb Christian Boltz: > AppArmor rules are in most cases declarative so that the order doesn't > matter (exception: before you can extend a variable with "+=" you have > to initialize it with "="). > > The current definition is technically not a bug,

Bug#1003158: [pkg-apparmor] Bug#1003158: apparmor: tunables/home seems to have wrong order of variables

2022-01-05 Thread Christian Boltz
Hello, AppArmor rules are in most cases declarative so that the order doesn't matter (exception: before you can extend a variable with "+=" you have to initialize it with "="). The current definition is technically not a bug, "just" confusing. However, I agree that defining @{HOMEDIRS} before