20150601
3067
Comment:
|
2974
|
Deletions are marked like this. | Additions are marked like this. |
Line 3: | Line 3: |
== Meeting (DRAFT) == | == Meeting == |
Line 5: | Line 5: |
* '''When''': Mon Apr 27th 2015 16:30 UTC * '''End''': 17:00 UTC |
* '''When''': Mon Apr 27th 2015 16:33 UTC * '''End''': 16:58 UTC |
Line 11: | Line 11: |
* jdstrand | |
Line 20: | Line 19: |
* jdstrand | |
Line 25: | Line 25: |
{{{#!wiki comment | |
Line 26: | Line 27: |
{{{#!wiki comment | |
Line 32: | Line 32: |
}}} | }}} |
Line 35: | Line 35: |
{{{#!wiki comment * php5 updates * mysql updates * more security updates }}} |
* sponsoring ffmpeg * patch piloting * published several updates and have a couple more queued up for testing * finish the openssl precise update to enable tlsv1.2, by default, for clients |
Line 42: | Line 41: |
{{{#!wiki comment * openjdk updates * Do apparmor 2.9.2 release * Prepare for Trusty SRU of AppArmor python utils * Continue testing of gcc-5 pie-on-amd64 packages }}} |
* prepare Trusty SRU of AppArmor python utils * AppArmor patch review * continue testing of gcc-5 pie-on-amd64 packages |
Line 50: | Line 46: |
{{{#!wiki comment * Review snappy launcher * Review some snippets at the request of IS * Vivid systemd/sbuild/schroot bugs (LP: #1427264) (LP: #1438942) * Restart work on AppArmor kernel keyring mediation for user data encryption }}} |
* circle back to a number of things that were ignored during the ramp up to the Vivid release * finish kernel patches for AppArmor kernel keyring mediation |
Line 57: | Line 49: |
{{{#!wiki comment * AppArmor kernel cleanups and upstreaming * Possible help with 2.9.2 and 2.10 apparmor releases * Kernel SRU prep for the current release cycle }}} |
* Backported CVE kernel fixes to discuss with the kernel team * Send AppArmor bug fixes to the kernel team (LP: #1430546 and others) * AppArmor kernel cleanups and upstreaming * Triage new AppArmor kernel oops (LP: #1448912) |
Line 64: | Line 55: |
{{{#!wiki comment | |
Line 67: | Line 57: |
* conntrack MIR }}} |
|
Line 70: | Line 58: |
{{{#!wiki comment * Probable firefox update * Release oxide 1.6 |
* Chromium update |
Line 74: | Line 60: |
* Oxide bugs }}} |
* Triage browser crash on the phone |
Line 82: | Line 67: |
Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-04-20-16.33.moin.txt | Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-04-27-16.33.moin.txt |
Meeting
Who: SecurityTeam
When: Mon Apr 27th 2015 16:33 UTC
End: 16:58 UTC
Where: #ubuntu-meeting on irc.freenode.net
Chaired By: Tyler Hicks (tyhicks)
Attendance
- mdeslaur
- sbeattie
- tyhicks
- jjohansen
- sarnold
- chrisccoulson
Not present
- jdstrand
Agenda
- Announcements
- Rhonda D'Vine (rhonda) provided debdiffs for precise-utopic for wesnoth-1.10 (LP: #1445688)
- Weekly stand-up report (each member discusses any pending and planned future work for the week)
- mdeslaur
- weekly role: community
- sponsoring ffmpeg
- patch piloting
- published several updates and have a couple more queued up for testing
- finish the openssl precise update to enable tlsv1.2, by default, for clients
- sbeattie
- tyhicks
- weekly role: cve triage
- circle back to a number of things that were ignored during the ramp up to the Vivid release
finish kernel patches for AppArmor kernel keyring mediation
- jjohansen
- sarnold
- chriscoulson
- Chromium update
- Oxide code reviews
- Triage browser crash on the phone
- 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
Log
Logs available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-04-27-16.33.moin.txt
MeetingLogs/Security/20150601 (last edited 2015-06-01 17:08:08 by tyhicks)