Security Team Weekly Summary: December 21, 2017
Canonical
on 21 December 2017
This article is more than 8 years old.
The Security Team weekly reports are intended to be very short summaries of the Security Team’s weekly activities.
If you would like to reach the Security Team, you can find us at the #ubuntu-hardened channel on FreeNode. Alternatively, you can mail the Ubuntu Hardened mailing list at: ubuntu-hardened@lists.ubuntu.com
During the last week, the Ubuntu Security team:
- Triaged 301 public security vulnerability reports, retaining the 47 that applied to Ubuntu.
- Published 5 Ubuntu Security Notices which fixed 3 security issues (CVEs) across 7 supported packages.
Ubuntu Security Notices
Bug Triage
Mainline Inclusion Requests
-
libteam underway (LP: #1392012)
-
MIR backlog: https://bugs.launchpad.net/~ubuntu-security/+assignedbugs?field.searchtext=%5BMIR%5D
Development
- Disable squashfs fragments in snap
- prepared/tested/uploaded squashfs-tools fixes for 1555305 in bionic through trusty and did SRU paperwork
- PR 4387 – explicitly deny ~/.gnupg/random_seed in gpg-keys interface
- Submitted PR 4399 for rewrite snappy-app-dev in Go
- Created PR 4406 – interfaces/dbus: adjust slot policy for listen, accept and accept4 syscalls
- Reviews
- PR 4365 – wayland slot implementation
What the Security Team is Reading This Week
Weekly Meeting
More Info
Talk to us today
Interested in running Ubuntu in your organisation?
Newsletter signup
Related posts
The foundations of software: open source libraries and their maintainers
Open source libraries are repositories of code that developers can use and, depending on the license, contribute to, modify, and redistribute. Open source...
From inspiration to impact: design students from Regent’s University London explore open design for their dissertation projects
Last year, we had the opportunity to speak at Regent’s UX Conference (Regent’s University London’s conference to showcase UX work by staff, students, and...
When an upstream change broke smartcard FIPS authentication – and how we fixed it
This is the story of how Canonical’s Support team provided bug-fix support: we tracked down an upstream change in OpenSC that inadvertently broke FIPS...