20161121

Differences between revisions 12 and 55 (spanning 43 versions)
Revision 12 as of 2016-07-11 15:40:03
Size: 3013
Editor: tyhicks
Comment:
Revision 55 as of 2016-11-21 16:51:19
Size: 2722
Editor: tyhicks
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was copied from MeetingLogs/Security/20160627
## page was copied from MeetingLogs/Security/20
160620
## page was copied from MeetingLogs/Security/20161114
Line 5: Line 4:
 * '''When''': Mon June 27th 2016 16:31 UTC
 * '''End''': 16:54 UTC
 * '''When''': Mon Nov 21st 2016 16:31 UTC
 * '''End''': 16:50 UTC
Line 13: Line 12:
 * sbeattie
Line 21: Line 19:
 * None  * sbeattie
Line 25: Line 23:
  * Stefan Bader (smb) provided debdiffs for precise-xenial for xen
  * Otto Kekäläinen (otto) provided debdiffs for wily-xenial for mariadb-10.0 (LP: #1589302)
  * None
Line 29: Line 26:
   * Snappy dbus-bind interface
   * Snappy interfaces documentation
   * Work with morphis on testing/sponsoring pulseaudio SRU for disabling recording if snap policy (ie, finish phase 1)
   * dbus interface for snappy
    * finish small PR to snap-confine
   * start looking at network-namespace interface
Line 33: Line 30:
   * weekly role: CVE triage
   * tomcat updates
   * patch piloting
   * weekly role: community
   * imagemagick updates
   * security updates
Line 37: Line 34:
   * weekly role: bug triage
   * python updates to test
   * kernel signoffs
   * !AppArmor maintenance work
   * kernel update process tooling changes
  * tyhicks
   * weekly role: cve triage
   * SRU team followup to do on the apparmor 14.04 SRU
   * eCryptfs issues
    * inode timestamps issue (LP: #1636890)
    * crypto api usage issue
   * embargoed issue
   * work planning
  * jjohansen
   * AppArmor work
    * UNIX domain socket cross ns bug fix to test
    * quiet noisy logging of apparmor/.null files
    * mem leaks caused by ref counting issues
    * ADT test failures
    * upstreaming work
    * 4.9-rc7 rebase
  * sarnold
Line 38: Line 57:
   * kernel USNs
   * sponsor kinit update
   * watch for doko's yakkety test rebuild and fix any PIE related build failures
  * tyhicks
   * weekly role: community
   * !AppArmor upload and SRU
   * seccomp complain mode
   * embargoed issue
  * jjohansen
   * focus on !AppArmor (stacking bugs for 16.04)
    * finish IPC cross label validation fix for stacking
   * revise profile name validation checks
    * LXC/LXD use some characters that were planned to be blocked
   * prepare upstream kernel pull request for some of the Ubuntu !AppArmor delta
   * finish testing 4.7 !AppArmor rebase and handoff to the kernel team
  * sarnold
   * weekly role: bug triage
   * embargoed issue
Line 57: Line 58:
    * libsmbios
   * gathering info for an apt bug (LP: #1642386)
Line 58: Line 61:
   * chromium-browser sponsoring
   * publish Oxide update
   * test oxide on arm64 and fix any bugs discovered
   * converged device [[https://blueprints.launchpad.net/oxide/+spec/converged-device-support|features]] for oxide

   * document instructions for doing flash updates
   * oxide update
   * oxide build failures
   * oxide memory consumption crash
   * https://blueprints.launchpad.net/oxide/+spec/ubuntu-webview-implementation
Line 65: Line 66:
   * look into the Ubuntu CVE tracker    * weekly role: happy place
   * internal communication, coordination, and planning activities
   * universe CVEs project
Line 73: Line 76:
Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-06-27-16.31.moin.txt Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-11-21-16.31.moin.txt

Meeting

  • Who: SecurityTeam

  • When: Mon Nov 21st 2016 16:31 UTC

  • End: 16:50 UTC

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

  • Chaired By: Tyler Hicks (tyhicks)

Attendance

  • jdstrand
  • mdeslaur
  • tyhicks
  • jjohansen
  • sarnold
  • ChrisCoulson

  • ratliff

Not present

  • sbeattie

Agenda

  • Announcements
    • None
  • Weekly stand-up report (each member discusses any pending and planned future work for the week)
    • jdstrand
      • dbus interface for snappy
        • finish small PR to snap-confine
      • start looking at network-namespace interface
    • mdeslaur
      • weekly role: community
      • imagemagick updates
      • security updates
    • sbeattie
      • weekly role: bug triage
      • python updates to test
      • kernel signoffs
      • AppArmor maintenance work

      • kernel update process tooling changes
    • tyhicks
      • weekly role: cve triage
      • SRU team followup to do on the apparmor 14.04 SRU
      • eCryptfs issues
        • inode timestamps issue (LP: #1636890)
        • crypto api usage issue
      • embargoed issue
      • work planning
    • jjohansen
      • AppArmor work

        • UNIX domain socket cross ns bug fix to test
        • quiet noisy logging of apparmor/.null files
        • mem leaks caused by ref counting issues
        • ADT test failures
        • upstreaming work
        • 4.9-rc7 rebase
    • sarnold
      • weekly role: happy place
      • MIR audits
        • libsmbios
      • gathering info for an apt bug (LP: #1642386)
    • ChrisCoulson

    • ratliff
      • weekly role: happy place
      • internal communication, coordination, and planning activities
      • universe CVEs project
  • 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/2016/ubuntu-meeting.2016-11-21-16.31.moin.txt

MeetingLogs/Security/20161121 (last edited 2016-11-21 16:51:19 by tyhicks)