On 2014-04-03 16:41, James Knott wrote:
Carlos E. R. wrote:
Did you try aa-logprof yet?
Complain will fill your logs.
I get this response:
Reading log entries from /var/log/messages. Updating AppArmor profiles in /etc/apparmor.d.
Profile: /usr/sbin/dovecot Execute: /usr/bin/doveconf Severity: unknown
(I)nherit / (P)rofile / (C)hild / (N)ame / (U)nconfined / (X)ix / (D)eny / Abo(r)t / (F)inish ... So, what am I supposed to do? Why should this even be necessary?
Well, that is what you have to do to correct *your* apparmour installation. I don't know what all the above means, the "man" is close to unreadable, as typical (you noticed). According to the manual, the options are: (A)llow, (D)eny, (N)ew, (G)lob last piece, (Q)uit no more... So you have to make guesses. I take "Inherit" to be a variant of "Allow", so sometimes I use that, or "Allow". In this case it is asking if running "doveconf" should be allowed, and understand it should. Just work with the options in the manual, ignore the rest. When there is an update to AA, your modifications are lost, so it is of no consequence if you could create yourself a better profile by making use of the non-documented options. Let the developers use them. Sigh... -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)