Control: tag -1 + fixed-upstream
intrigeri (2018-12-16):
> Julian Andres Klode:
>> It needs some more changes, I'll try to get them fixed up
>> this weekend, so I can roll out my server in enforced mode.
>
> Did your https://gitlab.com/apparmor/apparmor/merge_requests/284 fix
> all the incorrect
Hi,
Julian Andres Klode:
> It needs some more changes, I'll try to get them fixed up
> this weekend, so I can roll out my server in enforced mode.
Did your https://gitlab.com/apparmor/apparmor/merge_requests/284 fix
all the incorrect paths this bug was about?
(I'd like to update this bug's
Julian Andres Klode:
> It needs some more changes, I'll try to get them fixed up
> this weekend, so I can roll out my server in enforced mode.
> It will be based on Ubuntu 18.04, though, so might need double
> checking.
Great!
On Mon, Jan 29, 2018 at 12:03:02PM +0100, intrigeri wrote:
> Hi,
>
> the preferred way to fix this nowadays is to fork
> https://gitlab.com/apparmor/apparmor, edit files in
> profiles/apparmor/profiles/extras, commit, push a branch and follow
> the instructions that `git push' will provide to
Hi,
the preferred way to fix this nowadays is to fork
https://gitlab.com/apparmor/apparmor, edit files in
profiles/apparmor/profiles/extras, commit, push a branch and follow
the instructions that `git push' will provide to submit
a merge request.
I guess that replacing all relevant occurrences
Control: severity -1 minor
Control: tag -1 + upstream
Control: found -1 2.11.0-6
Hi,
debian-b...@vorpal.se:
> After upgrading from jessie to stretch I noticed that postfix was no
> longer constrained by apparmor profiles (using aa-unconfined, ps
> auxZ etc).
> The cause of this issue seems to
Package: apparmor-profiles
Version: 2.11.0-3
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
After upgrading from jessie to stretch I noticed that postfix was no longer
constrained by apparmor profiles (using aa-unconfined, ps
7 matches
Mail list logo
