20170605

Differences between revisions 48 and 49
Revision 48 as of 2017-05-15 16:27:18
Size: 2782
Editor: tyhicks
Comment:
Revision 49 as of 2017-05-15 16:55:30
Size: 3390
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:57 UTC  * '''End''': 16:54 UTC
Line 27: Line 27:
   * finish overlayfs/apparmor/snaps investigation
   * snappy-debug work
    * fix to work with journald
    * update for snapd 2.25/2.26
Line 28: Line 32:
   * kubernetes-support interface
   * snappy PRs and store reviews
    * dbus activation PR upcoming
    * update-ns PR upcoming
   * seccomp arg filtering branch for uid/gid handling
   * snappy forum discussions and PR reviews
   * miscellaneous snappy policy updates PR
Line 36: Line 37:
   * tomcat7 and tomcat8 updates
   * apache2 updates
   * freetype updates
   * git updates
   * kde4libs updates
   * libytnef updates
   * gather qemu test results and then publish updates
    * cpaelzer is running tests
Line 42: Line 45:
   * openjdk-8 updates
   * openjdk-7 updates upcoming
   * libplist update
   * kernel signoff and triage
   * openjdk-7 updates to test and publish
   * kernel USNs
    * figure out precise/esm publishing
Line 47: Line 49:
   * !AppArmor upstream issues
Line 49: Line 52:
   * close precise and open precise/esm in UCT
Line 54: Line 56:
   * finish 4.11 !AppArmor port
    * memory corruption (crashing) issue is left to solve
Line 55: Line 59:
    * minimizing the securityfs changes
   * !AppArmor bug followup
    * need someone to review the upstream securityfs patch
    * LSM backlog to ensure that there are no proposed changes that affect upstreaming
     * IMA changes to fs/namespace.c are a possibility
    * fixing typesplitting so that unix mediation can go up
   * virt-aa helper upstreaming thread
Line 59: Line 66:
   * finish lasso MIR    * xdelta3 mir
   * shadow regression (LP: #bug:1690820)
   * !AppArmor patch review to support jjohansen's upstreaming work
Line 63: Line 72:
   * chromium-browser updates
   * firefox updates
    * upstream has not yet cut the release
Line 66: Line 74:
   * internal issue
   * work on the Firefox start page
    * move away start.ubuntu.com
    * provide Ubuntu-specific design once we hear back
Line 68: Line 80:
   * roadmap sprint followups
   * icu update for ESM
   * bring up the CVE notification service
   * ubuntu-core 15 update
   * internal tasks
   * technical content
    * participating in webinar
Line 79: Line 90:
Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-05-08-16.35.moin.txt Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-05-15-16.30.moin.txt

Meeting

  • Who: SecurityTeam

  • When: Mon May 15th 2017 16:30 UTC

  • End: 16:54 UTC

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

  • Chaired By: Tyler Hicks (tyhicks)

Attendance

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

Not present

  • none

Agenda

  • Announcements
    • None
  • Weekly stand-up report (each member discusses any pending and planned future work for the week)
    • jdstrand
      • finish overlayfs/apparmor/snaps investigation
      • snappy-debug work
        • fix to work with journald
        • update for snapd 2.25/2.26
      • gnome3/wayland/plasma interfaces
      • snappy forum discussions and PR reviews
      • miscellaneous snappy policy updates PR
      • embargoed issue
    • mdeslaur
      • weekly role: happy place
      • git updates
      • kde4libs updates
      • libytnef updates
      • gather qemu test results and then publish updates
        • cpaelzer is running tests
      • additional security updates as time allows
    • sbeattie
      • weekly role: community
      • openjdk-7 updates to test and publish
      • kernel USNs
        • figure out precise/esm publishing
      • additional security updates as time allows
      • AppArmor upstream issues

    • tyhicks
      • weekly role: bug triage
      • finish seccomp v5 patch set
      • start reviewing/using fscrypto userspace
      • roadmap sprint followups
    • jjohansen
      • finish 4.11 AppArmor port

        • memory corruption (crashing) issue is left to solve
      • AppArmor kernel patch upstreaming

        • need someone to review the upstream securityfs patch
        • LSM backlog to ensure that there are no proposed changes that affect upstreaming
          • IMA changes to fs/namespace.c are a possibility
        • fixing typesplitting so that unix mediation can go up
      • virt-aa helper upstreaming thread
    • sarnold
      • weekly role: cve triage
      • xdelta3 mir
      • shadow regression (LP: #bug:1690820)
      • AppArmor patch review to support jjohansen's upstreaming work

      • pick up other MIRs
    • ChrisCoulson

      • thunderbird updates
        • upstream has not yet cut the release
      • re-automate the uploading of firefox debug symbols
      • internal issue
      • work on the Firefox start page
        • move away start.ubuntu.com
        • provide Ubuntu-specific design once we hear back
    • ratliff
      • weekly role: happy place
      • internal tasks
      • technical content
        • participating in webinar
  • 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-05-15-16.30.moin.txt

MeetingLogs/Security/20170605 (last edited 2017-06-05 16:49:47 by tyhicks)