Writing updated profile for /usr/bin/konversation.
Setting /usr/bin/konversation to complain mode.

Before you begin, you may wish to check if a
profile already exists for the application you
wish to confine. See the following wiki page for
more information:
http://wiki.apparmor.net/index.php/Profiles

Please start the application to be profiled in
another window and exercise its functionality now.

Once completed, select the "Scan" option below in 
order to scan the system logs for AppArmor events. 

For each AppArmor event, you will be given the 
opportunity to choose whether the access should be 
allowed or denied.

Profiling: /usr/bin/konversation

[(S)can system log for AppArmor events] / (F)inish
Reading log entries from /var/log/syslog.
Updating AppArmor profiles in /etc/apparmor.d.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 402, in 
read_log
    self.add_event_to_tree(event)
  File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 206, in 
add_event_to_tree
    e = self.parse_event_for_tree(e)
  File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 303, in 
parse_event_for_tree
    raise AppArmorException(_('Log contains unknown mode %s') % rmask)
apparmor.common.AppArmorException: 'Log contains unknown mode senw'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/sbin/aa-genprof", line 151, in <module>
    lp_ret = apparmor.do_logprof_pass(logmark, passno)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2189, in 
do_logprof_pass
    log = log_reader.read_log(logmark)
  File "/usr/lib/python3/dist-packages/apparmor/logparser.py", line 407, in 
read_log
    raise AppArmorBug(ex_msg)  # py3-only: from None
apparmor.common.AppArmorBug: Log contains unknown mode senw

This error was caused by the log line:
Jul  6 12:31:45 kernel: [ 1585.343460] audit: type=1400 
audit(1467822705.150:668): apparmor="ALLOWED" operation="file_perm" 
profile="/usr/bin/konversation" pid=6877 comm="konversation" 
laddr=xxx.xxx.xxx.xxx lport=58236 faddr=164.132.77.237 fport=6697 family="inet" 
sock_type="stream" protocol=6 requested_mask="send" denied_mask="send"

-- 
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/1399027

Title:
  logparser doesn't understand /var/log/messages format

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  [impact]

  This bug causes tools that use libapparmor to parse syslog and other
  logs for apparmor rejections to fail to recognize apparmor events.

  [steps to reproduce]

  [regression potential]

  The patch for this issue is confined to the log parsing portion of
  the libapparmor library. Breakages occurring here would most likely
  prevent tools that help assist the management of apparmor policy
  from working; apparmor mediation would not be impacted. libapparmor
  does provide other functionality, mostly around the aa_change_hat(3)
  and aa_change_profile(3) calls; an entirely broken library could cause
  issues for applications that make use of these from working correctly;
  however, there are tests available in the upstream package that get
  invoked by the lp:qa-regression-testing test-apparmor.py script that
  ensure these continue to function.

  [original description]
   
  log parsing (part of libapparmor, used by aa-logprof and aa-genprof) doesn't 
understand the format in /var/log/messages, which means it doesn't find any 
events in it.

  IIRC I've seen a similar report for the ubuntu syslog format on IRC.

  Example log line from openSUSE:

  2014-06-09T20:37:28.975070+02:00 geeko kernel: [21028.143765]
  type=1400 audit(1402339048.973:1421): apparmor="ALLOWED"
  operation="open" profile="/home/cb/linuxtag/apparmor/scripts/hello"
  name="/dev/tty" pid=14335 comm="hello" requested_mask="rw"
  denied_mask="rw" fsuid=1000 ouid=0

  (Workaround: use auditd / audit.log)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to