Re: CPU as a service // MINIX in Intel ME

2017-11-28 Thread Timothy Pearson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/28/2017 04:47 PM, White_Rabbit wrote: > Il 28 novembre 2017 22:33:06 CET, Timothy Pearson > ha scritto: >> […] Think about that: *games*. Giving >> up >> privacy and control to waste time in front of a *game*.

Re: CPU as a service // MINIX in Intel ME

2017-11-28 Thread White_Rabbit
Il 28 novembre 2017 22:33:06 CET, Timothy Pearson ha scritto: >[…] Think about that: *games*. Giving >up >privacy and control to waste time in front of a *game*. […] (I'm sorry, I know this is not a reasonable use of the list) You've never played "Metal Gear

Re: CPU as a service has come!

2017-11-28 Thread Paul Boddie
On Monday 27. November 2017 13.52.55 Giovanni Biscuolo wrote: > > please also consider that many respectable free software supporters are > proposing solutions that are **useless tech workarounds**; e.g. looking at > https://privacylab.yale.edu/ , in the "What we do" box, I read: "Hosting > Tor",

Re: CPU as a service // MINIX in Intel ME

2017-11-28 Thread Timothy Pearson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I was using "unlicensed" somewhat facetiously from a large content provider perspective; specifically, in the common usage of "not paying a license fee back to the vendor on a continuous basis". The general idea was that the machine vendor wants to

Re: CPU as a service // MINIX in Intel ME

2017-11-28 Thread Adonay Felipe Nogueira
Jost to note that not all copies of Linux are unlicensed. The unlicensed ones are those shipped or provided by non-free system distributions that happen to break the terms of the license (currently: 99%). Besides, the Linux project itself seems to currently put non-free parts inside it so, one

Re: CPU as a service // MINIX in Intel ME

2017-11-28 Thread Timothy Pearson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/28/2017 03:23 PM, Jann KRUSE wrote: > In short: > We are essentially being forced, without even being told, to run buggy > proprietary code in a very powerful and very capable hyper-hyper-visor > of our OS, which can (benign or maliciously)

Re: CPU as a service // MINIX in Intel ME

2017-11-28 Thread Jann KRUSE
On 24 November 2017 18:19:23 EET, Giovanni Biscuolo wrote: >[...] > >2. between the "user facing OS" and the hardware there are at least 2 ½ >OS kernels (MINIX and UEFI) >3. these are proprietary and very likely exploit-friendly Update: Have been exploited... (And you wouldn't