From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Spectre-NG
Date: Mon, 07 May 2018 12:15:47 +0100 [thread overview]
Message-ID: <1549166.RPGoRN5ZiQ@dell_xps> (raw)
[-- Attachment #1: Type: text/plain, Size: 229 bytes --]
Rich was right when he mentioned more related vulnerabilities are bound to
show up soon:
https://www.heise.de/ct/artikel/Exclusive-Spectre-NG-Multiple-new-Intel-CPU-flaws-revealed-several-serious-4040648.html
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2018-05-07 11:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 11:15 Mick [this message]
2018-05-07 11:45 ` [gentoo-user] Spectre-NG Rich Freeman
2018-05-08 8:19 ` [gentoo-user] Spectre-NG Martin Vaeth
2018-05-08 20:15 ` Rich Freeman
2018-05-09 18:18 ` Martin Vaeth
2018-05-09 19:04 ` Wols Lists
2018-05-09 22:50 ` Ian Zimmerman
2018-05-10 13:35 ` Wol's lists
2018-05-10 16:52 ` Ian Zimmerman
2018-05-09 19:16 ` Rich Freeman
2018-05-10 5:34 ` Martin Vaeth
2018-05-10 13:58 ` Rich Freeman
2018-05-10 15:31 ` Martin Vaeth
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=1549166.RPGoRN5ZiQ@dell_xps \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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