Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×

Comment Vladimir Pentkovski did it Intel named Pentium @ (Score -1) 126

The research that lead to our public awareness of all of this was first published 6/27/2017. Appears to have been partially funded under DARPA Contract #FA8650-16-C-7622 (looking for attacks to fully recover private RSA keys). Our side and partners were funding research into recovering SSH private keys in a cloud environment. Same DARPA Contract # is listed under acknowledgements on https://meltdownattack.com/.

That DARPA Contract # lead to the research that was first published on 6/27/2017 by the international association of cryptology researchers here:
https://eprint.iacr.org/2017/627.pdf

This research was then used by various security interests to develop the proof of concept code for our side to exploit speculative-execution as a security vulnerability in early December last year.

Where did speculative-execution come from originally if the public story is Intel invented it? It came from the Russian military. They developed it 20 years before they weaponized it on us. Only known specter exploits can be patched...

We can all thank Vladimir Pentkovski for bringing speculative execution to Intel processors... and compromising our national security:
https://www.theregister.co.uk/1999/06/07/intel_uses_russia_military_technologies/

Comment Vladimir Pentkovski did it Intel named Pentium @ (Score -1) 126

This will also get modded down because they don't want anyone to read this links and connect these dots - but fwiw

The research that lead to our public awareness of all of this was first published 6/27/2017. Appears to have been partially funded under DARPA Contract #FA8650-16-C-7622 (looking for attacks to fully recover private RSA keys). Our side and partners were funding research into recovering SSH private keys in a cloud environment. Same DARPA Contract # is listed under acknowledgements on https://meltdownattack.com/.

That DARPA Contract # lead to the research that was first published on 6/27/2017 by the international association of cryptology researchers here:
https://eprint.iacr.org/2017/627.pdf

This research was then used by various security interests to develop the proof of concept code for our side to exploit speculative-execution as a security vulnerability in early December last year.

Where did speculative-execution come from originally if the public story is Intel invented it? It came from the Russian military. They developed it 20 years before they weaponized it on us. Only known specter exploits can be patched...

We can all thank Vladimir Pentkovski for bringing speculative execution to Intel processors... and compromising our national security:
https://www.theregister.co.uk/1999/06/07/intel_uses_russia_military_technologies/

Comment Vladimir Pentkovski did it Intel named Pentium @ (Score -1) 79

The research that lead to our public awareness of all of this was first published 6/27/2017. Appears to have been partially funded under DARPA Contract #FA8650-16-C-7622 (looking for attacks to fully recover private RSA keys). Our side and partners were funding research into recovering SSH private keys in a cloud environment. Same DARPA Contract # is listed under acknowledgements on https://meltdownattack.com/.

That DARPA Contract # lead to the research that was first published on 6/27/2017 by the international association of cryptology researchers here:
https://eprint.iacr.org/2017/627.pdf

This research was then used by various security interests to develop the proof of concept code for our side to exploit speculative-execution as a security vulnerability in early December last year.

Where did speculative-execution come from originally if the public story is Intel invented it? It came from the Russian military. They developed it 20 years before they weaponized it on us. Only known specter exploits can be patched...

We can all thank Vladimir Pentkovski for bringing speculative execution to Intel processors... and compromising our national security:
https://www.theregister.co.uk/1999/06/07/intel_uses_russia_military_technologies/

Comment Russians did it! lol Intel named Pentium @ him? (Score -1) 99

Previous RV (Remote Views) left me thinking it was everything for the last 5 years at least that was hardware compromised by our side. I didn't even think about RV'ing for the other side. Additional sessions have lead me to believe that everything on our side has been hardware compromised for over the last 20 years by the Russian military.

Here are the following dots to connect for an RV confirm:

The research that lead to our public awareness of all of this was first published 6/27/2017. Appears to have been partially funded under DARPA Contract #FA8650-16-C-7622 (looking for attacks to fully recover private RSA keys). Our side and partners were funding research into recovering SSH private keys in a cloud environment. Same DARPA Contract # is listed under acknowledgements on https://meltdownattack.com/.

That DARPA Contract # lead to the research that was first published on 6/27/2017 by the international association of cryptology researchers here:
https://eprint.iacr.org/2017/627.pdf

This research was then used by various security interests to develop the proof of concept code for our side to exploit speculative-execution as a security vulnerability in early December last year - with Intel only informing Microsoft. From what I can tell internally AWS blindsided. This was not a controlled disclosure afaik from RV sessions.

Now shit gets real. Where did speculative-execution come from originally if the public story is Intel invented it. From additional RV session work I believe: It came from the Russian military. They developed it 20 years before they weaponized it on us. Only known specter exploits can be patched...

Can we all thank Vladimir Pentkovski for bringing speculative execution to Intel processors?
https://www.theregister.co.uk/1999/06/07/intel_uses_russia_military_technologies/

Slashdot Top Deals

Keep your boss's boss off your boss's back.

Working...