20160321

Differences between revisions 37 and 57 (spanning 20 versions)
⇤ ← Revision 37 as of 2016-01-25 16:29:40 →
Size: 2688
Editor: tyhicks
Comment:
← Revision 57 as of 2016-03-21 15:58:58 → ⇥
Size: 2503
Editor: tyhicks
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was copied from MeetingLogs/Security/20160111 ## page was copied from MeetingLogs/Security/20160314
Line 4: Line 4:
 * '''When''': Mon Jan 25th 2016 16:35 UTC  * '''When''': Mon Mar 21st 2016 16:30 UTC
Line 12: Line 12:
 * sbeattie
Line 14: Line 13:
 * jjohansen
Line 16: Line 14:
 * chrisccoulson  * !ChrisCoulson
Line 19: Line 17:
 * None  * jjohansen
 * sbeattie
Line 23: Line 22:
  * Felix Geyer (debfx) provided debdiffs for trusty, wily for prosody (LP: #1532943)
  * Andreas Cadhalpun (andreas-cadhalpun) provided debdiffs for vivid and wily for ffmpeg (LP: #1533367) 		  * None
Line 27: Line 25:
   * work with zyga on snappy capabilities
   * review existing snappy frameworks as they pertain to the capabilities work		    * continue snappy interfaces work
   * start looking into snappy developer mode
Line 32: Line 30:
   * libvirt updates
   * embargoed update		    * patch piloting
   * graphite2 updates
   * exim2 updates
  {{{#!wiki comment
Line 36: Line 36:
   * 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		    * author kernel USNs
   * work on GCC pie build failures to prepare debdiffs to sponsor
   * look at !AppArmor stacking work
   * cut 2.11 !AppArmor release
    * requires packaging work for new binutils/ directory in upstream !AppArmor
  }}}
Line 44: Line 44:
   * embargoed issue
Line 46: Line 45:
    * 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		     * more testing
    * help land
   * Fix eCryptfs parallel copy file corruption bug (LP: #1543633)
   * embargoed issues
  {{{#!wiki comment
Line 50: Line 51:
   * email catch up
   * !AppArmor stacking development
   * sync with sbeattie and kernel team regarding pending kernel updates		    * !AppArmor stacking
  }}}
Line 55: Line 55:
   * DPDK MIR
   * pick up another MIR		    * finish fwupd MIR
   * golang-websocket-dev MIR
   * !AppArmor reviews
Line 58: Line 59:
   * sponsor chromium-browser updates
Line 59: Line 61:
   * Oxide 1.13 [[https://launchpad.net/oxide/+milestone/branch-1.13|milestones]]    * Convergence related tasks
    * https://blueprints.launchpad.net/oxide/+spec/converged-device-support
Line 67: Line 70:
Logs available at TODO Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-03-14-16.32.moin.txt

Meeting (DRAFT)

  • Who: SecurityTeam

  • When: Mon Mar 21st 2016 16:30 UTC

  • End: 16:50 UTC

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

  • Chaired By: Tyler Hicks (tyhicks)

Attendance

  • jdstrand
  • mdeslaur
  • tyhicks
  • sarnold

  • ChrisCoulson

Not present

  • jjohansen
  • sbeattie

Agenda

  • Announcements
    • None
  • Weekly stand-up report (each member discusses any pending and planned future work for the week)
    • jdstrand
      • continue snappy interfaces work
      • start looking into snappy developer mode
      • two embargoed issues
    • mdeslaur
      • weekly role: happy place
      • patch piloting
      • graphite2 updates
      • exim2 updates
    • tyhicks
      • weekly role: bug triage

      • AppArmor stacking

        • more testing
        • help land
      • Fix eCryptfs parallel copy file corruption bug (LP: #1543633)
      • embargoed issues
    • sarnold
      • weekly role: cve triage
      • finish fwupd MIR
      • golang-websocket-dev MIR

      • AppArmor reviews

    • 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-03-14-16.32.moin.txt

MeetingLogs/Security/20160321 (last edited 2016-03-21 16:57:58 by tyhicks)