Skip to main content
  1. Blog
  2. Article

Canonical
on 21 December 2017

Security Team Weekly Summary: December 21, 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 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

Development

  • Disable squashfs fragments in snap
  • 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

Related posts


Canonical
23 April 2026

Canonical releases Ubuntu 26.04 LTS Resolute Raccoon

Canonical announcements Article

The 11th long-term supported release of Ubuntu delivers deep silicon optimization and state-of-the-art security for enterprise workloads. ...


Samir Kamerkar
22 April 2026

From Jammy to Resolute: how Ubuntu’s toolchains have evolved

Ubuntu Article

We cover new toolchain versions, devpacks and workflows that improve the developer experience. The evolution of Ubuntu’s toolchains story goes beyond just providing up-to-date GCC, LLVM, and Python. It is also about opinionated openJDK variants, task-focused devpacks, FIPS compliant toolchains, and snaps, like the new .NET snap and Snapcr ...


Rob Gibbon
20 April 2026

Hybrid search and reranking: a deeper look at RAG

AI Article

Many of us are familiar with the retrieval augmented generative AI (RAG) pattern for building agentic AI applications – like digital concierges, frontline support chatbots and agents that can help with basic self-service troubleshooting.  At a high level, the flow for RAG is fairly clear – the user’s prompt is augmented with some relevant ...