[ 3 / biz / cgl / ck / diy / fa / g / ic / jp / lit / sci / tg / vr / vt ] [ index / top / reports / report a bug ] [ 4plebs / archived.moe / rbt ]

Due to resource constraints, /g/ and /tg/ will no longer be archived or available. Other archivers continue to archive these boards.Become a Patron!

/g/ - Technology

View post   

[ Toggle deleted replies ]
File: 332 KB, 800x522, file.png [View same] [iqdb] [saucenao] [google] [report]
64148148 No.64148148 [Reply] [Original] [archived.moe] [rbt]

Did AMD foresee Intelgate?

>20 June 2017

>> No.64148162

>According to researchers, Intel and other chip makers were informed June 1, 2017

>the filing also notes that Krzanich adopted the plan just a month before the sales, on Oct. 30, 2017.

>> No.64148232
File: 135 KB, 831x767, file.png [View same] [iqdb] [saucenao] [google] [report]

>the filing also notes that Krzanich adopted the plan just a month before the sales, on Oct. 30, 2017.

>> No.64148432

i really really really like your pic
do you mind if i save it?

>> No.64148459

please send royalties to intel's bank in Israel before using it

>> No.64148542

thx lauren, i'll pay my INTELaviv taxes soon

>> No.64149876

They knew, something was definitely up.






>> No.64149946

There is no way not even one team somewhere in the world did not found this in the last 20 years.
Putting backdoors on everything makes sense if you know you can memory dump whenever you want it.

>> No.64149962

simply epyc

>> No.64149971

Why the fuck is everything called SomethingGate?
What if you decide you no longer like Bill Gates, would that be BillGatesGate?

>> No.64149975

NSA, CIA and FBI were certainly aware of it and used it.

>> No.64149982

SEV needs PSP right?

>> No.64150344


>> No.64150438


>> No.64150544

>mfw a bug in the physical design of transistors is discovered in the future

>> No.64150737

no. 3ds

>> No.64151499

Because Intel literally left the gate open to hackers, and surveillance agencies

>> No.64151539

What if they left it open non-literally?

>> No.64152232

wouldn't surprise me, they are incompetent

>> No.64152286

SEV doesn't solve Spectre, albeit it may come in handy in datacenters.

>> No.64152595


Wait this was presented at blackhat 2016? Yeah there is no way scripts aren't out there taking advantage of this exploit. Intel dun goofed hard.

>> No.64152702

watergate, you fucking idiot

>> No.64152831

Doubt it. Why was there nothing in the snowden NSA leaks or the wikileaks CIA leaks?

>> No.64152921

yeah, that doesn't make it not fucking retarded

>> No.64153038

no but it does make you fucking retarded for not figuring it out yourself.

>> No.64153106

Holy shit. Fuck off back to pol and flatearth society.

>> No.64153132

Because it's the kind of leaks that you use to spy on other countries not on fellow burgers.

>> No.64153153

>Implying those leaks are the alpha and the omega of top secret stuff.
It's just the top of the iceberg.

>> No.64153420

AMD architecture does solve Spectre, so who fucking cares?

>> No.64153525

>AMD architecture does solve Spectre

No, it does not. Drop AMD and Intel press releases and read the fucking advisories. There's NO FIX for Spectre, only mitigation, and it affects AMD as well.

>> No.64153601


At worst SPECTRE on AMD allows a process to read it's own memory, unlike on Intel which allows userspace processes to access other processes memory. Not even in the same class of fault and that's not even counting MELTDOWN.

>> No.64153646

This mess just shows the sad state of IT security.

Meanwhile most middle managers/HR will now get one "security guy" to "look at the situation" for a month and then promptly tell him to fuck off, until the next fuckup happens.

>> No.64153677

>As a result, an unprivileged attacker could use these two flaws to read privileged memory by conducting targeted cache side-channel attacks. These variants could be used not only to cross syscall boundary (variant 1 and variant 2) but also guest/host boundary (variant 2).
nice try though

>> No.64153744

Those are speculations you're pulling out of your ass, except the factually correct statement that "Meltdown" != "Spectre" (no shit). AMD and Intel are both affected by Spectre to the same degree and Spectre has NO FIX no matter how hard we pretend there's one. The only fix will be a future CPU replacement. Techs like the referenced SEV allow to "harden" against Spectre in the VPS industry at best (guest/host relationship). This doesn't solve the Spectre vulnerability for each single machine (whether virtual or not) at all.

>> No.64153752


Not shown to work on AMD, confirmed by AMD engineers that it cannot work. Targeted cache side-channel attack is MELTDOWN. Nice try though intel fan.

>> No.64153797

as if they had a choice in the matter.

>> No.64153816


Nobody has proven or shown SPECTRE accessing privileged or segregated process memory on AMD, which confirms AMD's assertion that it's not affected. You're the one desperately trying to pull facts out of your ass but you have no proof, provide the proof.

>> No.64153868

Drop the press releases and fucking read the advisories. The only thing AMD engineers can assure you is that Meltdown won't affect AMD. No shit.

>which confirms
Does not confirm, at all. Read the fucking papers and the fucking advisories.

>> No.64153922

Spectre is a smokescreen by Intel trying to desperately associate AMD with the meltdown attack. Besides being way worse on Intel, spectre is something that was advised over six months ago and Intel shills have shotgunned it around as it's nominally related to the meltdown class of attack.

If you see anyone mention spectre, they are an intel shill spreading fake news to try and associate AMD with this disaster.

>> No.64154023


I read the advisories, at worst AMD is able to give a process access to its own memory. Provide proof otherwise or kys shill.

>> No.64154090

There are PAID intel shills in this forum and on every other one across the net. Intel payolla outlets Anandtech, Tom's Hardware and Arstechnica have all consulted their Intel contacts and VERY late published FAKE NEWS articles letting Intel off the hook. But not every tech site takes large cheques from Intel...

If anyone here mentions 'SPECTRE', they are an Intel shill. Spectre is an 'exploit' that has no proven attack vector on AMD Ryzen parts, and the THEORETICAL vectors are simply patched on AMD with no performance hit. On Intel, Spectre CANNOT be patched, however. Either way, spectre is another TRIVIAL and insignificant bug- of which many thousands have already been dealt with on both AMD and Intel.

It is MELTDOWN that is the only issue that matters. Meltdown describes the NSA backdoor built into every Intel CPU designed to allow user code ring-0 access. This is an ARCHITECTURAL design of intel's CPU's, and cannot be fixed except by flushing and state resetting before EVERY virtual memory/IO operation- a massive slowdown of key functionality.

AMD's memory architecture is completely different, and does NOT allow this NSA requested attcak vector- not now, not ever.

Linux has gone crazy cos the exploit is a clear NSA backdoor, which Linux types will not accept. Microsoft, as an OS, is riddled with NSA exploits by Microsoft, so doesn't need a CPU hardware vector. Thus MS can happily patch the hole (on Intel only) at the cost of significant performance degradation on all mutli-core mulit-app use cases (which excludes most current games).

Intel cannot have a 'fixed' CPU til the end of 2019 at the earliest. Roadmapped Intel parts (like icelake) all have this NSA backdoor.

There is ZERO AMD issue - indeed AMD Ryzen is the future, just as the original AMD64 was the future when intel was shilling for the broken hopeless netburst design.

>> No.64154126

How do I get paid by Intel to shill, I'm tired of doing it for free.

>> No.64154188

this anon speaks clearly and truthfully.

>> No.64154192


>> No.64154196

Even if it did apply to AMD, EYPC has a further mitigation against these kind of memory leaks with their transparent memory encryption preventing crosstalk between VMs, which in itself is worth more than anything else considering the amount of holes hypervisors have had in the past.

>> No.64154326

>I read the advisories, at worst AMD is able to give a process access to its own memory.

That's factually wrong (that you read advisories, and that a process on AMD has access to its own memory). What you're describing isn't even remotely the flaw defined in advisories and papers and completely negates the flaw. Stop pulling shit out of your ass once and for all.

>> No.64154347

What a fucking load of fucking memes.

>> No.64154447


Wow you're getting desperate. KYS.

>> No.64154603
File: 69 KB, 645x729, _.png [View same] [iqdb] [saucenao] [google] [report]

>Wow you're getting desperate. KYS.
I seriously can't tell if you're a shill or just pic related. Everything in advisories and in papers negates easily everything you say, yet you feel the need to spew bullshits on 4chan for hours on end.

>> No.64154690
File: 212 KB, 793x307, zero risk.png [View same] [iqdb] [saucenao] [google] [report]


OK then, post the specific bit where AMD is implicated. Here we see Google clearly stating that AMD isn't affected.

>> No.64155178
File: 45 KB, 443x243, 1341548482929.jpg [View same] [iqdb] [saucenao] [google] [report]

Bootlicker detected.

>> No.64155903

Fixing 2006 in 2016

Choose one.

They just ware kind of not telling that intel have cancer until it died.

>> No.64156006

never interrupt your enemies from making a mistake.

Name (leave empty)
Comment (leave empty)
Password [?]Password used for file deletion.