From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] new machine : (1) which CPU ?
Date: Sat, 21 Jul 2012 00:24:38 +0100 [thread overview]
Message-ID: <201207210024.49638.michaelkintzios@gmail.com> (raw)
In-Reply-To: <CA+czFiAyECou_JcBxZ-sDtX7GBoBu=ps--VQ+_dU8P8yKpy4Mw@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1924 bytes --]
On Friday 20 Jul 2012 13:13:41 Michael Mol wrote:
> On Fri, Jul 20, 2012 at 7:40 AM, <v_2e@ukr.net> wrote:
> > Hello!
> >
> > On Fri, 20 Jul 2012 03:24:42 -0400
> >
> > Philip Webb <purslow@ca.inter.net> wrote:
> >> I plan to build a new machine in the next few months:
> >> it wb for regular desktop use, but performance is as important as
> >> price.
> >>
> >> A quick look at what was available in April suggested
> >> an Intel Ivy Bridge i7 ( 22 nm ) ; Phoronix said it works with Kernel
> >> 3.2
> >> + an Intel Z77 mobo (I usually buy ASUS) & that power/watt was
> >> excellent.
> >>
> > If you are considering to buy an Intel CPU, I'd recommend you to pay
> >
> > some attention to such Intel' technologies as this one:
> > https://en.wikipedia.org/wiki/Sandy_Bridge#Intel_Insider_and_remote-contr
> > ol because it doesn't looks like an advantage to the end user, but rather
> > as a security (or privacy) hole in one's system.
>
> We went through this on this list a couple months ago.
>
> That tech has been part of business-grade laptops and workstations for
> a while. It's intended as a tool for a corporate IT department, not
> the direct user of the machine.
>
> I'm not saying it's something I'd necessarily like to have on my
> personal devices, just that it's not exactly new.
I didn't know my laptop came with this <aheam> 'Intel rootkit' feature until I
posted here a few weeks ago. I haven't done any research on this, but found
these spooky pages:
http://communities.intel.com/community/vproexpert/blog/2012/01/19/configuring-
intel-vpro-with-linux-in-user-control-mode
http://software.intel.com/en-us/articles/download-the-latest-intel-amt-open-
source-drivers/
I'm not sure how vulnerable my machine may be as supplied by Dell - I assume
that unless the system is enabled first no out-of-band attempts will work.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-07-20 23:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 7:24 [gentoo-user] new machine : (1) which CPU ? Philip Webb
2012-07-20 11:40 ` v_2e
2012-07-20 12:06 ` Dale
2012-07-20 12:18 ` Florian Philipp
2012-07-20 17:44 ` Dale
2012-07-21 1:27 ` Philip Webb
2012-07-21 1:49 ` Alecks Gates
2012-07-21 2:15 ` Dale
2012-07-21 4:06 ` Michael Mol
2012-07-21 5:55 ` waltdnes
2012-07-21 8:44 ` Florian Philipp
2012-07-21 9:59 ` v_2e
2012-07-22 3:13 ` Alecks Gates
2012-07-20 12:13 ` Michael Mol
2012-07-20 23:24 ` Mick [this message]
2012-07-21 12:33 ` [gentoo-user] " Nikos Chantziaras
2012-07-21 12:56 ` microcai
2012-07-21 13:07 ` Frank Steinmetzger
2012-07-22 3:18 ` Alecks Gates
2012-07-22 13:14 ` Nikos Chantziaras
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=201207210024.49638.michaelkintzios@gmail.com \
--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