← Back to team overview

touch-packages team mailing list archive

[Bug 1466812] Re: aa-logprof crash

 

So it is possible that network, and other ipc types will show up under
the "file_perm" operation. Operation is just a hint for which kernel
code paths the permission request came from. Sockets certainly can be
used with regular filesystem operations.

With that said, something is very wrong here. There should be request
and deny masks.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1466812

Title:
  aa-logprof crash

Status in AppArmor Linux application security framework:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  aa-logprof crash after adding generic profile of apache2.
  Reading log entries from /var/log/syslog.
  Updating AppArmor profiles in /etc/apparmor.d.
  Traceback (most recent call last):
    File "/usr/sbin/aa-logprof", line 54, in <module>
      apparmor.do_logprof_pass(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2280, in do_logprof_pass
      log = log_reader.read_log(logmark)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 373, in read_log
      self.add_event_to_tree(event)
    File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 278, in add_event_to_tree
      rmask = rmask.replace('c', 'w')
  AttributeError: 'set' object has no attribute 'replace'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apparmor-utils 2.8.95~2430-0ubuntu5.2
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Fri Jun 19 12:37:54 2015
  InstallationDate: Installed on 2015-04-23 (56 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-3.16.0-30-generic root=/dev/mapper/system-root ro
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1466812/+subscriptions


References