20161205
Size: 2168
Comment:
|
Size: 2811
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
## page was copied from MeetingLogs/Security/20161114 | |
Line 2: | Line 3: |
== Meeting (DRAFT) == | == Meeting == |
Line 4: | Line 5: |
* '''When''': Mon Nov 14th 2016 16:30 UTC * '''End''': 16:43 UTC |
* '''When''': Mon Nov 14th 2016 16:41 UTC * '''End''': 16:56 UTC |
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 28: | Line 35: |
* imagemagick updates | |
Line 32: | Line 40: |
* openjdk-7 updates to test * finish python updates * kernel signoffs * kernel update porocess tooling changes |
|
Line 34: | Line 46: |
* finish testing for snaps on 14.04 enablement | * SRU team followup to do on the apparmor 14.04 SRU * backport dbus unrequested reply protections to 14.04's dbus * eCryptfs issue |
Line 37: | Line 51: |
* 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 60: |
* ubuntu-terminal-app * zmqpp * unity-greeter-session-broadcast * snapd-glib |
|
Line 48: | Line 61: |
* publish Oxide | * firefox update * oxide update * oxide memory consumption crash |
Line 62: | Line 77: |
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
Who: SecurityTeam
When: Mon Nov 14th 2016 16:41 UTC
End: 16:56 UTC
Where: #ubuntu-meeting on irc.freenode.net
Chaired By: Tyler Hicks (tyhicks)
Attendance
- jdstrand
- mdeslaur
- sbeattie
- tyhicks
- jjohansen
- sarnold
ChrisCoulson
Not present
- ratliff
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: bug triage
- imagemagick updates
- testing updates
- embargoed updates
- sbeattie
- weekly role: cve triage
- openjdk-7 updates to test
- finish python updates
- kernel signoffs
- kernel update porocess tooling changes
- tyhicks
- weekly role: happy place
- SRU team followup to do on the apparmor 14.04 SRU
- backport dbus unrequested reply protections to 14.04's dbus
- eCryptfs issue
- 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
- firefox update
- oxide update
- oxide memory consumption crash
https://blueprints.launchpad.net/oxide/+spec/ubuntu-webview-implementation
- jdstrand
- 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)