20150420

Differences between revisions 24 and 47 (spanning 23 versions)
⇤ ← Revision 24 as of 2015-03-09 16:19:58 →
Size: 2977
Editor: tyhicks
Comment:
← Revision 47 as of 2015-04-20 17:00:43 → ⇥
Size: 2752
Editor: tyhicks
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was copied from MeetingLogs/Security/20150302
## page was copied from MeetingLogs/Security/20150223		 ## page was copied from MeetingLogs/Security/20150413
Line 5: Line 5:
 * '''When''': Mon Mar 2nd 2015 16:37 UTC
 * '''End''': 17:01 UTC		  * '''When''': Mon Apr 20th 2015 16:33 UTC
 * '''End''': 16:59 UTC
Line 23: Line 23:
 * Weekly stand-up report (each member discusses any pending and planned future work for the week)  * Weekly stand-up report (each member discusses any pending and planned future work for the week) 
Line 25: Line 25:
   * 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		    * 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 31: Line 31:
   * weekly role: community
   * patch piloting
   * ice updates		    * weekly role: bug triage
   * php5 updates
   * mysql updates
Line 36: Line 36:
   * 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		    * weekly role: cve triage
   * openjdk updates
   * Do apparmor 2.9.2 release
   * Prepare for Trusty SRU of AppArmor python utils
   * Continue testing of gcc-5 pie-on-amd64 packages
Line 43: Line 42:
   * 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		    * weekly role: happy place
   * Review snappy launcher
   * Review some snippets at the request of IS
   * Vivid systemd/sbuild/schroot bugs (LP: #1427264) (LP: #1438942)
   * Restart work on AppArmor kernel keyring mediation for user data encryption
Line 48: Line 48:
   * 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		    * AppArmor kernel cleanups and upstreaming
   * Possible help with 2.9.2 and 2.10 apparmor releases
   * Kernel SRU prep for the current release cycle
Line 56: Line 52:
    * weekly role: happy place
    * several MIRs at the server team's request		    * weekly role: community
   * OpenStack security updates
   * AppArmor patch reviews
   * conntrack MIR
Line 59: Line 57:
  * Thunderbird updates
  * possible Chromium and oxide updates
    * oxide bugs		    * Probable firefox update
   * Release oxide 1.6
   * Oxide code reviews
   * Oxide bugs
Line 68: Line 67:
Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-03-02-16.37.moin.txt Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-04-20-16.33.moin.txt

Meeting

  • Who: SecurityTeam

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

  • End: 16:59 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
      • 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
    • mdeslaur
      • weekly role: bug triage
      • php5 updates
      • mysql updates
      • more security updates
    • sbeattie
      • weekly role: cve triage
      • openjdk updates
      • Do apparmor 2.9.2 release

      • Prepare for Trusty SRU of AppArmor python utils

      • Continue testing of gcc-5 pie-on-amd64 packages
    • tyhicks
      • weekly role: happy place
      • Review snappy launcher
      • Review some snippets at the request of IS
      • Vivid systemd/sbuild/schroot bugs (LP: #1427264) (LP: #1438942)

      • Restart work on AppArmor kernel keyring mediation for user data encryption

    • jjohansen

      • AppArmor kernel cleanups and upstreaming

      • Possible help with 2.9.2 and 2.10 apparmor releases
      • Kernel SRU prep for the current release cycle
    • sarnold
      • weekly role: community

      • OpenStack security updates

      • AppArmor patch reviews

      • conntrack MIR
    • chriscoulson
      • Probable firefox update
      • Release oxide 1.6
      • Oxide code reviews
      • 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-04-20-16.33.moin.txt

MeetingLogs/Security/20150420 (last edited 2015-04-20 17:00:43 by tyhicks)