Re: [apparmor] Question about defining a profile name via @{exec_path} variable

2019-01-09 Thread Mikhail Morfikov
On 10/01/2019 01:31, John Johansen wrote: > Well this is certainly allowed, and the python based tools should be able > to support it. Are you sure they weren't failing in the past? If so this > would be a regression. I have around 300 profiles, some of them are disabled because they're not finishe

Re: [apparmor] Question about defining a profile name via @{exec_path} variable

2019-01-09 Thread John Johansen
On 1/9/19 3:59 PM, Seth Arnold wrote: > On Wed, Jan 09, 2019 at 11:48:44PM +0100, Mikhail Morfikov wrote: >> @{exec_path} = /usr/bin/keepassxc >> profile keepassxc @{exec_path} { >> } > >> # aa-complain usr.bin.keepassxc >> ERROR: Profile for @{exec_path} exists in /etc/apparmor.d/some-app and >>

Re: [apparmor] Question about defining a profile name via @{exec_path} variable

2019-01-09 Thread Seth Arnold
On Wed, Jan 09, 2019 at 11:48:44PM +0100, Mikhail Morfikov wrote: > @{exec_path} = /usr/bin/keepassxc > profile keepassxc @{exec_path} { > } > # aa-complain usr.bin.keepassxc > ERROR: Profile for @{exec_path} exists in /etc/apparmor.d/some-app and > /etc/apparmor.d/some-other-app > Should this h

[apparmor] Question about defining a profile name via @{exec_path} variable

2019-01-09 Thread Mikhail Morfikov
For some time I've been using the following snipped to create new profiles: include @{exec_path} = /usr/bin/keepassxc profile keepassxc @{exec_path} { #include @{exec_path} mr, } The path of course changes as well as the profile name. Th