20170417

Differences between revisions 23 and 24
⇤ ← Revision 23 as of 2017-03-13 16:27:14 →
Size: 2790
Editor: tyhicks
Comment:
← Revision 24 as of 2017-03-13 16:49:12 → ⇥
Size: 2811
Editor: tyhicks
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
== Meeting (DRAFT) == == Meeting ==
Line 5: Line 5:
 * '''End''': 16:51 UTC  * '''End''': 16:48 UTC
Line 36: Line 36:
   * embargoed issue
   * imagemagick updates to test/release
Line 39: Line 37:
    * large apache2 backport
Line 42: Line 39:
   * embargoed issue
Line 44: Line 40:
   * look into QRT regressions/failures for the kernel team
Line 47: Line 44:
   * embargoed issue
Line 49: Line 47:
   * review snapd PR#2624
Line 51: Line 50:
    * revise and submit userspace patches to address review feedback
    * submit the !AppArmor policy notifaction interface patches for review		     * write additional regression tests
    * do FFE paperwork
Line 54: Line 53:
   * chase down kernel regressions that caused !AppArmor patches to be reverted from the recent SRU kernel
Line 57: Line 57:
   * finish lasso MIR
   * !AppArmor patch review		    * finish mellon/lasso MIR
Line 61: Line 60:
   * firefox update
   * prepare for thunderbird update
   * finish large oxide code review
   * get cargo bootstrapped in all releases
   * oxide development
   * sponsor chromium-browser		    * Firefox update for a regression fix
   * Thunderbird update
   * Oxide release
   * embargoed update
   * get firefox building with rustc/cargo
   * oxide development/reviews
Line 70: Line 69:
    * improvements to other CVE tools
Line 79: Line 79:
Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-02-27-16.42.moin.txt Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-03-13-16.31.moin.txt

Meeting

  • Who: SecurityTeam

  • When: Mon Mar 13th 2017 16:31 UTC

  • End: 16:48 UTC

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

  • Chaired By: Tyler Hicks (tyhicks)

Attendance

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

Not present

  • jdstrand

Agenda

  • Announcements
    • None
  • Weekly stand-up report (each member discusses any pending and planned future work for the week)
    • mdeslaur
      • weekly role: happy place
      • security updates
    • sbeattie
      • weekly role: happy place
      • glibc updates
      • look into QRT regressions/failures for the kernel team
      • security updates
    • tyhicks
      • weekly role: community
      • embargoed issue
      • propose design change for seccomp kernel patches and get out v5
      • design review
      • review snapd PR#2624
    • jjohansen
      • dconf/gsettings mediation
        • write additional regression tests
        • do FFE paperwork

      • preparing next batch of AppArmor kernel patches to upstream

      • chase down kernel regressions that caused AppArmor patches to be reverted from the recent SRU kernel

    • sarnold
      • weekly role: bug triage
      • shadow update
      • finish mellon/lasso MIR
      • pick up another MIR

    • ChrisCoulson

      • Firefox update for a regression fix
      • Thunderbird update
      • Oxide release
      • embargoed update
      • get firefox building with rustc/cargo
      • oxide development/reviews
    • ratliff
      • weekly role: CVE triage
      • CVE notifications
        • improvements to other CVE tools
      • internal tasks
      • security updates for ubuntu-core 15.04 and Touch
  • 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/2017/ubuntu-meeting.2017-03-13-16.31.moin.txt

MeetingLogs/Security/20170417 (last edited 2017-04-17 16:45:51 by tyhicks)