Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #227855
| From | Reco <recoverym4n@enotuniq.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Stretch => Buster: AppArmor |
| Date | 2020-10-16 12:40 +0200 |
| Message-ID | <B0vjr-4f4-9@gated-at.bofh.it> (permalink) |
| References | <B0v9L-4bV-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi. On Fri, Oct 16, 2020 at 12:23:30PM +0200, Jesper Dybdal wrote: > Buster enables AppArmor by default. I know just about nothing at all > about AppArmor. Does it constitute a risk that some of my existing > programs will not work? Depends. AppArmor is applied per-binary. If you're using something that ships an AppArmor policy - it will be enabled. > For instance, my postfix installation (which is by far the most > important application I run) uses a few non-standard tcp ports to > comunicate with helper services and to receive mail submissions - is > there a risk that AppArmor will block that? No, because there's no shipped AppArmor policy for postfix in buster. > Is there a simple way to disable AppArmor completely until I've had > time to figure out what to do with it long-term? Adding "apparmor=0" to your kernel cmdline should do the trick. Reco
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Stretch => Buster: AppArmor Jesper Dybdal <jd-debian-user@dybdal.dk> - 2020-10-16 12:30 +0200
Re: Stretch => Buster: AppArmor Reco <recoverym4n@enotuniq.net> - 2020-10-16 12:40 +0200
Re: Stretch => Buster: AppArmor Tixy <tixy@yxit.co.uk> - 2020-10-16 16:40 +0200
Re: Stretch => Buster: AppArmor Jesper Dybdal <jd-debian-user@dybdal.dk> - 2020-10-16 17:00 +0200
Re: Stretch => Buster: AppArmor Tixy <tixy@yxit.co.uk> - 2020-10-16 17:20 +0200
Re: Stretch => Buster: AppArmor Reco <recoverym4n@enotuniq.net> - 2020-10-16 17:00 +0200
Re: Stretch => Buster: AppArmor l0f4r0@tuta.io - 2020-10-16 20:20 +0200
csiph-web