20161205

Differences between revisions 50 and 53 (spanning 3 versions)
Revision 50 as of 2016-11-14 16:38:02
Size: 2168
Editor: tyhicks
Comment:
Revision 53 as of 2016-11-21 15:08:22
Size: 2679
Editor: tyhicks
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was copied from MeetingLogs/Security/20161031 ## page was copied from MeetingLogs/Security/20161114
Line 4: Line 4:
 * '''When''': Mon Nov 14th 2016 16:30 UTC
 * '''End''': 16:43 UTC
 * '''When''': Mon Nov 21st 2016 16:30 UTC
 * '''End''': 16:50 UTC
Line 17: Line 17:
 * ratliff
Line 19: Line 20:
 * ratliff  * None
Line 26: Line 27:
   * finalize various snappy interface PR reviews
   * address feedback in 32 bit binaries on 64 bit snap-confine PR
   * various snappy policy updates
   * pick up dbus-app PR
   * start looking at network-namespace interface
   * begin implementing seccomp arg filtering policy
Line 27: Line 34:
   * weekly role: bug triage    * weekly role: community
  * imagemagick updates
Line 31: Line 39:
   * weekly role: bug triage
   * openjdk-7 updates to test
   * finish python updates
   * kernel signoffs
   * kernel update porocess tooling changes
  * tyhicks
Line 32: Line 46:
  * tyhicks
   * weekly role: happy place
   * finish testing for snaps on 14.04 enablement
   * SRU team followup to do on the apparmor 14.04 SRU
   * eCryptfs issues
Line 37: Line 50:
   * work on bug fixes for stacking
   * upstream the change_hat() fix
   * gsettings review and related work
   * 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
Line 43: Line 59:
    * ubuntu-terminal-app
    * zmqpp
    * unity-greeter-session-broadcast
    * snapd-glib
Line 48: Line 60:
   * publish Oxide    * firefox update
   * oxide update
   * oxide memory consumption crash
Line 50: Line 64:
  {{{#!wiki comment
Line 52: Line 65:
   * weekly role: CVE triage    * weekly role: happy place
Line 54: Line 67:
  }}}
Line 62: Line 74:
Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-10-31-16.30.moin.txt Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-11-14-16.41.moin.txt

Meeting (DRAFT)

  • Who: SecurityTeam

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

  • End: 16:50 UTC

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

  • Chaired By: Tyler Hicks (tyhicks)

Attendance

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

  • ratliff

Not present

  • None

Agenda

  • Announcements
    • None
  • Weekly stand-up report (each member discusses any pending and planned future work for the week)
    • jdstrand
      • finalize various snappy interface PR reviews
      • address feedback in 32 bit binaries on 64 bit snap-confine PR
      • various snappy policy updates
      • pick up dbus-app PR
      • start looking at network-namespace interface
      • begin implementing seccomp arg filtering policy
    • mdeslaur
      • weekly role: community
      • imagemagick updates
      • testing updates
      • embargoed updates
    • sbeattie
      • weekly role: bug triage
      • openjdk-7 updates to test
      • finish python updates
      • kernel signoffs
      • kernel update porocess tooling changes
    • tyhicks
      • weekly role: cve triage
      • SRU team followup to do on the apparmor 14.04 SRU
      • eCryptfs issues
      • seccomp logging improvements
    • 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
    • sarnold
      • weekly role: happy place
      • MIR audits
    • ChrisCoulson

    • ratliff
      • weekly role: happy place
      • 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-14-16.41.moin.txt

MeetingLogs/Security/20161205 (last edited 2016-12-05 18:56:44 by tyhicks)