20160222

Differences between revisions 34 and 35
⇤ ← Revision 34 as of 2016-01-11 16:15:52 →
Size: 2645
Editor: tyhicks
Comment:
← Revision 35 as of 2016-01-11 16:56:17 → ⇥
Size: 2674
Editor: tyhicks
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
== Meeting (DRAFT) == == Meeting ==
Line 4: Line 4:
 * '''When''': Mon Jan 4th 2016 16:39 UTC
 * '''End''': 16:55 UTC		  * '''When''': Mon Jan 11th 2016 16:35 UTC
 * '''End''': 16:53 UTC
Line 14: Line 14:
 * jjohansen
Line 19: Line 18:
 * None  * jjohansen
Line 26: Line 25:
   * catch up email/IRC from last week while attending the Snappy sprint
   * fix seccomp denial that Mir on Snappy is seeing
    * update libseccomp for mbarrier syscall
    * allow mbarrier in ubuntu-core-security
   * followups from the Snappy sprint (put work into Trello)
   * start work to support Snappy capabilities
    * ubuntu-core-security and review tools		    * work with zyga on snappy capabilities
   * review existing snappy frameworks as they pertain to the capabilities work
   * two embargoed issues
Line 34: Line 29:
   * weekly role: bug triage
   * libvirt updates
   * embargoed update
  * sbeattie
Line 35: Line 34:
   * samba updates
   * other pending updates in need of testing
  * sbeattie		    * embargoed issue
   * gcc-pie churn
    * review test failures from doko's test pie build
    * finish work to fix the kernel build to disable pie
   * upstream !AppArmor patch review
   * QRT test failures for s390x
  * tyhicks
Line 40: Line 43:
   * gcc-pie churn
   * upstream !AppArmor work
  * tyhicks
   * weekly role: community
   * catch up on email from the holidays
   * assist with !AppArmor stacking development		    * !AppArmor stacking
    * drive the AppArmor stacking interface designs in libapparmor and securityfs
    * create easy to use namespace creation APIs and binutils
Line 47: Line 47:
  {{{#!wiki comment
Line 51: Line 52:
  }}}
Line 52: Line 54:
   * weekly role: bug triage
   * email catch up		    * weekly role: community
Line 55: Line 56:
  * ChrisCoulson
   * email catch up		    * pick up another MIR
  * !ChrisCoulson
Line 58: Line 59:
   * Chromium updates
   * Oxide updates
   * Oxide reviews		    * Oxide 1.13 [[https://launchpad.net/oxide/+milestone/branch-1.13|milestones]]
Line 68: Line 67:
Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-01-04-16.39.moin.txt Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-01-11-16.35.moin.txt

Meeting

  • Who: SecurityTeam

  • When: Mon Jan 11th 2016 16:35 UTC

  • End: 16:53 UTC

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

  • Chaired By: Tyler Hicks (tyhicks)

Attendance

  • jdstrand
  • mdeslaur
  • sbeattie
  • tyhicks
  • sarnold
  • chrisccoulson

Not present

  • jjohansen

Agenda

  • Announcements
    • Andreas Cadhalpun provided a debdiff for wily for ffmpeg (LP: #1528682)
  • Weekly stand-up report (each member discusses any pending and planned future work for the week)
    • jdstrand
      • work with zyga on snappy capabilities
      • review existing snappy frameworks as they pertain to the capabilities work
      • two embargoed issues
    • mdeslaur
      • weekly role: bug triage
      • libvirt updates
      • embargoed update
    • sbeattie
      • weekly role: cve triage
      • embargoed issue
      • gcc-pie churn
        • review test failures from doko's test pie build
        • finish work to fix the kernel build to disable pie

      • upstream AppArmor patch review

      • QRT test failures for s390x
    • tyhicks
      • weekly role: happy place
      • embargoed issue

      • AppArmor stacking

        • drive the AppArmor stacking interface designs in libapparmor and securityfs

        • create easy to use namespace creation APIs and binutils
      • investigate if rngd can be used in Snappy on the Beagle Bone Black to seed /dev/random
    • sarnold
      • weekly role: community
      • DPDK MIR
      • pick up another MIR

    • ChrisCoulson

  • 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
    • None

Log

Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-01-11-16.35.moin.txt

MeetingLogs/Security/20160222 (last edited 2016-02-22 16:55:16 by tyhicks)