From: "txt.file" <txt.file@txtfile.eu>
To: libreplanet-discuss@libreplanet.org
Subject: Re: Does VIA's x86 CPUs have non-free "ME"s?
Date: Mon, 21 Aug 2017 18:53:00 +0000 [thread overview]
Message-ID: <01e6b3f9-93b4-c2fa-33b4-9fb8bebfd244@txtfile.eu> (raw)
In-Reply-To: <a1d93a29-00f6-047f-60fb-389ecdc992a3@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1616 bytes --]
Even AMD and Intel had not always these „management“ engines. If you use
a cpu older than these techniques then you are probably safer.
According to libreboot[0] pre-2013 AMD cpus are not know to be vulnerable.
en.wikipedia[1] lists which Intel cpu has which version of Intel AMT.
First mentioned version is for an ethernet controller released Q2'05.
The latest VIA cpus have been released in May 2011. AMD had no
„management“ engine at this point in time. Intel had already a few
versions of their hard-/software. So I expect all public released VIA
cpus have _no_ such engine. But I have no proof.
kind regards
txt.file
[0] https://libreboot.org/faq.html#amd
[1]
https://en.wikipedia.org/w/index.php?title=Intel_AMT_versions&oldid=792147452
Pen-Yuan Hsing:
> Dear Libreplanet,
>
> As we all know, a major problem with Intel (and AMD) x86 CPUs is that
> they come with a proprietary "Management Engine (ME)" (or "Platform
> Security Processor" for AMD) that is not only non-free but also with
> demonstrated security holes.
>
> I just recalled that VIA Technologies also have a line of x86 CPUs [1].
> Do VIA CPUs also have the equivalent of the much-maligned ME? Or are VIA
> CPUs more freedom-respecting? Would it help software freedom at all (or
> not?) to use VIA CPUs instead? I'm curious!
>
> [1]: https://en.wikipedia.org/wiki/VIA_Technologies#Processors
>
> _______________________________________________
> libreplanet-discuss mailing list
> libreplanet-discuss@libreplanet.org
> https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 183 bytes --]
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
next prev parent reply other threads:[~2017-08-21 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 15:30 Does VIA's x86 CPUs have non-free "ME"s? Pen-Yuan Hsing
2017-08-21 18:53 ` txt.file [this message]
2017-08-21 18:56 ` Pen-Yuan Hsing
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
List information: https://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01e6b3f9-93b4-c2fa-33b4-9fb8bebfd244@txtfile.eu \
--to=txt.file@txtfile.eu \
--cc=libreplanet-discuss@libreplanet.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).