20150316

Differences between revisions 1 and 23 (spanning 22 versions)
Revision 1 as of 2015-01-26 16:50:46
Size: 2687
Editor: tyhicks
Comment:
Revision 23 as of 2015-03-02 17:02:40
Size: 2922
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/20150223
== Meeting ==
Line 3: Line 4:
 * '''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 Mar 2nd 2015 16:37 UTC
 * '''End''': 17:01 UTC
Line 6: Line 7:
 * '''Chaired By''': JamieStrandboge (jdstrand)  * '''Chaired By''': Tyler Hicks (tyhicks)
Line 18: Line 19:
 * None
Line 22: Line 22:
  * 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! :)
Line 25: Line 24:
   * weekly role: triage
   * snappy
   * pending issues
   * updating the store review tools for snappy
   * helping with the oxide FFe and to coordinate some oxide work
   * team performance reviews
   * longer term design of snappy hardware access
   * discuss overlayfs and AppArmor in regards to snappy
Line 30: Line 31:
   * pending updates (openssl)
   * embargoed issue
   * patch piloting
   * ice updates
   * more security updates
Line 33: Line 35:
   * pending updates (various yaml packages)
   * !AppArmor patch review
   * binutils security update
   * pick up pie-on-amd64
   * weekly role: bug triage
   * fix the fix for bug 1422521
   * testing gcc-5 packages that have pie by default set
   * AppArmor patch review
   * possible AppArmor 2.9.2 release
   * do a more investigation into how the apparmor init script is working with systemd
Line 38: Line 42:
   * 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
   * land fixes upstream, retest and publish ecryptfs-utils security updates
   * add the ability to check subfeatures and then send out v2 of the libapparmor API changes
   * restart work on AppArmor kernel keyring mediation for user data encryption
Line 42: Line 47:
   * monthly !AppArmor meeting
   * !AppArmor patch review
   * Bug:1408833
   * Bug:1408106 - attach_disconnected not sufficient for overlayfs
   * !AppArmor upstreaming
   * finish testing the fix for the failing fd inheritance tests on krillin (LP: #1423810)
   * triage bug 1425398
   * push the current stack of bug fixes up to the kernel team
   * finish reviewing of the latest revision of the LSM stacking patches
   * review/discuss the libapparmor policy load api
   * sync up with jdstrand on overlayfs
   * AppArmor kernel cleanups and upstreaming
Line 48: Line 55:
   * weekly role: happy place
    * pending updates (coreutils)
    *
MIR audits
  * chrisccoulson
   * mozilla updates
   * Bug:1377198 - CertificateError is not cancelled if you stop the pending navigation
  * weekly role: happy place
    * several MIRs at the server team's request
  * chriscoulson
    * Thunderbird updates
    * possible Chromium and oxide updates
    *
oxide bugs
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-03-02-16.37.moin.txt

Meeting

  • Who: SecurityTeam

  • When: Mon Mar 2nd 2015 16:37 UTC

  • End: 17:01 UTC

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

  • Chaired By: Tyler Hicks (tyhicks)

Attendance

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

Not present

Agenda

  • Announcements
  • Weekly stand-up report (each member discusses any pending and planned future work for the week)
    • jdstrand
      • updating the store review tools for snappy
      • helping with the oxide FFe and to coordinate some oxide work
      • team performance reviews
      • longer term design of snappy hardware access
      • discuss overlayfs and AppArmor in regards to snappy

    • mdeslaur
      • weekly role: community
      • patch piloting
      • ice updates
      • more security updates
    • sbeattie
      • weekly role: bug triage
      • fix the fix for bug 1422521
      • testing gcc-5 packages that have pie by default set
      • AppArmor patch review

      • possible AppArmor 2.9.2 release

      • do a more investigation into how the apparmor init script is working with systemd
    • tyhicks
      • weekly role: cve triage
      • land fixes upstream, retest and publish ecryptfs-utils security updates
      • add the ability to check subfeatures and then send out v2 of the libapparmor API changes
      • restart work on AppArmor kernel keyring mediation for user data encryption

    • jjohansen
      • finish testing the fix for the failing fd inheritance tests on krillin (LP: #1423810)
      • triage bug 1425398
      • push the current stack of bug fixes up to the kernel team
      • finish reviewing of the latest revision of the LSM stacking patches
      • review/discuss the libapparmor policy load api
      • sync up with jdstrand on overlayfs
      • AppArmor kernel cleanups and upstreaming

    • sarnold
      • weekly role: happy place
      • several MIRs at the server team's request
    • chriscoulson
      • Thunderbird updates
      • possible Chromium and oxide updates
      • oxide bugs
  • 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-03-02-16.37.moin.txt

MeetingLogs/Security/20150316 (last edited 2015-03-16 16:59:48 by tyhicks)