Hi all,<br><br><div class="gmail_quote"><div dir="ltr">Le ven. 23 mars 2018 13:56, <<a href="mailto:tpearson@raptorengineering.com">tpearson@raptorengineering.com</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I am not a lawyer, but have some understanding of the relevant liability<br>
law. This is not legal advice.<br>
<br>
If damage is cause to the hardware that the ME would have prevented, very<br>
likely. </blockquote></div><div>Damage orevrntrd by ME?</div><div><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Same goes for any security holes opened by removing the ME. </blockquote></div><div>Like deactivating fTPM Boeing considered as opening security holes? I don't understand the suppositions made here.</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This<br>
is not a supported option by Intel, so (practically*) they have no further<br>
liability for anything that goes wrong on ME scrubbed systems.<br>
<br>
* You would need to prove in an airtight manner that the same defect shows<br>
up on fully updated ME-enabled systems. Given the closed nature of the ME<br>
this may be difficult in a legal environment short of reproducing a defect<br>
across multiple ME-enabled identical systems.<br>
<br>
> Hi all,<br>
><br>
> Searching legal implications of reselling deblobbed hardware, and can't<br>
> fight straight answers.<br>
><br>
> If the bios is replaced, and ME is disabled with its modules erased, could<br>
> the maker pursue the seller for having made those modifications?<br>
><br>
> Thanks,<br>
> Thierry<br>
><br>
> Le mar. 23 janv. 2018 13:56, Timothy Pearson<br>
> <<a href="mailto:tpearson@raptorengineering.com" target="_blank">tpearson@raptorengineering.com</a>><br>
> a écrit :<br>
><br>
>> -----BEGIN PGP SIGNED MESSAGE-----<br>
>> Hash: SHA1<br>
>><br>
>> 4 cores, SMT4. There's an 8-core available for $190 more, and AFAIK<br>
>> there are plans to start offering an 18-core server chip very shortly.<br>
>><br>
>> These are the OpenPOWER machines, so there is hardware virtualization<br>
>> support (including I/O passthrough) that works well with kvm and QEMU.<br>
>> I haven't really heard anything referred to as "LPAR" on these newer<br>
>> POWER8/POWER9 machines outside of legacy documents.<br>
>><br>
>> On 01/23/2018 12:47 PM, ron minnich wrote:<br>
>> > how many cores is that? Does it come with LPAR?<br>
>> ><br>
>> > On Mon, Jan 22, 2018 at 9:48 PM <a href="mailto:Taiidan@gmx.com" target="_blank">Taiidan@gmx.com</a><br>
>> <mailto:<a href="mailto:Taiidan@gmx.com" target="_blank">Taiidan@gmx.com</a>><br>
>> > <<a href="mailto:Taiidan@gmx.com" target="_blank">Taiidan@gmx.com</a> <mailto:<a href="mailto:Taiidan@gmx.com" target="_blank">Taiidan@gmx.com</a>>> wrote:<br>
>> ><br>
>> > In case anyone wants to know the (non-coreboot) libre firmware<br>
>> TALOS<br>
>> 2<br>
>> > single CPU/board combo is now only 2.5K.<br>
>> ><br>
>> > I still can't figure out how they managed to make it so<br>
>> affordable,<br>
>> this<br>
>> > is seriously great.<br>
>> ><br>
>> > --<br>
>> > coreboot mailing list: <a href="mailto:coreboot@coreboot.org" target="_blank">coreboot@coreboot.org</a><br>
>> > <mailto:<a href="mailto:coreboot@coreboot.org" target="_blank">coreboot@coreboot.org</a>><br>
>> > <a href="https://mail.coreboot.org/mailman/listinfo/coreboot" rel="noreferrer" target="_blank">https://mail.coreboot.org/mailman/listinfo/coreboot</a><br>
>> ><br>
>><br>
>><br>
>> - --<br>
>> Timothy Pearson<br>
>> Raptor Engineering<br>
>> +1 (415) 727-8645 (direct line)<br>
>> +1 (512) 690-0200 (switchboard)<br>
>> <a href="https://www.raptorengineering.com" rel="noreferrer" target="_blank">https://www.raptorengineering.com</a><br>
>> -----BEGIN PGP SIGNATURE-----<br>
>> Version: GnuPG v1<br>
>><br>
>> iQEcBAEBAgAGBQJaZ4U2AAoJEK+E3vEXDOFbBUEIAKxL6cD2L27yZh63OhM0TD8h<br>
>> BZD2r0nYF/NLfGi50KuMZPNzb2lpzgLHc06ZHZmJBU0sFUbTdI3WrYibDPtY4lva<br>
>> 1uG3gedN2u+sUCzTKrLILOyrstlJ2lQ4+8jxyO8PncK9Zx3LtgbSlGVGq+pvxsXI<br>
>> Ac8Yqm+de6Is8aaAHMMzaT9UNxcjXCAs/zZm3iWcPkA2B0CVVUoKnsFuhtGG1cGd<br>
>> j4bukGJrojkUMEFxIG93qphcurdP2AjuvOaUdZVuoC0uxdVL2az77SgRUH8Vmxdd<br>
>> SFhAzG7j4LsqGMwiZBkubBZpSMPj6kPyRQUIxwwAk/vRLpOxoPdaEbrI/9wyIaM=<br>
>> =PFaf<br>
>> -----END PGP SIGNATURE-----<br>
>><br>
>> --<br>
>> coreboot mailing list: <a href="mailto:coreboot@coreboot.org" target="_blank">coreboot@coreboot.org</a><br>
>> <a href="https://mail.coreboot.org/mailman/listinfo/coreboot" rel="noreferrer" target="_blank">https://mail.coreboot.org/mailman/listinfo/coreboot</a><br>
>><br>
><br>
<br>
<br>
</blockquote></div>