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/
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/
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/
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/
Agreed - add another 100k to that just to get anybody worth a shit in the Atlanta market.... where the cost of living is dirt cheap compared to living in Mountain View.
If you got some Java - try your hand at Scala. Huge market demand is building over the new few years expect it to explode. We still have a few slots left open at TST:
We release on average twice a week at a new startup funded by AAA - heavy DevOps shop with fast developing online travel product suite (www.tstllc.net).
Infrastructure runs on a mix of local private cloud and public cloud. MySQL replication between the two geographically different locations. Only 1 site takes traffic at a time. Replication is stopped before a push, new code deployed to cold site, automated QA testing verifies code site updates are working correctly, traffic gets flipped across datacenters via DNS Failover (see dnshat.com for example), backup site goes hot, release is pushed to other site, verified, traffic shifted back to primary site again via DNS Failover, and lastly replication is resumed. Replication is stopped only if there are schemas changes that prevent the new release from going live with replication running (rare now we have the Devs up to speed on the failover architecture). Pushes are done via automated scripts - Java/Scala/Play apps. Total release time 1 hour - smooth as butter - transparent to site visitors and AAA club clients pulling webservices to their automated backend systems (we make sure their backend systems obey's DNS TTLs like end user browsers so that the release failovers are transparent).
Within a year the whole thing will automated for multiple releases per day if needed.
There is a child molester serving 60+ years for aggrevated child molestation against my oldest step daughter. That child molestors mother - the grandmother that raise the evil bastard - is out for revenge for her son being convicted.
She stalked my wife through 3rd parties on facebook. One day someone is irriated with their firefighter job and post a stupid 1 liner the read: "Ever feel like blowing something up?" in a Facebook post.
My wife - after years of harrasment by the evil child molestor's grandmother - posts back "lol 43 joe chambers rd lol". The evil grandmother prints it out - takes it to the local courthouse - and shows a judge getting him to sign off on issuing a terroristic threat warrant against my wife over that remark. The firefighter joking about blowing up was not arrested - but wife was. In front of her children - sheriff's show up one night and arrest her and haul her off to jail charged with a Felony terroristic threat. The county issuing the warrant was half a state away - so she was held in the local prison awaiting transfer - no bond could be issued on the terroristic threat warrant - so she was held indefinitely waiting on a transfer to take place at some future date to get her to the county issuing the warrant before she could see a judge to have bail set.
Fuck Facebook. Fuck our Justice System. Fuck that ignorant judge that signed the warrant (now unemployed - he got arrested for DUI and lost his seat).
True story - never made the news - no one gives a shit.
Yay - and I've been reading for all them - just check my low id number.
Now - when who do I have to payoff to fix my karm which as been stuck at Terrible with -1 posts for the last 10 of those 15 years despite having done nothing except read like a regular user should - way to treat us old timers.
Given that Apple has turned into the most Evil Patent Foce on the planet - if you had it to do over again and the result would be the same wealth for you personally - would you choose with this hypothetic foresight to have created a company with a legacy more in line with your own hacker values (hence necessitating the exclusion of Steve - or do you still value that friendship enough to not regret said evil legacy)?
Slashdot Mirror
"said Bastian Hacker, a researcher at the Max Planck" nevermind, lmao.
ok, wtf does this mean?
Mostly CIA dude lol
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/
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/
Good info - but... dated 2018. I don't trust "non-durable media" anymore :(
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/
Yup, because their Remote Viewing skills are so much more advanced than our own. Probably the alien DNA.
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/
And still keep reading.
in like 10 years lol
That's was my experience too - and exactly what I did. I quadrupled though.
Agreed - add another 100k to that just to get anybody worth a shit in the Atlanta market.... where the cost of living is dirt cheap compared to living in Mountain View.
If you got some Java - try your hand at Scala. Huge market demand is building over the new few years expect it to explode. We still have a few slots left open at TST:
https://www.tstllc.net/careers#Software_Developer
We release on average twice a week at a new startup funded by AAA - heavy DevOps shop with fast developing online travel product suite (www.tstllc.net).
Infrastructure runs on a mix of local private cloud and public cloud. MySQL replication between the two geographically different locations. Only 1 site takes traffic at a time. Replication is stopped before a push, new code deployed to cold site, automated QA testing verifies code site updates are working correctly, traffic gets flipped across datacenters via DNS Failover (see dnshat.com for example), backup site goes hot, release is pushed to other site, verified, traffic shifted back to primary site again via DNS Failover, and lastly replication is resumed. Replication is stopped only if there are schemas changes that prevent the new release from going live with replication running (rare now we have the Devs up to speed on the failover architecture). Pushes are done via automated scripts - Java/Scala/Play apps. Total release time 1 hour - smooth as butter - transparent to site visitors and AAA club clients pulling webservices to their automated backend systems (we make sure their backend systems obey's DNS TTLs like end user browsers so that the release failovers are transparent).
Within a year the whole thing will automated for multiple releases per day if needed.
Not my style. Forgiveness is for you, not the other person. I shouldn't even have posted this - let my anger slip on me.
Btw - this was in Georgia, the United States - so take that whole Freedom of Speech shit we supposedly have here with a grain of salt.
There is a child molester serving 60+ years for aggrevated child molestation against my oldest step daughter. That child molestors mother - the grandmother that raise the evil bastard - is out for revenge for her son being convicted.
She stalked my wife through 3rd parties on facebook. One day someone is irriated with their firefighter job and post a stupid 1 liner the read: "Ever feel like blowing something up?" in a Facebook post.
My wife - after years of harrasment by the evil child molestor's grandmother - posts back "lol 43 joe chambers rd lol". The evil grandmother prints it out - takes it to the local courthouse - and shows a judge getting him to sign off on issuing a terroristic threat warrant against my wife over that remark. The firefighter joking about blowing up was not arrested - but wife was. In front of her children - sheriff's show up one night and arrest her and haul her off to jail charged with a Felony terroristic threat. The county issuing the warrant was half a state away - so she was held in the local prison awaiting transfer - no bond could be issued on the terroristic threat warrant - so she was held indefinitely waiting on a transfer to take place at some future date to get her to the county issuing the warrant before she could see a judge to have bail set.
Fuck Facebook. Fuck our Justice System. Fuck that ignorant judge that signed the warrant (now unemployed - he got arrested for DUI and lost his seat).
True story - never made the news - no one gives a shit.
Yay - and I've been reading for all them - just check my low id number.
Now - when who do I have to payoff to fix my karm which as been stuck at Terrible with -1 posts for the last 10 of those 15 years despite having done nothing except read like a regular user should - way to treat us old timers.
Given that Apple has turned into the most Evil Patent Foce on the planet - if you had it to do over again and the result would be the same wealth for you personally - would you choose with this hypothetic foresight to have created a company with a legacy more in line with your own hacker values (hence necessitating the exclusion of Steve - or do you still value that friendship enough to not regret said evil legacy)?
Same here for servers since 97.
+ -> Ubuntu for laptops/desktops in the last 6 years
I'm still smart and I'm like almost 40 I think
Now I have to find a new datacenter to store all of my backups in.
No seriously - how would one go about getting one of those government contracts?
.... in my pants!