20161205

Differences between revisions 10 and 65 (spanning 55 versions)
Revision 10 as of 2016-06-27 16:08:28
Size: 3362
Editor: tyhicks
Comment:
Revision 65 as of 2016-12-05 18:56:44
Size: 2681
Editor: tyhicks
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was copied from MeetingLogs/Security/20160620
== Meeting (DRAFT) ==
## page was copied from MeetingLogs/Security/20161128
== Meeting ==
Line 4: Line 4:
 * '''When''': Mon June 27th 2016 16:30 UTC
 * '''End''': 16:50 UTC
 * '''When''': Mon Dec 05th 2016 16:30 UTC
 * '''End''': 16:42 UTC
Line 12: Line 12:
 * sbeattie
Line 14: Line 13:
 * jjohansen
Line 20: Line 18:
 * None  * jjohansen
 * sbeattie
Line 24: 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 28: Line 26:
   * snappy PR followups (gsettings, input methods)
   * snappy interface reviews (modem-manager, ppp, etc)
   * seccomp arg filtering follow-ups
   * various snapd interface policy updates and investigations
   * review tools updates for upcoming snap.yaml changes and various bug fixes
   * im-config testing
   * docker interface as have time
   * follow up on dbus-app interface for snappy
   * snappy reviews
   * start looking at network-namespace interface
   * seccomp arg filtering policy as have time
Line 36: Line 31:
   * weekly role: CVE triage
   * publish security updates that were prepared/tested last week during the sprint
   * publish some additional security updates after testing
   * update the UEFI secure boot testing instructions
   * weekly role: happy place
   * nss updates
   * security updates
  {{{#!wiki comment
Line 42: Line 37:
   * post-sprint followups/todos
   * pick up a security update
   * watch for and fix build failures in yakkety due to gcc pie changes
   * investigate failing aslr tests on ppc64el and s390x (LP: #1594347)
   * vim updates
   * kernel USNs
   * pick up an update
   * !AppArmor maintenance work
  }}}
Line 48: Line 44:
   * post-sprint followups/todos
   * AppArmor upload and SRU
   * lingering email catchup from vacation and sprint weeks
   * seccomp complain mode
   * snap-confine PR reviews (seccomp arg filtering and some others that landed without security team review)
   * seccomp logging changes for snappy
   * eCryptfs issues
    * inode timestamps issue (LP: #1636890)
    * crypto api usage issue
Line 54: Line 49:
   * focus on !AppArmor (stacking bugs for 16.04)
   * post-sprint followups/todos
   * finish 4.7 AppArmor rebase and handoff to the kernel team
   * prepare upstream kernel pull request for some of the Ubuntu AppArmor delta
   * !AppArmor work
    * collaborate w/ desktop team to finish gsettings mediation
    * triage/fix report of apparmor_parser hanging (LP: #1645037)
    * more testing of fix for [[https://pastebin.canonical.com/172640/|mount oops]]
    * fix parser stacking bug (LP: #1639660)
Line 60: Line 56:
   * sprint prep and imagemagick    * MIR audits
    * finish libsmbios
    * start swift-s3-storage
   * test SRU fix for apt bug (LP: #1642386)
Line 62: Line 61:
   * document instructions for doing flash updates
   * oxide updates
   * test oxide on arm64 and fix any bugs discovered
   * bug 1637190
   * oxide merge review
   * https://blueprints.launchpad.net/oxide/+spec/ubuntu-webview-implementation
Line 66: Line 65:
   * post-sprint followups/todos
   * misc management tasks
   * finish the manager transition tasks from jdstrand
   * take time to learn the UCT tools
   * weekly role: cve triage
   * ghostscript regression (LP: #1647276)
Line 77: Line 74:
Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-06-20-16.31.moin.txt Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-12-05-16.30.moin.txt

Meeting

  • Who: SecurityTeam

  • When: Mon Dec 05th 2016 16:30 UTC

  • End: 16:42 UTC

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

  • Chaired By: Tyler Hicks (tyhicks)

Attendance

  • jdstrand
  • mdeslaur
  • tyhicks
  • sarnold
  • ChrisCoulson

  • ratliff

Not present

  • jjohansen
  • sbeattie

Agenda

  • Announcements
    • None
  • Weekly stand-up report (each member discusses any pending and planned future work for the week)
    • jdstrand
      • follow up on dbus-app interface for snappy
      • snappy reviews
      • start looking at network-namespace interface
      • seccomp arg filtering policy as have time
    • mdeslaur
      • weekly role: happy place
      • nss updates
      • security updates
    • tyhicks
      • weekly role: community
      • seccomp logging changes for snappy
      • eCryptfs issues
        • inode timestamps issue (LP: #1636890)
        • crypto api usage issue
    • jjohansen
      • AppArmor work

        • collaborate w/ desktop team to finish gsettings mediation
        • triage/fix report of apparmor_parser hanging (LP: #1645037)
        • more testing of fix for mount oops

        • fix parser stacking bug (LP: #1639660)
    • sarnold
      • weekly role: bug triage
      • MIR audits
        • finish libsmbios
        • start swift-s3-storage
      • test SRU fix for apt bug (LP: #1642386)
    • ChrisCoulson

    • ratliff
      • weekly role: cve triage
      • ghostscript regression (LP: #1647276)
  • 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-12-05-16.30.moin.txt

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