usr/bin/man profile in ...doc...extra dir. in apparmor-profiles package is almost empty

[dinar qurbanov]

Binary package hint: apparmor-profiles

usr/bin/man profile in ...doc...extra dir. in apparmor-profiles package is almost empty, so quite unusable, i think.

also in that extra directory paths to directories seems to be with old apparmor syntax, there is difference in trailing slash meaning, etc.

ProblemType: Bug
ApparmorStatusOutput:
 Error: command /usr/sbin/apparmor_status failed with exit code 4: You do not have enough privilege to read the profile set.
 apparmor module is loaded.
Architecture: i386
Date: Tue Jan 26 10:18:02 2010
Dependencies:

DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: apparmor-profiles 2.3.1+1403-0ubuntu27.2
ProcEnviron:
 LANG=tr_TR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
SourcePackage: apparmor
Uname: Linux 2.6.31-16-generic i686

[dinar qurbanov (qdinar)]

i reported this with ubuntu-bug apparmor-profiles, but here it is changed to apparmor, i too lately noticed it.

[Steve Beattie (sbeattie)]

Thanks for taking the time to report this. Sadly, no one has taken the time to update the man profile(s). The actual profile contents are contained in the usr.lib.man-db.man profile. It would be great if someone could take the time to develop and update these profiles.

The apparmor-profiles binary package is built from the apparmor source package, which is why the ubuntu-bug apparmor-profiles filed it that way.

[dinar qurbanov (qdinar)]

usr.bin.man :
i have tried to comment out "nameservice":
# #include <abstractions/nameservice>
because it allows to connect to internet, i have not used man so, and had not known that it is possible, seems it works...
and i added 5 rules.

(i do not know how to modify exactly header with license and suse copyright notice and names of who made the profile.)

[Colin Watson (cjwatson)]

Is it perhaps relevant that /usr/bin/man used to be a symlink to /usr/lib/man-db/man for historical reasons, but since man-db 2.5.6-1 the symlink has been the other way round?

man does not currently need to connect to the Internet for anything, although there is an outstanding feature request (bug 270984) which would involve it doing so.