desktop-packages team mailing list archive

[Mathew Hodson <mathew.hodson@xxxxxxxxx>]

** Changed in: openssh (Ubuntu)
   Importance: Undecided => Medium

** Changed in: shadow (Ubuntu)
   Importance: Undecided => Medium

** Changed in: openssh (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: openssh (Ubuntu Vivid)
   Importance: Undecided => Low

** Changed in: openssh (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: shadow (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: shadow (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: shadow (Ubuntu Vivid)
   Importance: Undecided => Low

** Also affects: openssh (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797727
   Importance: Unknown
       Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1478087

Title:
  Add libaudit support

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Committed
Status in Light Display Manager 1.14 series:
  Fix Released
Status in Light Display Manager 1.16 series:
  Fix Released
Status in Light Display Manager 1.2 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Triaged
Status in openssh source package in Trusty:
  Fix Committed
Status in shadow source package in Trusty:
  Fix Committed
Status in lightdm source package in Vivid:
  Triaged
Status in openssh source package in Vivid:
  Triaged
Status in shadow source package in Vivid:
  Triaged
Status in lightdm source package in Wily:
  Fix Released
Status in openssh source package in Wily:
  Fix Released
Status in shadow source package in Wily:
  Fix Released
Status in openssh package in Debian:
  Unknown

Bug description:
  [Impact]
  Auditing support is a commonly used feature in large enterprises, and allows better tracking of actions happening on secured systems, especially when it comes to accounting for login events.

  Such systems fail to correctly list login events in aureport due to
  some software not integrating libaudit.

  [Test Case]
  1) Install auditd
  2) Login to the system multiple times (or allow for others to connect to the system)
  3) Run aureport -l

  System should list login information.

  [Regression Potential]
  There is minimal risk for issues since libaudit support only allows for generating extra logging saved on the local system. A possible side-effect of this may be that systems on which auditing is enabled and where there are many users of the affected software (see bug tasks), such as many logins over SSH, there may be an increased demand on disk space necessary for the auditing data.

  ---

  -- Problem Description --
  We installed ubuntu 14.04.3 on lakelp1 and installed package auditd. We tried to
  ssh to lakelp1 several times and found that "aureport -l" couldn't print out the login
  info.

  root@lakelp1:~# /etc/init.d/auditd status
   * auditd is running.

  root@lakelp1:~# auditctl -e 1
  AUDIT_STATUS: enabled=1 flag=1 pid=38784 rate_limit=0 backlog_limit=320 lost=12 backlog=1

  root@lakelp1:~# grep -i login /var/log/audit/audit.log
  type=LOGIN msg=audit(1437641256.987:67): pid=11752 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=4 res=1
  type=LOGIN msg=audit(1437642646.478:85): pid=44269 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=5 res=1
  type=LOGIN msg=audit(1437642700.295:90): pid=21504 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=6 res=1
  type=LOGIN msg=audit(1437642765.339:104): pid=16628 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=7 res=1
  type=LOGIN msg=audit(1437644638.593:130): pid=44443 uid=0 old-auid=4294967295 auid=0 old-ses=4294967295 ses=8 res=1

  root@lakelp1:~# aureport -l

  Login Report
  ============================================
  # date time auid host term exe success event
  ============================================
  <no events of interest were found>

  This looks like a bug in aureport or libaudit. In addition to giving
  admins falsely empty record selections, this would prevent successful
  completion of a Common Criteria certification.

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