[ 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: 54 KB, 679x758, 1489898569240.jpg [View same] [iqdb] [saucenao] [google] [report]
64135793 No.64135793 [DELETED]  [Reply] [Original] [archived.moe] [rbt]

>i-it affects AMD t-too goy!
Shills are in maximum overshill tonight

>> No.64135822

Your Arm chip also effected, intel goin full shill now

>> No.64135832

It does though.

>> No.64135866

Show me a non-jewish source

>> No.64135944

take it to pol, tks.

>> No.64135972

Look at "Spectre"

It affects AMD but is no where near as severe as intel though.

>> No.64136009
File: 65 KB, 679x711, 9420c28dfe6b7091082fc32f52eec3a3fdf08140d95e18c2d3e.jpg [View same] [iqdb] [saucenao] [google] [report]

only in linux

>> No.64136019

t.schlomo intelstein

>> No.64136022

nice "source", moron

>> No.64136053

Also only fx pro and Apu line is affected by specter 1

>> No.64136119

Go Blue Team!

>> No.64136157

So if I notice a (((coincidence))) I must be a Nazi? Great mental gymnastics you got there bro.

>> No.64136169

>Shills are in maximum overshill tonight
haha yeah they are, it's definitely entertaining.

>> No.64136174
File: 18 KB, 304x293, 1510512770188.jpg [View same] [iqdb] [saucenao] [google] [report]


are you a Nazi?

>> No.64136178
File: 18 KB, 267x297, 1499956370954.jpg [View same] [iqdb] [saucenao] [google] [report]


>> No.64136201

No I'm Hitler

>> No.64136202

LOL this. seeing it in every thread, its probably one butthurt intel shill

>> No.64136241

That's not good

>> No.64136245

Really? I've heard Ryzen was affected, but I can't confirm that source.

>> No.64136270

the source is from intel, what expected

>> No.64136285

I'm seeing the exact same fake news pics and sentences being posted in every single thread, intlel shills aren't even trying to be subtle anymore.

>> No.64136305

But yet everyone shills about it in the threads about Meltdown (the one that doesn't affect AMD)

>> No.64136925

Oh yea, they must paying out big bucks to lump all these exploits together. That way they can make it out that they're being picked on. "We're all affected guys."

Mind you, AMD hasn't come out and straight up said "We're safe" yet which makes me wonder if they're still looking into it.

>> No.64136952

>Mind you, AMD hasn't come out and straight up said "We're safe" yet which makes me wonder if they're still looking into it.

Spectre V1 and Meltdown are 100% safe.
Spectre V1 requires a patch, no impact on performance.
Meltdown can't touch them at all, no fix needed.

Spectre V2 is <1% chance of being a thing, but they're looking into it.

>> No.64137104

If you read what they say its "near zero" and "absolutely zero". By all accounts the performance-robbing one is the one they are completely safe from, though.

>> No.64137118

>Almost every system is affected by Spectre: Desktops, Laptops, Cloud Servers, as well as Smartphones. More specifically, all modern processors capable of keeping many instructions in flight are potentially vulnerable. In particular, we have verified Spectre on Intel, AMD, and ARM processors.


>> No.64137168

Spectre is insanely difficult to exploit, and impossible to patch; so no performance drops.

Meltdown (which only affects Intel) is easy to exploit, incredibly dangerous, and patching it means a 30% performance hit.

>> No.64137193

It's compiled from project zero paper

>> No.64137195


>> No.64137196
File: 10 KB, 320x180, ULuuxpcm.jpg [View same] [iqdb] [saucenao] [google] [report]

>tfw the botnet doesn't want me to fly

>> No.64137204

Spectre and Meltdown are both needed to exploit.
Meltdown can only read data while Spectre can inject data.

>> No.64137235

So AMD is also safe from Spectre?

>> No.64137237

You don't need to write data to steal information.

>> No.64137254

Spectre by itself is not a major threat, it's software patchable with little perf penalty, and difficult to exploit.

Meltdown is a huge problem. AMD doesn't have the Meltdown problem. That quoted sentence seems like they want to imply that AMD is as fucked as Intel, but if AMD is free from Meltdown, then it should be in the clear.

>> No.64137260

Sure, if you want to steal and nothing else, then Meltdown is perfect tool for that, but if you want to inject something, then both of the exploits are necessary
so far, nobody has provided any proof that you can inject data to AMD, if it's safe or not is to be seen.

>> No.64137263



>> No.64137290

>huge problem
Do you run servers or virtual machine? Exploits are always been found and patched dude. You do you care now?

>> No.64137300

Why do you*

>> No.64137331

This isn't specific to either of those though. The flaw is with virtual memory not virtual machines

>> No.64138210
File: 47 KB, 649x280, IntelKilledWithOneGitMerge.jpg [View same] [iqdb] [saucenao] [google] [report]

Used to be only on linux
Not anymore

>> No.64138658

doesnt this count as insider trading?

>> No.64139170

is my 3570k gonna be okay?

>> No.64139310


Are you imbecile or what? What part you cannot understand? EVERY Intel processor from the past 10 year is effected. C2D, i series, most of the Atoms. Would you need to worry? Yes, you would, because a browser with enabled javashit can steal data from kernel space (crypto keys, passwords, everything). Will the os patch correct this? Yes it would, but with performance penalty. AMD effected? Yes, and no. It can be if programmers don't exclude AMD processors from the patched code.

>> No.64139341
File: 10 KB, 192x204, 1513614088110.jpg [View same] [iqdb] [saucenao] [google] [report]


>> No.64139393

Wouldn't that require the browsers to allow for that?
I mean, wasn't this what rust is supposed to mitigate? (Not allow overflows and not have undefined behavior)

>> No.64139529

>under non-default kernel setting

>> No.64139620


The exploit was demonstrated with javascript. No sandbox or a VM can protect you from hardware design flaws.

>> No.64139626

what u be sayin is, is that I have the freedom to fuck my shit up? wooooooow free software wins again

>> No.64139650

for you

>> No.64139917

So hypervisors are vulnerable or just guests OS?

>> No.64139988

i'm not sure if i can trust that nose.

>> No.64140147

I'm new to the party what's the uproar about?

>> No.64140200
File: 13 KB, 504x129, sponsors.png [View same] [iqdb] [saucenao] [google] [report]


>> No.64140354

>Affected by meltdown
>Performance degrading software

>> No.64140363

yup suck to be intel

>> No.64140390


>> No.64140459

is this the reason Intel's processors are faster than AMD's?

>> No.64140472


>> No.64140476

Yes it does, because he sold shares before secret information that can affect share price went public. It's the same thing as if he dumped his stack before a negative quarterly report.

>> No.64140492

Oy vey! Oy gevalt! The Chutzpah of these Goyim! This is anudda shoah! By the Protocols! Alert the Elders! Get Mossad! The Goyim Know! Shut it Down!

>> No.64140558

>software gimping
i think so

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