public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: pavel@denx.de (Pavel Machek)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [ANNOUNCE] 4.19.50-cip3 and 4.4.181-cip33
Date: Mon, 24 Jun 2019 13:11:41 +0200	[thread overview]
Message-ID: <20190624111141.GA22088@amd> (raw)
In-Reply-To: <b7549d5e-bf7e-ba5b-dd44-fca0346b8a12@siemens.com>

Hi!

> > Although patches for MDS are included in this release, no test code has been
> > published for these, so we have not tested for MDS. Also, patches did not
> > really follow the stable rules, so they could not be checked the same way
> > as checking for other patches. But the bug is ugly enough so we included
> > the patches anyway.
> > For the above reasons, modern x86 CPUs can not really be trusted with secrets;
> > similar attacks are likely to happen in future.
> > 
> 
> I wouldn't see it that extreme, it still heavily depends on what you are running and where. Also, the attacks are getting more complex.
> 

Well, most systems do not really need to protect local user's secrets
from each other. We simply don't allow code execution for untrusted
parties.

If someone decides to combine "top secret document storage" and
"honeypot giving shell to attackers" on single machine, well, they are
asking for trouble.

Best regards,
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20190624/698caec2/attachment.sig>

      parent reply	other threads:[~2019-06-24 11:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14  9:11 [cip-dev] [ANNOUNCE] 4.19.50-cip3 and 4.4.181-cip33 nobuhiro1.iwamatsu at toshiba.co.jp
2019-06-16 22:14 ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-06-19 16:58   ` Jan Kiszka
2019-06-20 10:00     ` nobuhiro1.iwamatsu at toshiba.co.jp
2019-06-24 11:11     ` Pavel Machek [this message]

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=20190624111141.GA22088@amd \
    --to=pavel@denx.de \
    --cc=cip-dev@lists.cip-project.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