20180129

Differences between revisions 65 and 69 (spanning 4 versions)
Revision 65 as of 2018-01-22 16:04:08
Size: 2912
Editor: tyhicks
Comment:
Revision 69 as of 2018-01-29 16:28:09
Size: 2650
Editor: tyhicks
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was copied from MeetingLogs/Security/20171211 ## page was copied from MeetingLogs/Security/20180122
Line 4: Line 4:
 * '''When''': Mon Jan 22nd 2018 16:30 UTC
 * '''End''': 16:48 UTC
 * '''When''': Mon Jan 29th 2018 16:43 UTC
 * '''End''': 17:09 UTC
Line 14: Line 14:
 * jjohansen
Line 17: Line 16:
 * ratliff
Line 20: Line 20:
 * ratliff  * jjohansen
Line 24: Line 24:
  * Otto Kekäläinen provided debdiffs for mariadb-5.5, mariadb-10.0, and mariadb-10.1 (LP: #1740608) (LP: #740768)
  * Ray Link (rlink) provided a debdiff for xenial for xmltooling (LP: #1743762)
  * None
Line 29: Line 28:
    * wayland slot
Line 31: Line 29:
    * xdg-settings/userd
   * rewrite the snappy-app-dev udev script
   * finish review-tools updates for December
   * pickup brand store snap declarations as have time
   * pickup tun/tap and kmod spread test issues
    * portals
    * x11 interface slot policy
   * lxd snap regression wrt confinement
   * LSM stacking demo
   * create screencast interface
   * stric mode snaps on livecd
   * upload chrony with an AppArmor profile in bionic
Line 37: Line 37:
   * weekly role: bug triage
   * intel-microcode update
   * mysql updates
   * QEMU updates
  * sbeattie
Line 38: Line 43:
   * openssl security update
   * ubuntu-support-status improvements
   * additional security updates
  * sbeattie
   * GCC retpoline backports
   * kernel USN publication
   * kernel CVE triage
   * openjdk packages
  * tyhicks
   * Meltdown/Spectre fix coordination
   * LSM stacking demo
  {{{#!wiki comment
  * jjohansen
   * update bionic LSM stacking patches with the latest upstream revision
   * !AppArmor mount mediation
   * FOSDEM prep
   * 4.16 pull request
  }}}
  * sarnold
Line 43: Line 59:
   * CVE notifications for snap owners
   * upstream !AppArmor tasks
   * kernel CVE triage
  * tyhicks
   * weekly role: happy place
   * embargoed issues
   * squashfs reproduceability
   * nudge a number of things along:
    * snapd seccomp logging PR
    * libseccomp Xenial SRU
    * audit SRUs
    * libseccomp-golang upstream PR
  * jjohansen
   * !AppArmor mount mediation
   * prepare 4.14 !AppArmor backport for the Ubuntu kernel
   * update the backport kernels
  * sarnold
   * weekly role: community
   * libteam MIR
   * sync w/ tyhicks to identify next MIR to start on
Line 63: Line 61:
   * publish chromium-browser updates
  {{{#!wiki comment
   * firefox updates
   * chromium-browser updates to test and publish
   * rust updates
   * !AppArmor audit logging changes
Line 69: Line 69:
  }}}
Line 71: Line 70:
   * weekly role: bug triage
   * libxml2 updates
   * weekly role: community
   *
gimp update
   * rsync update
   * my
sql update
Line 75: Line 76:
 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:
 <<Include(SecurityTeam/HighlightedPackages, , from="==== Highlighted packages: ====", to="Last updated:")>>
 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 http://people.canonical.com/~ubuntu-security/d2u/ for available merges and https://wiki.ubuntu.com/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 https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.
Line 81: Line 81:
Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-12-11-16.30.moin.txt Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2018/ubuntu-meeting.2018-01-22-16.43.moin.txt

Meeting (DRAFT)

  • Who: SecurityTeam

  • When: Mon Jan 29th 2018 16:43 UTC

  • End: 17:09 UTC

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

  • Chaired By: Tyler Hicks (tyhicks)

Attendance

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

Not present

  • jjohansen

Agenda

  • Announcements
    • None
  • Weekly stand-up report (each member discusses any pending and planned future work for the week)
    • jdstrand
      • snapd PR reviews
        • layouts
        • portals
        • x11 interface slot policy
      • lxd snap regression wrt confinement
      • LSM stacking demo
      • create screencast interface
      • stric mode snaps on livecd
      • upload chrony with an AppArmor profile in bionic

    • mdeslaur
      • weekly role: bug triage
      • intel-microcode update
      • mysql updates
      • QEMU updates
    • sbeattie
      • weekly role: CVE triage
      • GCC retpoline backports
      • kernel USN publication
      • kernel CVE triage
      • openjdk packages
    • tyhicks
      • Meltdown/Spectre fix coordination
      • LSM stacking demo
    • sarnold
      • weekly role: happy place
      • sync w/ tyhicks to identify next MIR to start on
    • ChrisCoulson

      • firefox updates
      • chromium-browser updates to test and publish
      • rust updates
      • AppArmor audit logging changes

    • ratliff
      • weekly role: happy place
      • internal work
      • import KPI data into InfluxDB
    • leosilva
      • weekly role: community
      • gimp update
      • rsync update
      • mysql update
      • additional security updates
  • Highlighted packages

    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 http://people.canonical.com/~ubuntu-security/d2u/ for available merges and https://wiki.ubuntu.com/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 https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.

  • Miscellaneous and Questions
    • None

Log

Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2018/ubuntu-meeting.2018-01-22-16.43.moin.txt

MeetingLogs/Security/20180129 (last edited 2018-02-05 16:33:42 by tyhicks)