public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Microcode update AMD
Date: Mon, 17 Jan 2011 21:52:12 +0100	[thread overview]
Message-ID: <4d34abfe.815bdf0a.65ee.ffffcf70@mx.google.com> (raw)
In-Reply-To: <AANLkTi=Urr=S=REX1U3h8DvFaqmGFf7rhP5MEoOzeApV@mail.gmail.com>

On Monday 17 January 2011 12:12:08 Mark Knecht wrote:
> On Mon, Jan 17, 2011 at 11:57 AM,  <meino.cramer@gmx.de> wrote:
> <SNIP>
> 
> > So...why should I try unknown code patched into my CPU.
> > 
> > It looks like "install this virus" from the security point
> > of view, doesn't ist?
> 
> That was my point.
> 
> I think the idea Volker is suggesting is the micro-code updates go
> from AMD (who understands what the issue is with their processor) to
> the BIOS manufacturer (Phoenix or whoever did yous) and get
> incorporated in a secure way. They are 'known good' in the BIOS update
> we receive and write into a Flash drive. It's just a choice whether
> you want to use that part of BOIS or now.
> 
> After all, _any_ BIOS update represents an opportunity for someone to
> really mess you machine up. Doesn't matter if it's micro-code or
> something else.
> 
> That's my reading of this so far....
> 
> - Mark

also the microcode you download is from amd's servers. If you don't that stuff 
- you can't use CPUs because they might be loaded with 'hacked' microcode from 
the start. Or motherboards, because the bios might be hacked. Or the linux 
kernel because maybe somebody incorporated code into linux. gcc and binutils 
that looks innocent but combined will kill your machine.

On the other hand, CPU bugs can result in miscalculations. Very, very 
expensive miscalculations.

So what is worse - an instable, incorrect CPU or paranoia?



  reply	other threads:[~2011-01-17 21:16 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17 17:21 [gentoo-user] Microcode update AMD meino.cramer
2011-01-17 18:10 ` BRM
2011-01-17 18:34   ` meino.cramer
2011-01-17 19:14     ` Volker Armin Hemmann
2011-01-17 18:48   ` Mark Knecht
2011-01-17 19:12     ` Volker Armin Hemmann
2011-01-20  0:53       ` [gentoo-user] " walt
2011-01-20  1:08         ` walt
2011-01-17 19:08 ` [gentoo-user] " Volker Armin Hemmann
2011-01-17 19:19   ` meino.cramer
2011-01-17 19:46     ` Volker Armin Hemmann
2011-01-17 19:57       ` meino.cramer
2011-01-17 20:12         ` Mark Knecht
2011-01-17 20:52           ` Volker Armin Hemmann [this message]
2011-01-18  4:29       ` William Kenworthy
2011-01-18 15:38         ` Paul Hartman
2011-01-18 16:16           ` Mark Knecht
2011-01-18 17:34             ` Mark Knecht
2011-01-18 17:48               ` Volker Armin Hemmann
2011-02-05 14:28                 ` Enrico Weigelt
2011-02-05 15:26                   ` meino.cramer
2011-02-05 17:07                   ` Volker Armin Hemmann
2011-02-06 11:36                   ` Volker Armin Hemmann
2011-01-18 17:55               ` Paul Hartman
2011-01-18 18:21                 ` Mark Knecht
2011-01-18 20:42                   ` Paul Hartman
2011-01-18 20:56                     ` Mick
2011-01-18 21:13                       ` Paul Hartman
2011-01-18 23:08                         ` Mick
2011-01-18 23:56                       ` Mark Knecht
2011-01-17 20:13     ` Jason Weisberger
2011-01-17 20:49       ` Volker Armin Hemmann
2011-01-17 21:59         ` Jason Weisberger
2011-01-17 23:27           ` Volker Armin Hemmann
2011-01-18 15:39           ` [gentoo-user] " Nuno J. Silva
2011-02-05 13:34   ` [gentoo-user] " Enrico Weigelt
2011-02-05 16:15     ` Florian Philipp
2011-01-18 16:27 ` Volker Armin Hemmann
2011-01-19 17:10 ` Volker Armin Hemmann

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=4d34abfe.815bdf0a.65ee.ffffcf70@mx.google.com \
    --to=volkerarmin@googlemail.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