Quantcast
[ 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: 3.97 MB, 7000x7000, intel_collage.jpg [View same] [iqdb] [saucenao] [google] [report]
64172491 No.64172491 [Reply] [Original] [archived.moe] [rbt]

Intel Meltdown thread

I just bought a 1700.

PNG version in case someone wants to make it bigger and add stuff to it: https://chiru.no/u/intel_collage.png

>> No.64172520

cant wait for india to become a super power

>> No.64172540 [DELETED] 
File: 45 KB, 200x200, 1506977929561.png [View same] [iqdb] [saucenao] [google] [report]
64172540

>>64172491
This thread is anti-semitic

>> No.64172554
File: 127 KB, 600x600, 1515188294026.gif [View same] [iqdb] [saucenao] [google] [report]
64172554

>> No.64172575
File: 3.91 MB, 7000x7000, intel_collage.jpg [View same] [iqdb] [saucenao] [google] [report]
64172575

>>64172491

>> No.64172576
File: 58 KB, 700x700, 1515172583446.jpg [View same] [iqdb] [saucenao] [google] [report]
64172576

>> No.64172582

>>64172491
Hey guys i just got a fresh new I5 family cpu what's going on here?

>> No.64172597
File: 197 KB, 700x700, 525.png [View same] [iqdb] [saucenao] [google] [report]
64172597

>>64172576

>> No.64172603
File: 145 KB, 1500x1054, jer01nov14BAZ.jpg [View same] [iqdb] [saucenao] [google] [report]
64172603

>>64172491
Intel is literally Israeli.

Brian Krzanich is literally a Jew.

All of this shit is subversive Jewish backdoors.

>> No.64172607
File: 98 KB, 1500x1054, Nv1ChCu.jpg [View same] [iqdb] [saucenao] [google] [report]
64172607

>> No.64172672
File: 403 KB, 495x500, 1503025840893.png [View same] [iqdb] [saucenao] [google] [report]
64172672

>> No.64172777

>>64172603
What OS do the Jews use? ShlomOS, Gnuberg, Temple 3, linux?

>> No.64172790

>>64172540
>>64172576
>>64172597
>>64172603
It's not surprising to see /pol/ latching on to overblown news.

>> No.64172945

Is this going to affect multiplayer servers on video games at all? No idea what that sized machine looks like but would be a shitty side effect if any are built around Intel.

>> No.64173097

>>64172790
>if it hurts my feelings, it must be /pol/

kek

>> No.64173161

Who AMD non-Zionism master race here?

>> No.64173191
File: 3.99 MB, 8000x8000, intel_collage.jpg [View same] [iqdb] [saucenao] [google] [report]
64173191

>> No.64173214

We must make this event conform to nazi ideals such that we can subvert /g/ to our glorious struggle!!!

>> No.64173230

amd doesn't have the 30% performance loss that intel has
all intel cpus since 1995 are affected
no amd cpus are affected from meltdown
spectre bugfix is a regular non-intrusive bugfix

>> No.64173344

So how the fuck do I patch against this shit? I'm on windows 10 ltsb and after installing the latest update some tool still says I'm vulnerable. The other thread says that it has to be manually enabled, but there were still people who are vulnerable after performing the registry voodoo magic. Then someone said that you actually need a patch from your hardware vendor.

Why is there no clear way to patch against this? Does antivirus break the patch? Which antivirus and how? Does the patch need to be manually enabled? How many patches do we need? When can we expect them to get released?

>> No.64173406

JUST REPORTED ON NBC NIGHTLY NEWS

NORMIES OFFICIALLY KNOW

INTEL IS FINISHED RIP

>> No.64173418
File: 420 KB, 1493x1153, speccy_ryzen.jpg [View same] [iqdb] [saucenao] [google] [report]
64173418

Post your comfy Ryzen builds.

>> No.64173456

So how much of a performance hit am I expected to take on a i7 7700k? Can't find any info on this anywhere, every site just says "If your CPU is newer, expect a small hit" What the fuck is the definition of small? 10%? 5%? 1%?

>> No.64173465
File: 38 KB, 609x324, 1513084138613.jpg [View same] [iqdb] [saucenao] [google] [report]
64173465

https://youtu.be/SqbNWCehbmU

AidsMD is so sad right now, lieing about nvidia , and the shill pcbg that says avoid intel... why not avoid nvidia too you faggots and listen to your own propaganda

>> No.64173495

>>64173418

Is Windows 10 as bad as everyone says? I have Enterprise torrented and I'm currently saving all my stuff onto my hard drive that I want to keep. I've had Windows 7 for seven years and kind of want to at least try Windows 10.

I'd switch to linux but ARMA 3.

>> No.64173557

>>64173495
It requires more work than Windows 7 to get the OS to leave you alone so you can get work done or play vidya. Don't upgrade until you have to.

>> No.64173565

>>64173557

Gosh darn it. I've read it's better for gaming, though, which is why I'm looking into it in the first place.

>> No.64173626
File: 45 KB, 690x388, 1514991287541.jpg [View same] [iqdb] [saucenao] [google] [report]
64173626

Jewtel fags on suicide watch
>bbbut amd is affected too!
jewtel fags enjoy your premium priced shit chip or not net, whatever you prefer

>> No.64173769
File: 1.04 MB, 400x224, FEELS GOOD.gif [View same] [iqdb] [saucenao] [google] [report]
64173769

>>64172491
>MFW roughly 70% of pics which I made landed in OP's collage

>> No.64173823

>>64173769
https://www.youtube.com/watch?v=1Bix44C1EzY

>> No.64173903
File: 2.44 MB, 4160x2340, IMG_20180106_012918.jpg [View same] [iqdb] [saucenao] [google] [report]
64173903

>>64172491
>>64173418
Happy feelings thread :^)
>>64173769
Good work !

>> No.64173917

>>64173418
>slow ram
ouch

>> No.64173968
File: 524 KB, 1515x660, i9 Russia.jpg [View same] [iqdb] [saucenao] [google] [report]
64173968

>>64173823
>>64173903
Here's some more, famalams:

>> No.64173985
File: 947 KB, 1659x951, i9 global release.jpg [View same] [iqdb] [saucenao] [google] [report]
64173985

>>64173968

>> No.64173996

>>64173917
you are missing that this is probably quad channel ram so 4x 1064 MHz = 4256 MHz with CL15 Low Latency

>> No.64174015
File: 67 KB, 800x552, 1515171911876.jpg [View same] [iqdb] [saucenao] [google] [report]
64174015

>>64173985

Also add this, naturally:

>> No.64174152 [DELETED] 
File: 52 KB, 679x758, 1495936060019.jpg [View same] [iqdb] [saucenao] [google] [report]
64174152

>>64172790

>> No.64174314

>>64173097
No it's the antisemitism.

>> No.64174337
File: 1.41 MB, 1183x900, ader1.png [View same] [iqdb] [saucenao] [google] [report]
64174337

>don't go on /g/ for five days
>come back to this
What's going on?

>> No.64174348

>>64174337
Intel fucked up again

>> No.64174357

>>64172790
your tears are delicious intlet

>> No.64174360

>>64172491
...there's also Spectre...

>> No.64174370

>>64174337
>Can someone give me a quick rundown/summary?
Intel has a massive security bug affecting everything they shitted out in last 10 years.
AMD is absolutely flawless, completely unaffected.
Security patches got released. Security """""(((patches)))""""" create performance drop anywhere from 30% to 67%.
Patch affects syscalls directly.
Nvidia's video cards don't have internal syscall module and heavily rely on external syscalls from OS, thus potentially making nVidia cards susceptible to performance drops and being essentially compromised even if paired with an AMD CPU. Alas, this was not proven nor refuted thus far, We will see soon.
If paired with Intel CPU, however, nVidia GPUs get a 100% confirmed performance drop.
AMD is absolutely flawless, unaffected on neither the security of CPUs or performance of CPUs and GPUs. Radeon GPUs are absolutely not affected by syscall performance drops because Radeons had an internal integrated syscall module as far back as GCN 1.1, nVidia, however, deliberately got rid of them since GTX 5xx days.
Worst combination of hardware EVER starting from this point on - Intel CPU + Nvidia GPU.
Fine, but potentially compromised combination of hardware - AMD CPU + nVidia GPU (compromising is purely on nVidia's side if it ever happens, as AMD is absolutely flawless).
Absolutely flawless, impenetrable, invulnerable combination - AMD CPU + AMD GPU.
Brian Krzchanich sold several millions of Intel's stock several days before this was found out, while Intel's board of directors fully knew what was happening.
Covfefe Lake was released even though Intel already knew it was affected.
Each and EVERY Intel processor released in the last 10 years is affected.
Even if AMD encounters some future attempts at bypassing it's absolutely flawless SEV protection system, any and all potential holes can be fixed easily on software level.
Intel's holes are hardware and cannot be fixed fully.

>> No.64174394
File: 148 KB, 1173x563, unlimitedpower.png [View same] [iqdb] [saucenao] [google] [report]
64174394

>>64173418

My nigga.

>> No.64174407

>>64174394
>3.7GHz
Nigger, what the fuck? Like, come on.

>> No.64174412

>>64174370
Bugger.
I fear for my poor i5 Latitude.
Do I have to install the patch?

>> No.64174422
File: 107 KB, 576x1024, 1449725623089.jpg [View same] [iqdb] [saucenao] [google] [report]
64174422

>>64172790
(you)

>> No.64174434

>>64174412
You don't have to. But then you're bare naked to attacks from all over. It's for you to decide how to be cucked over...or not, if you move AMD.

>> No.64174437
File: 97 KB, 798x277, 1515100527122.png [View same] [iqdb] [saucenao] [google] [report]
64174437

>>64174394
>>64174407
>AMD faggots can overclock every CPU, no matter what suffix it has

>> No.64174470
File: 38 KB, 659x570, Speccy.png [View same] [iqdb] [saucenao] [google] [report]
64174470

>>64172491
Alright gents, I know there must've been a billion threads on the subject already but will you answer a brainlets question? Here are my specs, can I switch from an Intel to an AMD processor without completely fucking my computer up? I don't have much money to spend but I think I can shell out a couple extra bucks for a good processor? Yes I know my specs must be outdated but its all I have right now

>> No.64174478

>>64174434
I just got it very recently, so I'd much rather not have to replace it if possible.
Are there any laptops on par with ThinkPads and Latitudes that use AMD processors?

>> No.64174504

>>64174370
t. redteam+ shill

>> No.64174518

>>64174370

JUST

>> No.64174525

>>64174407

I've had it up over 4 on the Enermax TR360 AIO

>> No.64174546

>>64174478
A life's lesson - never fall in to kike trickery and never buy from dirty Jews ever again. You'll know better now.

>Are there any laptops on par with ThinkPads and Latitudes that use AMD processors?
Soon. Wait for after CES. First Zen APUs are almost at the door.

>> No.64174563
File: 971 KB, 484x682, JUST.png [View same] [iqdb] [saucenao] [google] [report]
64174563

>>64174504

>> No.64174594

>>64173418
what would be the equivalent to an i5 7500? processing and TDP wise.

>> No.64174596

got the urge to start a thread for this, but, kinda lazy and since this is the general.
Don't you think youtubers a bit too quiet about this all?

those retards all jumped to conclusions on every single big topic I can remember from the last 2 years, with breaking news style of vids, but now, they're all leaving it for their talk shows or not even bothering.

There are which I know never make these kinds of rushed videos, no matter what, level1tech and adoredtv, but all of the others like paulshardware, bitwit, joker, and people in their circle jerk have never failed before on topics like radeon power gate, nvidia 3.5gb meme.

>> No.64174602

>>64174594
1500X. Not equivalent, better.

>> No.64174617

>>64174596
They're all over Logan Paul right now.

>> No.64174647

>>64174596
heavy (or mid) hitters that mentioned it so far
hardware unboxed
jayz
gamers nexus
adoretv, but en passant, simply acknowledging it
pcper coincided with their talk show, so it was kinda unavoidable

doesn't that list feel a bit empty, given the impact of these news?

>> No.64174727

So /g/ looking for a new processor build. preferably 4 cores or more.

What's a good one?

>> No.64174746

>>64174647
I recall seeing techyescity thumbnail rec'ed with this topic, but I can't stand him on a personal level, don't even know for whom he shills.

>> No.64174756
File: 1.25 MB, 1002x1480, brianJustnich.png [View same] [iqdb] [saucenao] [google] [report]
64174756

>>64172491
Post more photos of JUSTnich with hair

>> No.64174770

>>64174727
1200 if homeless bum, 1400X if starving student, 1500X if jobless, 1600X if cheapskate.

>> No.64174870

idiots AMD got the patch anyways so they get lower performance also

>> No.64174881
File: 136 KB, 960x1240, 1515091967450.jpg [View same] [iqdb] [saucenao] [google] [report]
64174881

>>64174756

>> No.64174962

>>64174370
How about my Ivy-E and R9 machine?

>> No.64175019

>>64174470
You'll need an R5 1600 or R7 1700, B350 or X370 motherboard, DDR4 RAM, and an SSD.

>> No.64175037

>>64174470
You basically need to build a new pc. New mobo, ddr4.

>> No.64175108

>>64174470

You'll have to buy a new windows license too if you change your motherboard.

>> No.64175147
File: 60 KB, 397x642, Captura de pantalla (1002).png [View same] [iqdb] [saucenao] [google] [report]
64175147

How protected am I if i use Tails SO?

>> No.64175234
File: 58 KB, 716x493, Theo on intel.png [View same] [iqdb] [saucenao] [google] [report]
64175234

>> No.64175235

>>64175147
dude it is a hw bug. OS is not important.

>> No.64175254
File: 30 KB, 380x255, inteljewed.jpg [View same] [iqdb] [saucenao] [google] [report]
64175254

>yfw the goyim ruin everything

>> No.64175257

>>64175235
I didn't understand what you said.

>> No.64175380

>>64174314
are you possibly from the jewish community/culture?

>> No.64175604

>tfw you've been an amd fanboy since my phenon 955

>> No.64175622

>>64175257
it's a hardware bug. All OS is affected in some way. And Tails OS is based on Linux so if it's not using most recent Linux version, then it's affected.

>> No.64175817

>>64175108
lmao

dollar fags on suicide watch

>> No.64176068
File: 11 KB, 343x543, 1472674085267.png [View same] [iqdb] [saucenao] [google] [report]
64176068

I have a really really old i7 and I'm scared about Vladimir and friends breaking into my computer and getting all my passwords stolen.
Realistically, how likely is it that this could happen? I have no money for new parts or let alone a new computer. Consider I use it only for normie shit.

>> No.64176158

>>64176068
Just patch and you'll be fine.

>> No.64176240

>>64176158
What about the slowdown memes?

>> No.64176278

>>64176240
what do you use your PC for?
You will only be affected by operations with loads of syscalls.

>> No.64176293

>>64176158
As far as I've recollected from here, the patch can't even be enabled if the mobo's BIOS isn't updated first to make it able to adapt and enable it.
I do have the patch but Silverlight says the mitigation isn't enabled because it's not compatible with the hardware. The funny part is my mobo is also Intel and I want to die.

>> No.64176338

>>64176278
I'm not this guy >>64176068, but I have the same problem with my laptop. I basically just use it for photoshop, and general stuff like web browsing, music, movies, etc., and maybe Steam if I'm away from home with it.

>> No.64176441
File: 556 KB, 1314x1125, tfw AMD CPU and not affected by hardware bug like Intel shit processors.jpg [View same] [iqdb] [saucenao] [google] [report]
64176441

>>64173418

>> No.64176462

>>64172491
hey /g/

As a normiefaggot with a macbook who uses bootcamp to play games

Do i have to install the windows10 security patch? I already got 10.13.2 macOS

>> No.64176466
File: 413 KB, 485x608, [HorribleSubs] Konohana Kitan - 03 [720p].mkv_snapshot_06.55_[2017.10.18_11.32.35].png [View same] [iqdb] [saucenao] [google] [report]
64176466

It begins. https://www.theregister.co.uk/2018/01/04/amazon_ec2_intel_meltdown_performance_hit/

>Some Amazon AWS customers have complained of noticeable slowdowns on their cloud server instances – following the deployment of a security patch to counter the Intel processor design flaw dubbed Meltdown.

>> No.64176472
File: 94 KB, 811x1380, _Intel_Core_2_-_MARC_-_2018-01-05_21.30.00.png [View same] [iqdb] [saucenao] [google] [report]
64176472

Reminder.

>> No.64176501
File: 92 KB, 190x190, 1493341543659.gif [View same] [iqdb] [saucenao] [google] [report]
64176501

>>64176472
>2007

>> No.64176516

>>64176466

Fucking YES!!!!!

As someone who hates Amazon and Jeff "Hillary Clinton" Bezos, I would gladly let him cum inside my ass if he replaced all AWS hardware with AMD Epyc

>> No.64176530

>>64176462

nigga you need a fucking firmware/BIOS update

>> No.64176561

Fuck Intel and fuck jewish people.

>> No.64176562

>>64176462
Obviously. Bootcamp is just a BIOS for babies, your mac behaves 100% like any other windows laptop if you boot windows.

>> No.64176576 [DELETED] 

>>64176530
>tfw no more bios updates for my Intel-infected mobo

>all Intel processors since 1995 are affected

>> No.64176589
File: 300 KB, 594x800, __hirasawa_yui_k_on_and_slayer_band_drawn_by_kaiga__02dafc30372e3188c5f317c2c643cc16.jpg [View same] [iqdb] [saucenao] [google] [report]
64176589

>>64176530
>tfw no more bios updates for my Intel-infected mobo

>all Intel processors since 1995 are affected.

>> No.64176602
File: 6 KB, 250x203, 1514949857188.jpg [View same] [iqdb] [saucenao] [google] [report]
64176602

>mfw waiting for the next Security Now podcast

>> No.64176615

>>64176589
>not baking a new BIOS update with the microcode update yourself
git gud!
Seriously though, i don't get why intel can't release the microcode update via windows update, like they usually do.

>> No.64176620

>>64176562
dammit anon give it to me in straight english

>>64176562
I'm sure this is what other anon meant.

Thanks anons.

>> No.64177586

in ryzen we trust

>> No.64177642
File: 26 KB, 1077x382, IMG_20180106_013242.jpg [View same] [iqdb] [saucenao] [google] [report]
64177642

Lol I just got this captcha and thought you guys would get a kick out of it.

>> No.64177711

>>64177642
lmao

>> No.64177822
File: 339 KB, 682x792, 14962322898927.png [View same] [iqdb] [saucenao] [google] [report]
64177822

>>64172790

>> No.64177927
File: 828 KB, 854x1723, file.png [View same] [iqdb] [saucenao] [google] [report]
64177927

Thought you guys might like what I found in the other thread

>> No.64178464

>>64176615
>i don't get why intel can't release the microcode update via windows update, like they usually do.
That's because hackers these days are lazy and would only try to open up severe security updates to get around and use the loophole against those who didn't receive updates
The winning game is not to play. All or no.

>> No.64178482
File: 48 KB, 858x405, pasted image 0.png [View same] [iqdb] [saucenao] [google] [report]
64178482

Add this next time
https://www.epicgames.com/fortnite/forums/news/announcements/132642-epic-services-stability-update
>muh it doesn't affect gayming

>> No.64178517

>>64176530
Did the firmware/Bios updates that fix this already come out?

>>64176615
Who said they aren't going to release it through windows update? Was there already an official statement regarding the microcode updates? I haven't heard anything about it yet.

>> No.64178630

>>64174962
You're fucked on CPU side.

>> No.64179107

>brainlet
How do I actually check if the update is installed on windows 10?

>> No.64179127

>>64179107
Look for KB4056892.

>> No.64179142

>>64176441
Why the fuck would you mount your HDDs like that, and not in the cage next to the PSU?

>> No.64179201

>>64179127
Found a bunch of files.
What am I looking for exactly?

>> No.64179223

I need to patch windows and bios? I thought bios was enough

>> No.64179274

I remember that Linus Torvalds ranted about Linux patch to address the Meltdown thingy on Intel CPU. What exactly was it?

>> No.64179276

>>64179223
How did you patch your bios?

>> No.64179284

>>64172491
Just ran a virus scan and didn't get anything so no idea what this thread is about.

>> No.64179299

>>64179201
nvm found it

>> No.64179323

>>64172582
Desktop users overeacting stuffs.
Company (cloud and other) have noticed a 30-50% performance loss. But desktop user even gotten 1-2% performance boost.

>> No.64179503
File: 104 KB, 232x344, 1390729848562.gif [View same] [iqdb] [saucenao] [google] [report]
64179503

>>64179201
>Look for KB4056892.

>> No.64179508

My samshit touchjizz tablet doesn't have this problem.

>> No.64179516
File: 41 KB, 216x114, 120417613833333.png [View same] [iqdb] [saucenao] [google] [report]
64179516

>Intel drops 30% performance
>Still better than pooMD
Couldn't pay me to care less.

>> No.64179527

>>64179503
found it already (>>64179299
). my brainlet stub decided to check files instead of windows update history.
this is now the part where you can laugh at me.

>> No.64179559

>>64179516
for what? playing games? gtfo /v/irgins
>>>/v/

>> No.64179868

>>64179284
your intel chip is the virus

>> No.64179870

>>64172491
Is Via or Powermac affected by this?

>> No.64179982
File: 8 KB, 185x185, 16046-32530-9913.jpg [View same] [iqdb] [saucenao] [google] [report]
64179982

>>64179284

>> No.64180010

>>64179870
It's only Intel that is affected. All of their chips produced in the last decade have a flaw in the design of the chips themselves.

>> No.64180034

Are Pentiums G-series not affected?
They are not listed by Intel: https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00088&languageid=en-fr

>> No.64180115

i like how i can disable the management engine in bios.

>> No.64180129

>>64180010
ARM and some AMD chips are affected as well.

>> No.64180180

>>64175108
Not necessarily. If you're on Windows 10 then you can probably add a Microsoft account and then use the built-in 'contact support' thing. Tell the pajeets there that your motherboard broke and you had to replace it, but 'suddenly Windows isn't activated please help oh god what do I do'. Worked for me at least - they generated a new product key immediately.

>> No.64180193
File: 64 KB, 691x771, 1515145992968.jpg [View same] [iqdb] [saucenao] [google] [report]
64180193

>>64172790

>> No.64180216
File: 69 KB, 573x553, meltdown_and_spectre.png [View same] [iqdb] [saucenao] [google] [report]
64180216

randall doing what he does best being absolutely hilarious as always

>> No.64180218

pls no memes. what practical effect will this have for the average consumer?
I have AMD so i don't really care but it could be funny

>> No.64180236

>>64180218
Depends on what you do. Shit like database workloads gets hit the most. Games and rendering, however, are mostly unaffected by the mitigation measures.

>> No.64180237

>>64172491
http://www.dsogaming.com/news/intel-lists-all-cpus-affected-by-spectre-meltdown-epic-shows-performance-impact-on-gaming-servers/

>> No.64180243
File: 91 KB, 653x726, 1491601065144[1].png [View same] [iqdb] [saucenao] [google] [report]
64180243

>>64172491
http://lists.suse.com/pipermail/sle-security-updates/2018-January/003562.html

it's confirmed that amd will disable branch prediction for his cpus
this means lower performance for amd also

>> No.64180254

>>64180243
Fake news.

https://news.ycombinator.com/item?id=16081366

https://www.reddit.com/r/Amd/comments/7oekb4/amd_latest_microcode_update_does_not_disable/?st=jc3av3dk&sh=5606d9e5

>> No.64180265
File: 96 KB, 638x710, 1500260377912.jpg [View same] [iqdb] [saucenao] [google] [report]
64180265

>>64176466
NO NO NO NO NO NO NO

>> No.64180340

>>64172790
>/pol/
the amerimutt meme is from /int/, created to trigger americans on /pol/

>> No.64180410
File: 3.92 MB, 9000x9000, intel_collage.jpg [View same] [iqdb] [saucenao] [google] [report]
64180410

>> No.64180428

>>64180243
>>64180254
Intel shills btfo

>> No.64180439

Whats going on, i live under a rock.

>> No.64180461

>>64180439
Shit's thoroughly fucked. The future is now.

>> No.64180475
File: 1.31 MB, 250x141, 1479429538541.gif [View same] [iqdb] [saucenao] [google] [report]
64180475

>>64180410
>From this point on
>Each and every time
>Someone posts this collage
>That's literally 70% of pictures made by me
>Literally every single fucking time
>MFW

>> No.64180495

>>64173344
the only patch will be from your motherboard vendor, assuming windows update can't update your BIOS

visit motherboard mfg website and look for new BIOS update

>> No.64180609

SPECTRE vulnerability test program, compile with Visual Studio.

https://pastebin.com/MZVAi4Da

AMD Ryzen 1600x vulnerable on W10 here

>> No.64180619

>>64180609
stop shilling pastebin
https://gist.github.com/ErikAugust/724d4a969fb2c6ae1bbd7b2a9e3d4bb6

>> No.64180634

>>64180619
shit fucking (((Java))) braces and won't compile on Visual Studio at all, fuck off shill

https://pastebin.com/MZVAi4Da

>> No.64180648

>>64180634
>visual studio

>> No.64180658

>>64180648
>anything other than visual studio

>> No.64180675
File: 65 KB, 679x711, 1515046611979.jpg [View same] [iqdb] [saucenao] [google] [report]
64180675

>>64180609
>>64180609

>> No.64180706

>>64180675
Spectre is most definitely dangerous for AMD users too...

Proof of Concept code above will tell you that.

>> No.64180713
File: 27 KB, 526x300, 1314630994793.jpg [View same] [iqdb] [saucenao] [google] [report]
64180713

>>64180675
>reddit
>no additional sources

>> No.64180715

>>64180675
>>64180706
On Windows 10 at least...

>> No.64180720

>>64180034
Core X on X79 (3820-3970X, 4820K to 4960X)were not listed either. They, like the G series are definitely affected too.

>> No.64180744

>>64180609
not interested in installing VS, show results

>> No.64180772
File: 294 KB, 1386x860, spectre2.jpg [View same] [iqdb] [saucenao] [google] [report]
64180772

>>64180744
at 400 bytes it continues reading a lot of string literals from the .exe and printing them

>> No.64180790
File: 282 KB, 1334x1019, spectre.png [View same] [iqdb] [saucenao] [google] [report]
64180790

>>64180744
using the gist one because pastebin-anon is a dick

>> No.64180799

>>64180706
>Spectre
Spectre is a non-issue. It is only compared to Meltdown because of damage control from Intel: a way to say that every cpu has defaults, we aren't the only one, please don't sue us. Meltdown is ridiculously easy to exploit, break all protection, and only works on Intel. Spectre are only small cpu bugs like there is found dozen each years.

They aren't comparable and should never be compared.

Spectre 1 is trivially patchable. Spectre 2 is very complicated to implement, only work on some system, and does not impact AMD anyway.

>> No.64180815

>>64180799
>Spectre 1 is trivially patchable.

Oh ok, so in a week or so this exploit PoC shouldn't work. I look forward to testing it, and most likely being disappointed.

>> No.64180839

>>64178482
Intel shills on suicide watch

>> No.64180855

>>64180790
Why is the score so high on Linux?

score was the second try for most of them on W10

>> No.64180860

>>64180815
Everyone in seems to be concerned about Meltdown way more than the Spectre 1.

Except you for some reason? You really need a few shekels deposited into your PayPal account from Intel to pay for dinner tonight?

>> No.64180873

>>64180799
The veritable issue of that damage control is that it is working.

The narrative of relatively savvy tech guys has switched away from "Intel is utterly incompetent, and all Intel hardware designer should be killed on the spot", which is the natural, rational response to Meltdown. Only people like kernel devs are openly swearing at Intel, because they understand.

Instead, the narrative has come to pure FUD: all cpus are affected (fear), no-one really knows anything about what's possible (uncertainty), and can you even tell if AMD's cpus aren't affected too (doubt)?

FUD. It works.

>> No.64180883

>>64176068
unpatched with an Intel CPU, bad Javascript from a website can do it.

>> No.64180885

>>64180860
I'm still mad my AMD "master race" CPU is vulnerable to this exploit.

Fuck intel, is that what you want to hear?

>> No.64180890

>>64180855
noidea

>> No.64180901

>>64176501
That's when "the cloud" was really taking off in the professional IT world.

The non-idiots saw all the potential security risks, yet IT VPs ate it up for the cost savings.

>> No.64180906

Is my Exynos processor safe ?

>> No.64180912

>>64180883
What if I'm patched but the BIOS is not?

>> No.64180913

>>64180885
see
>>64180873

>> No.64180930

>>64180912
don't know to be honest.

>> No.64180943

>>64180912
then you aren't patched...

>> No.64180946

I always looked for laptops with AMD instead of Intel thanks to /g/ (and 4chan wide) shilling. My last laptop I gave up on it because Lenovo has some really good prices and most stored here don't have them with AMD...
Now this happens and I feel duped. Should've listened to /g/ and looked harder.

>> No.64180948

>>64172520
cant wait for india to invent the toilet

>> No.64180950
File: 466 KB, 1098x457, Untitled.png [View same] [iqdb] [saucenao] [google] [report]
64180950

>>64180609
Phenom II 955 on Win 7 is vulnerable, assuming this thing works as intended.

>> No.64180974
File: 20 KB, 505x441, 1422667271328.jpg [View same] [iqdb] [saucenao] [google] [report]
64180974

>>64180943
Fuck.

>> No.64180991

>>64180950
What?

It's not printing the text though... Change "len" to 400 like in my code and delete the "`" tilde signs that don't print out right.

int i, score[2], len = 400;


printf("0x%02X= %c score=%d ", value[0],
(value[0] > 31 && value[0] < 127 ? value[0] : '?'), score[0]);

>> No.64180998

>>64180034
It's me bug, don't be retarded.
>pentium g
Oh, nvm, it's too late.

>> No.64181005
File: 91 KB, 355x587, spectre3.jpg [View same] [iqdb] [saucenao] [google] [report]
64181005

>>64180950
If it isn't printing the magic words it isn't working...

>> No.64181038

>>64180815
Do you understand what is Spectre 1? It is a way for interpreted code to break from their sandbox to read the interpreting process' memory.

Javascript reading Firefox. Java apps reading the Java interpreter. BPF reading the kernel. Etc.

Spectre 1 can be trivially patched by the interpreter, and that is exactly what Firefox effectively did. It's a minor bug. Yet another thing interpreter should watch for. PHP, Java, Chrome, the BPF, etc, will be patched eventually. Well, probably not PHP. I don't think they have quite the competence to understand what is happening here.

Running a Spectre 1 PoC is absolutely retarded. You are effectively running an insecure code inside an insecure interpreter and being surprised that Spectre 1 works. Duh. Of course it works. Double duh.

>> No.64181047

>>64181038
Don't take it up with me, take it up with:

"* This source code originates from the example code provided in the
* "Spectre Attacks: Exploiting Speculative Execution" paper found at
* https://spectreattack.com/spectre.pdf
"

>> No.64181067
File: 73 KB, 700x565, 1515185963808.jpg [View same] [iqdb] [saucenao] [google] [report]
64181067

>> No.64181078

>>64180609
what part is the botnet part?

>> No.64181136

>>64175108
the absolute state of windows everybody

>> No.64181172

>>64177642
for real? looks fake

>> No.64181187

>>64181172
Does it matter?

>> No.64181275

I keep refreshing for updates but the update isn't showing up
Are microsoft fucking me ?

>> No.64181283
File: 725 KB, 1440x870, Untitled 2.png [View same] [iqdb] [saucenao] [google] [report]
64181283

>>64180991
>>64181005
I have no idea what the fuck any of this means. I also tried gcc, but it refused to compile it.

>> No.64181350

>>64179274
He was ranting about a patch that was a workaround to prevent the variant 2 spectre. The patch was written without a togglable variable to turn it off, i.e intel coder(s) who wrote and submitted that patch wrote it with the assumtion that all X86 processors, both current and all the future, will always have that vulnerability

>> No.64181382

>>64173495
>ARMA 3
I thought it had an linux client?

>> No.64181394

>>64181283
Success doesn't really mean success. It just means the exploit "thinks" it got the correct value.

Unless it says the magic words, it's not exploiting your memory.

>> No.64181433

https://www.barrons.com/articles/dont-blame-intel-for-the-failures-of-computer-security-1515213339

I agree. Don't blame Intel. Just buy AMD.

>> No.64181436
File: 633 KB, 1036x843, Untitled 3.png [View same] [iqdb] [saucenao] [google] [report]
64181436

>>64181283
The fixed 32-bit versions of both the Pastebin and the Github code print the ossifrage text (followed by a bunch of weird shit, not sure if that's intended), none of the others do.

>> No.64181453

>>64181433
>To Read the Full Story, Subscribe or Sign In
no thanks

>> No.64181472

>>64181038
Or said with numbers, because I'm tired trying to explain exactly what is Meltdown and Spectre to people who don't care. Now from the "Pulled Out of My Ass" 1-10 scale of difficulty to use, dangerousness, and difficulty to patch. Easy to understand numbers for morons and intellectually disabled people.

Spectre 1
Difficulty to use: 2
Dangerousness: 4
Difficulty to patch: 1
Vuln: Intel, Amd

Spectre 1 is more or less useless. Not an issue at all, only yet another CPU bug software devs need to protect against. Why are we even talking about it?

Spectre 2
Difficulty to use: 10
Dangerousness: 7
Difficulty to patch: 10
Vuln: Intel. (Maybe) Amd, but it's all FUD all the way down, so take it with a grain of salt.

Spectre 2 is incredibly complicated to use in a real environment. It isn't really that dangerous, but difficult to patch, and difficult to test against. Lots of FUD around that one, but honestly I don't fucking care, because:

Meltdown (aka KEKEK)
Difficulty to use: 0
Dangerousness: 10
Difficulty to patch: 10
Vuln: Intel

Kek. Kek. The incompetence of Intel knows no bound.

By the way, I am not bound to AMD or Intel. I am only a kernel developer that is laughing my ass off from the sheer incompetence of the second, and feel they should just kill themselves for the fucking work I need to do because they are so grossly incompetent. A bit of vengeance and schadenfreude all in one. For the love of god, for the love of all that is holy, fuck. Holy shit. Intel. What the fuck.

>> No.64181621

Paranoid user here. Apparently it's possible for javascript to steal info I type in my browser? Would this only extend for as long as said compromised website remains open?

>> No.64181630
File: 3.91 MB, 9999x9999, intel_collage_9999preview.jpg [View same] [iqdb] [saucenao] [google] [report]
64181630

I need more material for the 9999x9999 final

>> No.64181714
File: 13 KB, 684x56, intel.png [View same] [iqdb] [saucenao] [google] [report]
64181714

how long do i need to wait to get hacked?

>> No.64181723

>>64181714
too late i hacked u m8

>> No.64181724

>>64174596
Because Jewtube shills are not programmers but salesmen.

Hardware Unboxed did a test showing that desktop users aren't affected and got called an Intel shill by AMDrones themselves.

Meanwhile hardcore AMD shill AdoredTV shat on Intel as usual and so did JayzTwoCents. I watched the WAN show to check if Linus will shit on Intel and while he wasn't on the show his #2 guy shat on Intel.

>> No.64181744

>>64181436
Additionally, gcc shits the bed on everything and clang works, but it only prints question marks and no ossifrage text even with a 32-bit executable and the fixes applied.

I'd set up a Linux VM to try it in but I honestly can't be fucked at this point, it's the weakest exploit anyways.

>> No.64181745

>>64176516
>he thinks companies will switch over to AMD just like that
>implying they won't throw shekels at Intel so Intel will solve the problem and with enough shekels and pressure they will
>he thinks Intel made the backdoor on purpose and without oversight from the intelligence community

>> No.64181770
File: 1.41 MB, 444x250, Raja Seal of Approuval.webm [View same] [iqdb] [saucenao] [google] [report]
64181770

>>64181621
Do you accept webums?

>> No.64181781
File: 14 KB, 938x120, 1503314155502.jpg [View same] [iqdb] [saucenao] [google] [report]
64181781

>>64181630

>> No.64181786
File: 61 KB, 1284x396, ryzen1600.png [View same] [iqdb] [saucenao] [google] [report]
64181786

gg amd

>> No.64181857

>>64174546
>Soon. Wait for after CES. First Zen APUs are almost at the door.
First Zen APUs are already out my man. HP has had one out for over a month now.

>> No.64181882

>>64174370
AMD shills sure are working overtime.

>> No.64181884

>>64180948
>cant wait for india to invent the toilet
Toilet's already been invented, Rajesh.

>> No.64181885
File: 94 KB, 532x594, lolwut.jpg [View same] [iqdb] [saucenao] [google] [report]
64181885

>>64174881
>best value investment: women

>> No.64181891

anybody into ring -3 yet? need transfer function

>> No.64181901

>>64181275
W10 patch drops Tuesday.

>> No.64181905

>>64173917
Still faster than your intel piece of junk, faggot.

>> No.64181931

>>64181786
Easy Photoshop

>> No.64181943

>>64181901
thanks my man

>> No.64181946
File: 183 KB, 1280x1196, Screen_Shot_20180105_at_19.34.05.png [View same] [iqdb] [saucenao] [google] [report]
64181946

>> No.64181959

>>64181882
It's the Intel shills using FUD about Spectre to deflect the massive ass-rape Meltdown is for Intel's server business.

>> No.64181970

intel about to get blow the fuck out in the server market
https://www.epicgames.com/fortnite/forums/news/announcements/132642-epic-services-stability-update

>> No.64181979

>>64181946
Similar fix for Ryzen is needed. It's 100% vulnerable to both versions of Spectre. AMD lied, shills died

>> No.64181983
File: 52 KB, 464x431, 2018-01-06-095830_1366x768_scrot.png [View same] [iqdb] [saucenao] [google] [report]
64181983

What did Intel mean by this?

>> No.64181990

Hopefully the fix will be CPU agnostic and penalize AMD too. It's only fair, to be frank, why would I have a premium CPU with shitty perfs while AMPoors and their pocket-change worth CPU are unaffected.

>> No.64181993
File: 561 KB, 1176x775, Screen Shot 2018-01-06 at 16.59.13.png [View same] [iqdb] [saucenao] [google] [report]
64181993

>> No.64182078

>>64181990
It has to be. I've already convinced my IT department to never purchase AMD desktops because they lied on their response to Spectre. We're replacing all of our pre-Haswell desktops with Coffee Lake systems.

>> No.64182100

>>64181983
Intel shills are so insecure

>> No.64182111

>>64181979
Begone shill.

>> No.64182127

>>64182078
>>64181990

Because different things can be different

>> No.64182142

>>64181990
The Windows updates does not enable VA shadowing nor BTI mitigation on AMD processors. Anyway, you can toggle them manually on the registry even on Intel. Therefore, you can just make a script that changes these values when the PC is disconnected from the internet and change them back when it reconnects.

As for Linux, you probably seen the few lines of code posted here over a thousand times already.

So no, AMD is not slowed down by Meltdown.

Future Spectre patches might slow them down though, although same goes for Intel(in this case, again).

Salty, huh? I have both AMD and Intel, I am about 50% salty right now.

>> No.64182222

>>64174422
I looked up goldenhar syndrome and considering the results I got, that guy doesnt look too bad

>> No.64182233

>>64182142
>So no, AMD is not slowed down by Meltdown.
But it should be. It's only fair that AMD harden themselves against the same vulnerabilities that all the other x86 CPUs face. Otherwise, that's just being dishonest and scummy.

>> No.64182253

lmao theyve known wat they were doing since the 60s

>> No.64182269

This bullshit over the ME is retarded, if Intel were spying on everyone you'd be able to detect it in the network traffic.

>> No.64182271

>>64182233
I fail to find your logic on the fairness of business competition when it's a jungle out there. If you want to be an inteldrone go on about how spectre fucks everyone not how it's unfair AMD isn't affected by Meltdown.

>> No.64182277

http://www.multicians.org/protection.html forgot link

>> No.64182287

>>64182078
They did not lie, the exact tests used by spectre is ineffective against AMD CPUs and they claimed just that. It is just that they can be thoretically affected by an attack of similar principle, but executed differently. Not to say, >>64181990 did not mention explicitly spectre, so we can assume he is talking about meltdown(which is OP's topic) which only affects Intel systems.

Also,
>replacing a batch of vulnerable systems with another batch of vulnerable systems
Why even bother upgrading(unless you need 6 cores urgently)? I would wait for the new generations of Intel that does not have this problem.

>it has to be
Nope, Linux and Microsoft disables the mitigation on AMD cpus.

>> No.64182291

Probably the best decision Microsoft made in the past decade was going AMD for their Xbone.

We could've had an ISO loader by now

>> No.64182303

>>64182233
except AMD's executor applies a sanity policy before trying to speculatively execute potentially retarded and blatantly exception throwing instructions.

so no, they are not being scummy.

>> No.64182316

>>64182271
The person's trolling. It was obvious from the first post.

Anyone who states that AMD should be penalized for Intel's failures is BSing or ridiculously naive.

>> No.64182328
File: 997 KB, 500x270, 1507179268167.gif [View same] [iqdb] [saucenao] [google] [report]
64182328

>>64182233

>> No.64182344

>>64182287
>the exact tests used by spectre is ineffective against AMD CPUs and they claimed just that
But that was a lie. Ryzen is fully compromised now with a working PoC able to defeat whatever measures AMD put into place to mitigate Spectre on the kernel level. As far as we know, AMD could still be vulnerable to an exploit similar to Meltdown, too.

>Why even bother upgrading
Older systems were not going to receive BIOS updates for Spectre. They need to be removed from our network immediately.

>I would wait for the new generations of Intel that does not have this problem.
BIOS updates already fixed Spectre for Intel systems only. AMD Ryzen Pros/A-Series Pros has no such updates!

>Nope, Linux and Microsoft disables the mitigation on AMD cpus.
That's a vulnerability waiting to be exploited.

>> No.64182345

>>64182233
The problem is that the mitigation for meltdown(not spectre) will not harden AMD systems in any way, and brings bad publicity to the OS maker. AMD systems however should be hardened against all spectre fixes because they can theoretically be affected.

>> No.64182363

>>64181472
>Holy shit. Intel. What the fuck.

They saw the profits on the horizon and decided to ignore it. They probably knew the bug existed.

>> No.64182368

https://en.wikipedia.org/wiki/Intel_Active_Management_Technology#Ring_-3_rootkit

>> No.64182383

>64182344
[citation needed]

>> No.64182389

>>64182142
>Salty, huh?
Yeah, intel may pay OS vendors to include it for AMD or whatever I don't give a shit as long as the natural order is respected.
I paid premium price for my CPU, I want premium perfs whatever it takes.

>> No.64182397

>>64182383
Lenovo, HP, and Dell
Driver and support pages for their more recent business desktops

>> No.64182399

>>64181744
My version compiles in visual studio if you have that: https://pastebin.com/MZVAi4Da

be sure to turn optimization off in the project settings though

>> No.64182423

>>64181931
That's the spectre1 bug, it hasn't been patched yet, and it works on my 1600x W10 system too

>> No.64182428
File: 217 KB, 1080x873, 1515122782491.jpg [View same] [iqdb] [saucenao] [google] [report]
64182428

I don't understand what bug you're talking about.

>> No.64182435

>>64181472
At least they're not grossly incompetent like AMD is with their OEM relation, product availability, and general support. Now fuck off, AMDshill

>> No.64182437

>>64181959
Fully Un-Detected?

>> No.64182467
File: 90 KB, 957x621, 1505496973556.jpg [View same] [iqdb] [saucenao] [google] [report]
64182467

>HP is aware of the recent class of vulnerabilities referred to as “speculative execution side-channel attacks” that affect many modern processors (Intel, AMD, and ARM ) and operating systems. HP will be providing updated information on this support site as soon as it becomes available.
Where is my updates you fockin' Joooz. I paid for this. REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE

>> No.64182491

>>64175108
what is that nazi shit?
microsoft pls

>> No.64182492

>>64182467
You bought an HP? Is this what frogposters have become?

>> No.64182493

>>64182467
>no updates are planned for EliteDesk 705 G3s
REEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE

>> No.64182509

Fact : AMD is sexist and racist and deserve the perf hit even though it isn't vulnerable.

>> No.64182523

>>64182467
>>64182493
It's not something that can be fixed with a software update.

>> No.64182547

https://www.slideshare.net/codeblue_jp/igor-skochinsky-enpub

>> No.64182552

>>64181990
good thing that i use freedom respecting software so those patches arent forced on my computers if i dont want them.

>> No.64182568
File: 193 KB, 1920x1080, screenshot.png [View same] [iqdb] [saucenao] [google] [report]
64182568

Hmm

>> No.64182583

it affect heavy load only ? my score goes down on multi core bench.

>> No.64182620

>>64182344
Even if AMD systems could be vulnerable to a similar exploit as compared to Meltdown, there should be a separate patch for it because (part of) the problem would lie somewhere else. This time, it should/would rightfully be turned off on Intel machines however.

>Not receive BIOS updates
You could hope for microcode updates through the OS. I am not certain when they would push it on the update channels, or if they decide to update them at all though.

>fixed Spectre for Intel systems only.
From what I read online, the BIOS updates(mainly just a microcode update) only fixed meltdown, not spectre(which cannot be 100% fixed but only mitigated). Would appreciate a source/read on the spectre mitigation update.

You implied that Haswell systems would get BIOS updates, which is released mid 2013. This would be interesting because Ivy Bridge-E is released fall-2013 but is on an older platform (X79), and if they patched X79 they would have patched Sandy Bridge-E as well. Not sure what Intel decides to do with the Patsburg platform which incidentally is what my main Workstation runs on. I am certainly looking forward to the BIOS patch of course.

>> No.64182623

>>64182269
maybe but there might be a way to enable it and do bad things with it without the user knowing. its easier than ever to access bios stuff now when you can flash it and change settings directly from windows. im actually surprised that no one has used the windows based bios flashers to install persistent malware.

>> No.64182660

>>64182583
Depends on what you mean by heavy load. Anything that depends heavily on syscalls is going to see a hit.

>> No.64182734

lmao rom bypass partition

>> No.64182783

>can effect via sms
from my tablet (or from a phone!), you can access the AMT/IME browser on your box AND TURN IT OFF! Seriously! You have a Win7/Sp1 box, running something, and some guy with a phone (if you have been foolish enough to expose this machine to the internet), can reach out and *touch* you good.

>> No.64182900

>>64181990
Because you like wasting money, that's the only reason to buy Intel.

>> No.64182990

>>64182428
amd faggits on suicide watch

>> No.64183013

relevant https://en.wikipedia.org/wiki/Flynn%27s_taxonomy

>> No.64183022

>design flaw
perfected in 1990 http://www.google.com/patents/US5765012

>> No.64183033

>>64182783
how would that work? i have still not found any way to enable those and seems like theres no public documentation about it even though some say that business users use it for system management.

>> No.64183052
File: 68 KB, 2320x3408, lmao.png [View same] [iqdb] [saucenao] [google] [report]
64183052

>>64183033
am still gathering information, ctrl p at boot to access the me/amt

>> No.64183125

When will we know for sure how much of a performance hit the fix will cause? I've had my PC disconnected since tuesday

>> No.64183126

not so obsolete http://www.staff.city.ac.uk/~kloukin/IN2P3/material/JEFF_SF_14March2002.pdf within me/amt
>classes for cryptography, ui elements, flash storage access, implementing loadable applets

>> No.64183179

>>64182509
(you)

>> No.64183181

>>64183125
How are you even posting?
Also, it's less than 1%. Some benchmarks even GAIN performance after the fix. lol

>> No.64183187
File: 257 KB, 453x477, 1515096669949.png [View same] [iqdb] [saucenao] [google] [report]
64183187

>>64181630

>> No.64183190

>>64172790
yes goys don't be antisemitic !
buy intel for the memory of 6 goryllion

>> No.64183192

https://www.globalplatform.org/specificationsdevice.asp

>> No.64183205
File: 84 KB, 676x507, 1515224795982.jpg [View same] [iqdb] [saucenao] [google] [report]
64183205

is it true that this meltdown occured because designers prioritized looks over security?

>> No.64183214

So is the full fix coming next week and I won't have to fiddle wit anything?

>> No.64183216

anybody zenmaster of huffman compression?

>> No.64183222

>>64181786
Only EPYC has SEV

>> No.64183224

>>64183214
There will not be a full fix. It can't be patched with software.

>> No.64183226

>>64173456
35%

>> No.64183248

>tfw bought a 7600K back in august
i g-guess no updates til i upgrade

>> No.64183250

>>64183187
Nice. Added.

>> No.64183295

this 'flaw' was meant to be theft deter ie prey

>> No.64183301

I've got a bunch of old shit, ivy/sandy bridge processors, old gen NUCs. What are the chances of these things getting a bios update? I don't really feel like spending money or time on switching everything over to AMD.

>> No.64183311

>>64183301
You'll probably just have to wait for software updates and gradually get your performance from 70% to ~85% back.

>> No.64183323

ring -3 rotkiss http://www.stewin.org/slides/pstewin-SPRING6-EvaluatingRing-3Rootkits.pdf

>> No.64183327
File: 33 KB, 657x527, 1476894583895.png [View same] [iqdb] [saucenao] [google] [report]
64183327

what else i need other than os and bios update to be """"secure"""?

>> No.64183347

>>64183327
theres no securing this. its designed into substrate

>> No.64183348

i dont give a fuck

hack me and steal my passwords, im gonna kill myself anyway

>> No.64183353

>>64183327
an amd cpu

>> No.64183354

>>64182316
>i was pretending to be retarded
Ironic retardation is still retardation.

>> No.64183381

>>64183327
You need to buy a new CPU.

>> No.64183382

>>64183224
I heard that there was going to be an automatic windows update next week for it

>> No.64183387

>>64181382
It does but AFAIK you can't play on windows servers

>> No.64183394

>>64183348
don't do it anon, it will only embolden the AMD fanboys--AMfags will probably have a performance decreasing patch come along soon.

>> No.64183403

>>64183382
Tuesday, is what someone said.

>> No.64183406

>>64183382
That only fixes the Meltdown bug. Every modern CPU will continue to be vulnerable to Spectre.

>> No.64183420

>>64183381
lmao https://en.wikipedia.org/wiki/Out-of-band_management whole substrate design process has to be revised

>> No.64183437

How long will it take for new processors without these issues?

I want to build PC for VR soon and I'm not sure if I should wait for new generation.

>> No.64183447

>>64183437
At least a year.

>> No.64183451

posting https://sourceforge.net/projects/openamt/ massive loic campaign needs orchestration

>> No.64183494

>>64183437
>How long will it take for new processors without these issues?
Wait for new uarch in 2021.

>> No.64183500

>>64183406
I thought the meltdown bug was spectre

Pls understand, I'm browsing with a slow 6 inch tablet, its hard to keep up

>> No.64183579
File: 321 KB, 681x438, 1504904148876.png [View same] [iqdb] [saucenao] [google] [report]
64183579

>>64183250

>> No.64183593

>all these vulnerabilities discovered
>billions of dollars in stock wiped out

Let this be a lesson to companies that deliberately empower the NSA. Intel's hardware simply cannot be trusted. It's highly unlikely that Intel's competitors can be trusted.

>> No.64183595

Just build your own processors... fags

>> No.64183602

>>64183500
Nah they're two separate fuck ups. Meltdown is worse because it's easier to get access to your shit but will be stop gap fixed by an OS and BIOS update. Spectre will eventually be mitigated but none of this will be right until the new processors roll off the lines. So hold onto your butt and hope you aren't worthy enough of a target.

>> No.64183604

>A parallel array processor for massively parallel applications is formed with low power CMOS with DRAM processing while incorporating processing elements on a single chip. Eight processors on a single chip have their own associated processing element, significant memory, and I/O and are interconnected with a hypercube based, but modified, topology. These nodes are then interconnected, either by a hypercube, modified hypercube, or ring, or ring within ring network topology. Conventional microprocessor MMPs consume pins and time going to memory. The new architecture merges processor and memory with multiple PMEs (eight 16 bit processors with 32K and I/O) in DRAM and has no memory access delays and uses all the pins for networking. The chip can be a single node of a fine-grained parallel processor. Each chip will have eight 16 bit processors, each processor providing 5 MIPs performance. I/O has three internal ports and one external port shared by the plural processors on the chip. Significant software flexibility is provided to enable quick implementation of existing programs written in common languages. It is a developable and expandable technology without need to develop new pinouts, new software, or new utilities as chip density increases and new hardware is provided for a chip function. The scalable chip PME has internal and external connections for broadcast and asynchronous SIMD. MIMD and SIMIMD (SIMD/MIMD) with dynamic switching of modes. The chip can be used in systems which employ 32, 64 or 128,000 processors, and can be used for lower, intermediate

>> No.64183617

>>64183595
O HAI, MCST. You fogrot to enter tripcode and log in.

>> No.64183661

>>64183595
Can I do that with legos?

>> No.64183664

>>64183604
>1990

>> No.64183691

New thread >>64183682

New thread >>64183682

New thread >>64183682

>> No.64184332

>>64179323
im sure
that they done that on purpose, since its fixed nothing really

>> No.64184462

Fuck its going to be years before anyone creates a new architecture to avoid this shit. 2020, 2025?

Fuckers can’t even get their 10nm tech to work properly

>> No.64184878

>>64181172
Yes. What looks fake about it?

>> No.64185546

>>64172491
How much does this affect people who write on the computer?

>> No.64185584

>>64185546
Why are you drawing on your own computer?

>> No.64185601

>>64185584
Sometimes you just gotta jot something down and there's no paper around.

>> No.64185946

>>64181472
well
i bet every hacker has been controlled and ran by intel this whole time. trying to get peoples information they dont care about using the computer or selling a computer they want to threaten you into stuff

>>
Name (leave empty)
Comment (leave empty)
Name
E-mail
Subject
Comment
Password [?]Password used for file deletion.
Captcha
Action