On 08/29/2017 02:24 PM, Timothy Pearson wrote:
Let me know what you think of the OpenBMC system. We're considering
allowing bugs to be tracked on GitHub; is this something the community
wants to see or would a separate Bugzilla type install be preferred? We
want to provide the infrastructure
NOTE: I have no idea as to how trustworthy these companies are.
http://www.officespecialties.com/asus_computer_international_kcma_d8_server_motherboard_217195_prd1.htm?pSearchQueryId=420212
Ah even better, $250 and now one doesn't have to support a chinese owned
newegg.
On 08/30/2017 12:58 AM, Philipp Stanner wrote:
Am 29.08.2017 um 20:15 schrieb Timothy Pearson:
On 08/29/2017 06:10 AM, Rene Shuster wrote:
Wow.
My favorite part is where the NSA itself basically admits that the ME
can't be trusted! I wonder if they are looking at other architectures
or if
Am 29.08.2017 um 20:15 schrieb Timothy Pearson:
> On 08/29/2017 06:10 AM, Rene Shuster wrote:
> > Wow.
>
> My favorite part is where the NSA itself basically admits that the ME
> can't be trusted! I wonder if they are looking at other architectures
> or if this HAP bit was enough for their needs?
I can't download the .pdf file for some reason (maybe the tla's got to it?)
http://fm.csl.sri.com/LAW/2009/dobry-law09-HAP-Challenges.pdf
can someone send it to me?
Thanks
Thoughts:
Sad this is still not an actual method of disablement, but it doesn't
really matter as anyone who buys *new* x86
OK, thanks for the clarification.
On Tue, Aug 29, 2017 at 4:13 PM, Timothy Pearson <
tpear...@raptorengineering.com> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 08/29/2017 02:57 PM, Leah Rowe wrote:
> >
> >
> > On 29/08/17 19:15, Timothy Pearson wrote:
> >> On 08/29/2017
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/29/2017 02:57 PM, Leah Rowe wrote:
>
>
> On 29/08/17 19:15, Timothy Pearson wrote:
>> On 08/29/2017 06:10 AM, Rene Shuster wrote:
>>> Wow.
>
>> My favorite part is where the NSA itself basically admits that the
>> ME can't be trusted! I
http://fm.csl.sri.com/LAW/2009/dobry-law09-HAP-Challenges.pdf (linked in
PTSecurity's blogpost) might have the answer to your question, but it's not
accessible for me.
On Tue, Aug 29, 2017 at 3:57 PM, Leah Rowe wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 29/08/17 19:15, Timothy Pearson wrote:
> On 08/29/2017 06:10 AM, Rene Shuster wrote:
>> Wow.
>
> My favorite part is where the NSA itself basically admits that the
> ME can't be trusted! I wonder if they are looking at other
> architectures
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We are pleased to announce that the OpenBMC port for the KGPE-D16 has
reached the first release stage!
https://www.raptorengineering.com/coreboot/kgpe-d16-bmc-port-status.php
While it has inherited some of the rough edges of its Facebook
predecessor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/29/2017 06:10 AM, Rene Shuster wrote:
> Wow.
My favorite part is where the NSA itself basically admits that the ME
can't be trusted! I wonder if they are looking at other architectures
or if this HAP bit was enough for their needs?
- --
Hi,
Please find the latest report on new defect(s) introduced to coreboot found
with Coverity Scan.
1 new defect(s) introduced to coreboot found with Coverity Scan.
New defect(s) Reported-by: Coverity Scan
Showing 1 of 1 defect(s)
** CID 1380036: Control flow issues (NO_EFFECT)
Wow.
On Mon, Aug 28, 2017 at 12:08 PM, Matthias Gliwka wrote:
> Some new development on disabling Intel ME 11: http://blog.ptsecurity.
> com/2017/08/disabling-intel-me.html
>
> Kind regards,
> Matthias Gliwka
>
> --
> coreboot mailing list: coreboot@coreboot.org
>
Hello Vincenzo,
Since you replied only to me, I would like to write my reply also to the
whole list, in order to draw some more experienced people with INT 13H
knowledge.
Explicitly, I do not know with 100% certainty if OSes direct via INT 13H
some data to be written to the USB and/or SATA. It
14 matches
Mail list logo