Package: apparmor Version: 2.13.2-10 Severity: minor Dear Maintainer,
On an almost fresh Buster install: I did not gave sudo power for my user, so when i need to ckeck aa-status i open the terminal and put 'su root', but aa- status only work inside the root account when i put sudo aa-status. If im already the root on terminal, calls for sudo is really necessary? Thank you -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=pt_BR:pt:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages apparmor depends on: ii debconf [debconf-2.0] 1.5.71 ii libc6 2.28-10 ii lsb-base 10.2019051400 ii python3 3.7.3-1 apparmor recommends no packages. Versions of packages apparmor suggests: pn apparmor-profiles-extra <none> ii apparmor-utils 2.13.2-10 -- debconf information excluded
