20150504

Differences between revisions 1 and 50 (spanning 49 versions)
Revision 1 as of 2015-01-26 16:50:46
Size: 2687
Editor: tyhicks
Comment:
Revision 50 as of 2015-04-27 16:59:43
Size: 2974
Editor: tyhicks
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== Meeting (DRAFT) == ## page was copied from MeetingLogs/Security/20150420

== Meeting ==
Line 3: Line 5:
 * '''When''': [[http://www.timeanddate.com/worldclock/fixedtime.html?month=01&day=12&year=2015&hour=16&min=30&sec=0&p1=0|Mon Jan 12th 2014 16:30 UTC]]
 * '''End''': 17:00 UTC
 * '''When''': Mon Apr 27th 2015 16:33 UTC
 * '''End''': 16:58 UTC
Line 6: Line 8:
 * '''Chaired By''': JamieStrandboge (jdstrand)  * '''Chaired By''': Tyler Hicks (tyhicks)
Line 9: Line 11:
 * jdstrand
Line 18: Line 19:
 * None  * jdstrand
Line 22: Line 23:
  * Lev Lazinskiy (levlaz) provided a debdiff for precise for nginx (LP: #1370478). Your work is very much appreciated and will keep Ubuntu users secure. Great job! :)
 * Weekly stand-up report (each member discusses any pending and planned future work for the week)
  * Rhonda D'Vine (rhonda) provided debdiffs for precise-utopic for wesnoth-1.10 (LP: #1445688)
 * Weekly stand-up report (each member discusses any pending and planned future work for the week)    {{{#!wiki comment
Line 25: Line 27:
   * weekly role: triage
   * snappy
   * pending issues
   * Finalizing snappy seccomp glue layer today
   * Test the applied snappy seccomp policies and update ubuntu-core-security, if necessary
   * Write code to update already generated snappy seccomp policies when ubuntu-core-security-seccomp is updated
   * Update snappy build to fail if the package.yaml is malformed when dbus bus-name is specified
   * Snappy review tools updates
  }}}
Line 30: Line 35:
   * pending updates (openssl)
   * embargoed issue
   * sponsoring ffmpeg
   * patch piloting
   * published several updates and have a couple more queued up for testing
   * finish the openssl precise update to enable tlsv1.2, by default, for clients
Line 33: Line 40:
   * pending updates (various yaml packages)
   * !AppArmor patch review
   * binutils security update
   * pick up pie-on-amd64
   * weekly role: bug triage
   * prepare Trusty SRU of AppArmor python utils
   * AppArmor patch review
   * continue testing of gcc-5 pie-on-amd64 packages
Line 38: Line 45:
   * pending updates (git)
   * help with Bug:1408106 - attach_disconnected not sufficient for overlayfs
   * get back to Bug:1362469 - AppArmor unrequested reply protection generates unallowable denials
   * weekly role: cve triage
   * circle back to a number of things that were ignored during the ramp up to the Vivid release
   * finish kernel patches for AppArmor kernel keyring mediation
Line 42: Line 49:
   * monthly !AppArmor meeting
   * !AppArmor patch review
   * Bug:1408833
   * Bug:1408106 - attach_disconnected not sufficient for overlayfs
   * !AppArmor upstreaming
   * Backported CVE kernel fixes to discuss with the kernel team
   * Send AppArmor bug fixes to the kernel team (LP: #1430546 and others)
   * AppArmor kernel cleanups and upstreaming
   * Triage new AppArmor kernel oops (LP: #1448912)
Line 49: Line 55:
    * pending updates (coreutils)
    * MIR audits
  * chrisccoulson
   * mozilla updates
   * Bug:1377198 - CertificateError is not cancelled if you stop the pending navigation
   * OpenStack security updates
   * AppArmor patch reviews
  * chriscoulson
   * Chromium update
   * Oxide code reviews
   * Triage browser crash on the phone
Line 58: Line 65:
  * tyhicks asked the !AppArmor devs if there was anything else needed to help the patch review for his patches. They responded "more time"
Line 61: Line 67:
Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-01-12-17.12.moin.txt Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-04-27-16.33.moin.txt

Meeting

  • Who: SecurityTeam

  • When: Mon Apr 27th 2015 16:33 UTC

  • End: 16:58 UTC

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

  • Chaired By: Tyler Hicks (tyhicks)

Attendance

  • mdeslaur
  • sbeattie
  • tyhicks
  • jjohansen
  • sarnold
  • chrisccoulson

Not present

  • jdstrand

Agenda

  • Announcements
    • Rhonda D'Vine (rhonda) provided debdiffs for precise-utopic for wesnoth-1.10 (LP: #1445688)
  • Weekly stand-up report (each member discusses any pending and planned future work for the week)
    • mdeslaur
      • weekly role: community
      • sponsoring ffmpeg
      • patch piloting
      • published several updates and have a couple more queued up for testing
      • finish the openssl precise update to enable tlsv1.2, by default, for clients
    • sbeattie
      • weekly role: bug triage
      • prepare Trusty SRU of AppArmor python utils

      • AppArmor patch review

      • continue testing of gcc-5 pie-on-amd64 packages
    • tyhicks
      • weekly role: cve triage
      • circle back to a number of things that were ignored during the ramp up to the Vivid release
      • finish kernel patches for AppArmor kernel keyring mediation

    • jjohansen
      • Backported CVE kernel fixes to discuss with the kernel team
      • Send AppArmor bug fixes to the kernel team (LP: #1430546 and others)

      • AppArmor kernel cleanups and upstreaming

      • Triage new AppArmor kernel oops (LP: #1448912)

    • sarnold
    • chriscoulson
      • Chromium update
      • Oxide code reviews
      • Triage browser crash on the phone
  • 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-27-16.33.moin.txt

MeetingLogs/Security/20150504 (last edited 2015-05-04 17:08:53 by jdstrand)