Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #227869
| From | Tixy <tixy@yxit.co.uk> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Stretch => Buster: AppArmor |
| Date | 2020-10-16 16:40 +0200 |
| Message-ID | <B0z3I-6sr-3@gated-at.bofh.it> (permalink) |
| References | <B0v9L-4bV-5@gated-at.bofh.it> <B0vjr-4f4-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, 2020-10-16 at 13:30 +0300, Reco wrote: > > On Fri, Oct 16, 2020 at 12:23:30PM +0200, Jesper Dybdal wrote: [...] > > 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. Or do what I did, just uninstall the apparmor package which is pulled in as a 'recommends' of the Linux kernel. Or pin it to priority -1 for extra paranoia. -- Tixy
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