20150413

Differences between revisions 37 and 40 (spanning 3 versions)
⇤ ← Revision 37 as of 2015-04-06 15:37:31 →
Size: 3167
Editor: tyhicks
Comment:
← Revision 40 as of 2015-04-13 16:20:48 → ⇥
Size: 3157
Editor: tyhicks
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was copied from MeetingLogs/Security/20150406
Line 3: Line 4:
== Meeting (DRAFT) == == Meeting ==
Line 5: Line 6:
 * '''When''': Mon Apr 6th 2015 16:30 UTC  * '''When''': Mon Apr 6th 2015 16:45 UTC
Line 24: Line 25:
 * Weekly stand-up report (each member discusses any pending and planned future work for the week)
Line 25: Line 27:
   {{{#!wiki comment
   * Review mvo's framework policies branch for snappy
   * Review tools updates
   * Review mvo's seccomp launcher branch
   * Prepare snappy seccomp policy
   * Embargoed item
   }}}		    * Write review tool tests for new snappy security yaml
   * Finish landing the snappy framework policy changes
   * Write review tool tests for new snappy hashes.yaml
   * Continue working on snappy seccomp policy
Line 41: Line 40:
   {{{#!wiki comment
Line 43: Line 41:
   * Prepare for Trusty SRU of AppArmor python utils
Line 44: Line 43:
   }}}
Line 47: Line 45:
   * systemd/sbuild/schroot/kernel bugs (LP: #1427264) (LP: #1438942) (LP: #1439849)    * Vivid systemd/sbuild/schroot/kernel bugs (LP: #1427264) (LP: #1438942) (LP: #1439849)
Line 52: Line 50:
   {{{#!wiki comment
   * Make final fixups for libapparmor policy cache API changes
   * Review the initial snappy launcher code
   }}}
Line 67: Line 61:
    {{{#!wiki comment
Line 70: Line 63:
    * SRU fix testing
    }}}
Line 85: Line 76:
Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-03-30-16.32.moin.txt Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-04-06-16.45.moin.txt

Meeting

  • Who: SecurityTeam

  • When: Mon Apr 6th 2015 16:45 UTC

  • End: 17:00 UTC

  • Where: #ubuntu-meeting on irc.freenode.net

  • Chaired By: Tyler Hicks (tyhicks)

Attendance

  • jdstrand
  • sbeattie
  • tyhicks
  • sarnold

Not present

  • mdeslaur
  • jjohansen
  • chrisccoulson

Agenda

  • Announcements
    • Johan Van de Wauw (johanvdw) provided debdiffs for trusty-vivid for postgis (LP: #1438875)
  • Weekly stand-up report (each member discusses any pending and planned future work for the week)
    • jdstrand
      • Write review tool tests for new snappy security yaml
      • Finish landing the snappy framework policy changes
      • Write review tool tests for new snappy hashes.yaml
      • Continue working on snappy seccomp policy
    • sbeattie
      • weekly role: community

      • AppArmor patch review

      • Prepare for Trusty SRU of AppArmor python utils

      • Continue testing of gcc-5 pie-on-amd64 packages
    • tyhicks
      • weekly role: bug triage
      • Vivid systemd/sbuild/schroot/kernel bugs (LP: #1427264) (LP: #1438942) (LP: #1439849)

      • Restart work on AppArmor kernel keyring mediation for user data encryption

      • Finish up the patches to fix bug #1430532 and send them out for review
      • python-cryptography MIR (LP: #1430082)
        • sarnold may do the MIR
    • sarnold
      • weekly role: cve triage

      • OpenStack security updates

      • Outstanding MIR requests
  • Highlighted packages

    The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so. See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved. The highlighted packages for this week are:

    The Ubuntu Security team suggests that contributors look into merging Debian security updates in community-supported packages. If you would like to help Ubuntu but are not sure where to start, this is a great way to do so. See the available merges and SecurityTeam/UpdateProcedures for details on preparing Ubuntu security updates. If you have any questions, feel free to ask in #ubuntu-hardened. To find out other ways of helping out, please see SecurityTeam/GettingInvolved.

  • Miscellaneous and Questions

Log

Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-04-06-16.45.moin.txt

MeetingLogs/Security/20150413 (last edited 2015-04-13 17:00:58 by tyhicks)