Historical speck list archives
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: speck@linutronix.de
Subject: [MODERATED] Debian problem with Slow Randomizing Boosts DoS
Date: Mon, 8 Jun 2020 21:06:21 +0200	[thread overview]
Message-ID: <20200608190621.GA2189328@eldamar.local> (raw)

Hi

A human error caused today that the changelog entry for the planned
4.9.210-1+deb9u1 upload in Debian covering the SRBDS mitigation
changes were for a short time leaked on
https://tracker.debian.org/linux (the message was sent as well to 56
subscribers for the tracker entry).

The leaked information covers the following changelog entries:

 linux (4.9.210-1+deb9u1) stretch-security; urgency=high
[...]
   * [x86] Add support for mitigation of Special Register Buffer Data Sampling
     (SRBDS) (CVE-2020-0543):
     - x86/cpu: Add 'table' argument to cpu_matches()
     - x86/speculation: Add Special Register Buffer Data Sampling (SRBDS)
       mitigation
     - x86/speculation: Add SRBDS vulnerability and mitigation documentation
     - x86/speculation: Add Ivy Bridge to affected list
   * [x86] speculation: Do not match steppings, to avoid an ABI change
[...]

The packages itself were not exposed. The NEWS entry on
https://tracker.debian.org/linux was removed.

On behalf I want to apologies for this mistake, and steps were taken
to avoid this in future.

Salvatore

             reply	other threads:[~2020-06-08 19:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 19:06 Salvatore Bonaccorso [this message]
2020-06-08 20:08 ` [MODERATED] Re: Debian problem with Slow Randomizing Boosts DoS Stewart, David C

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200608190621.GA2189328@eldamar.local \
    --to=carnil@debian.org \
    --cc=speck@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).