Skip to main content
  1. Blog
  2. Article

Canonical
24 August 2017

Security Team Weekly Summary: August 24, 2017


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 195 public security vulnerability reports, retaining the 42 that applied to Ubuntu.
  • Published 13 Ubuntu Security Notices which fixed 54 security issues (CVEs) across 16 supported packages.

Ubuntu Security Notices

Bug Triage

Mainline Inclusion Requests

Development

  • snapd on Debian discussion

  • add wayland interface spread test
  • verify wayland interface with sway and weston
  • reviews for snapd: solus, broadcom-asic-control interface, udev tagging, bluez implicit classic)
  • continue/propose desktop, accessibility and desktop-input interfaces
  • lots of discussion with snappy team regarding auto-connectable content snaps
  • fix apparmor ‘ux’ warning with lxd snap
  • miscellaneous policy updates (some in response to chromium snap call for testing)
  • review tools updates for new interfaces
  • AppArmor pull request for next (4.14)

What the Security Team is Reading This Week

Weekly Meeting

More Info


Related posts

Designing a better future: your guide to design contribution in Open Source

This guide covers why design matters in open source, and how designers can make a bigger impact in open source software.

How to build, maintain, and secure infrastructure for AI factories

Moving AI into production creates a long-term maintenance obligation for the software behind it. GPU infrastructure can remain in service across several generations of models...

Why embargoes matter for open source security

Open source is built on a foundation of transparency, collaboration, and speed. We share code, we share ideas, and together, we build better software. But when it comes to...

From personas to archetypes: a living, shared understanding of the people we build for (Part 2 of 2)

This is the second of two posts on our archetypes, shared, machine-readable descriptions of the people we build for. The first covers why we needed them and what they are. This...