On 2017.10.03 02:17, Christian Boltz wrote:
I guess I could create bug / feature request against apparmor_parser,
about emitting warning when `Pux` is used in profile.
Yes, please do.
Done.
https://bugs.launchpad.net/apparmor/+bug/1721071
--
AppArmor mailing list
AppArmor@lists.ubuntu.com
Hello,
Am Montag, 2. Oktober 2017, 17:17:53 CEST schrieb Vincas Dargis:
> On 2017.10.02 02:19, John Johansen wrote:
> > I believe it was a deliberate decision by the author to not support
> > the confusing syntax of mixed characters.
Right, that's an (intended) side effect of rewriting the file
On 2017.10.02 02:19, John Johansen wrote:
I believe it was a deliberate decision by the author to not support
the confusing syntax of mixed characters. The parser's support is much
older and has not been patched to conform with the above mentioned
decision, ideally it should be reporting that the
On 10/01/2017 08:42 AM, Vincas Dargis wrote:
> Hi,
>
> I have reported bug [0] that `usr.bin.totem` containing `Pux` rule produces
> `aa-logprof` error:
>
> ```
> ERROR: permission contains unknown character(s) Pux
> ```
>
> Though `apparmor_parser` itself does not emit any errors or warnings.
Hi,
I have reported bug [0] that `usr.bin.totem` containing `Pux` rule produces
`aa-logprof` error:
```
ERROR: permission contains unknown character(s) Pux
```
Though `apparmor_parser` itself does not emit any errors or warnings.
I can't find `Pux` in `man apparmor.d`, though it's mentioned i
