20160321

Differences between revisions 35 and 51 (spanning 16 versions)
Revision 35 as of 2016-01-11 16:56:17
Size: 2674
Editor: tyhicks
Comment:
Revision 51 as of 2016-03-07 15:48:18
Size: 2381
Editor: tyhicks
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was copied from MeetingLogs/Security/20160104
== Meeting ==
## page was copied from MeetingLogs/Security/20160229
== Meeting (DRAFT) ==
Line 4: Line 4:
 * '''When''': Mon Jan 11th 2016 16:35 UTC
 * '''End''': 16:53 UTC
 * '''When''': Mon Mar 7th 2016 16:30 UTC
 * '''End''': 16:50 UTC
Line 14: Line 14:
 * jjohansen
Line 15: Line 16:
 * chrisccoulson  * !ChrisCoulson
Line 18: Line 19:
 * jjohansen  * None
Line 22: Line 23:
  * Andreas Cadhalpun provided a debdiff for wily for ffmpeg (LP: #1528682)   * Stefan Bader (smb) provided debdiffs for precise-wily for xen
Line 25: Line 26:
   * work with zyga on snappy capabilities
   * review existing snappy frameworks as they pertain to the capabilities work
   * two embargoed issues
   * finish squashfs snappy store checks
   * snappy skills work
   * embargoed issue
Line 30: Line 31:
   * libvirt updates
* embargoed update
   * embargoed issues
   * squid3
updates
Line 34: Line 35:
   * work on GCC pie build failures
Line 35: Line 37:
   * 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
Line 42: Line 39:
   * embargoed issue
Line 44: Line 40:
    * 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
    * finish the parser changes needed for stacking
   * Fix eCryptfs parallel copy file corruption bug (LP: #1543633)
   * embargoed issues
Line 49: Line 45:
   * email catch up
   * !AppArmor stacking development
   * sync with sbeattie and kernel team regarding pending kernel updates
   * !AppArmor stacking
Line 55: Line 49:
   * DPDK MIR
   * pick up another MIR
   * openjpeg MIR
   * fwupd and fwupdate MIRs
    * fwupdate review is a re-review of a previous MIR that sarnold performed
   * embargoed issue
Line 58: Line 54:
   * Firefox updates
Line 59: Line 56:
   * 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 65:
Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-01-11-16.35.moin.txt Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-02-29-16.36.moin.txt

Meeting (DRAFT)

  • Who: SecurityTeam

  • When: Mon Mar 7th 2016 16:30 UTC

  • End: 16:50 UTC

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

  • Chaired By: Tyler Hicks (tyhicks)

Attendance

  • jdstrand
  • mdeslaur
  • sbeattie
  • tyhicks
  • jjohansen
  • sarnold
  • ChrisCoulson

Not present

  • None

Agenda

  • Announcements
    • Stefan Bader (smb) provided debdiffs for precise-wily for xen
  • Weekly stand-up report (each member discusses any pending and planned future work for the week)
    • jdstrand
      • finish squashfs snappy store checks
      • snappy skills work
      • embargoed issue
    • mdeslaur
      • weekly role: bug triage
      • embargoed issues
      • squid3 updates
    • sbeattie
      • weekly role: cve triage
      • work on GCC pie build failures
      • embargoed issue
    • tyhicks
      • weekly role: happy place
      • AppArmor stacking

        • finish the parser changes needed for stacking
      • Fix eCryptfs parallel copy file corruption bug (LP: #1543633)
      • embargoed issues
    • sarnold
      • weekly role: community
      • openjpeg MIR
      • fwupd and fwupdate MIRs
        • fwupdate review is a re-review of a previous MIR that sarnold performed
      • embargoed issue
    • 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-02-29-16.36.moin.txt

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