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

Maintenance is complete! We got more disk space.
Become a Patron!

/g/ - Technology

View post   

[ Toggle deleted replies ]
File: 75 KB, 925x604, Selection_044.png [View same] [iqdb] [saucenao] [google] [report]
70958608 No.70958608 [Reply] [Original] [archived.moe] [rbt]

How fucked is Intel?

>> No.70958629

MEGA ULTRA FUCKED!!!!!!!!!!!!!!!!!!!!

>> No.70958630
File: 376 KB, 500x491, 1557267652585.gif [View same] [iqdb] [saucenao] [google] [report]

i7oddlers BTFO!

>> No.70958665


> Multiple researchers have discovered vulnerabilities in the way the
> Intel processor designs have implemented speculative forwarding of data
> filled into temporary microarchitectural structures (buffers). This
> flaw could allow an attacker controlling an unprivileged process to
> read sensitive information, including from the kernel and all other
> processes running on the system or cross guest/host boundaries to read
> host memory.

>> No.70959140

i would really like to see the face of a couple jerk companies asset managers which bought into the "xeon discounts" for their data centers only to have 50% of the performance taken away from them


>> No.70959152

Another year, another 5% performance lost to some fatal design flaw bug.

>> No.70959181

it's like 50% as hyper-threading must be disabled

>> No.70959184

How the fuck is the company still alive?

>> No.70959221
File: 2.65 MB, 320x240, 1554336135634.gif [View same] [iqdb] [saucenao] [google] [report]

Intel absolutely YEETED ON

>> No.70960375

>buy zion
>twice the price
>twice the power consumption
>half the performance
>1/4 performance per watt
>slash 30% cause spectre and meltdown
>now shave half of what's left cause lol fuck yo threads

those who bought xeon might as well replace them with raspberry pi clusters at this point

>> No.70960399

>hyper-threading doubles performance
The absolute state of this board

>> No.70960423

debian still not update the fucking microcode

>> No.70960442

are intel putting in those flaws on purpose to allow government agencies to spy on random people?

or is it just incompetence?

>> No.70960448

>hyper-threading doubles performance
for certain tasks. I would assume docker and similar server software will pay a penalty...

>> No.70960484

>Buy used xeon
>Same performance post spectre and meltdown patches as a Ryzen 2600 for 1/3rd the price
>Hyperthreading increase performance anywhere from 0% to 100% depending upon application
>Average is 20%
>Now have 0.8 of a ryzen 2600 for 0.33 the price
Still a good deal

>> No.70960499

At this point I'm using Raspberry Pis for mail, file, and web servers. They're slow but work alright for my uses. Just bought a new AMD ThinkPad A series. It's pretty nice. I also use PowerBooks with Debian. I'm torn between a Ryzen and a POWER9 workstation. I have $2500 allocated to either one.

I ditched my Intel laptop and workstation last year because I'm not retarded and knew it wouldn't be over soon.

Probably both. If you want to be safe you should get a SISD (single instruction, single data) processor. They're slow but not unusably so. A Raspberry Pi 3 is fast enough for basic web browsing and office tasks if you install a lightweight Linux or BSD distro and window manager

>> No.70960562

>30% performance loss for Spectre mitigation’s pushed out so far
>another 40% performance loss for this vuln on top of that
Intel CPUs are running approximately 28% as fast as they were two years ago, this is assuming you are running all the patches and turned off hyperthreading.

Literally more than two thirds performance penalty. Suddenly my Thinkpad X23 looks competitive again.

>> No.70961005

and the power consumption over the lifespan of the build?

>> No.70961073

People mocked me when I bought my fx eight years ago, who’s laughing now.

>> No.70961207

Ok, so there is no clear explanation yet, is this an actual "you are seriously fucked, they can hack you remotely", or it's another exploit that requires physical and admin access to the machine to be performed, which at that point you have way bigger things to worry about than cpu vulnerabilities?

>> No.70961227

they just want you to buy new chips, that's all

>> No.70961252

12-30 watts difference?

>> No.70961264

Feels good being a Threadripper owner.

>> No.70961305

Just delid + delap and everything will be fine goy

>> No.70961318
File: 8 KB, 140x135, 1553476374773.png [View same] [iqdb] [saucenao] [google] [report]

it's another speculative computing exploit. If they can see your kernel space, they can get whatever is in there. The fix wipes the buffer whenever its done with the data, with a penalty of 3-9% based on model, according to techcrunch. Yep, that's on top of your Spectre/Meltdown penalty.

I wish people actually knew how to read here.

>> No.70961338

That doesn't answer the question you fucking retard

>> No.70961348

The new chips has the same issues plus all the non-disclosed issues.

>> No.70961351

>tfw still on kernel 4.19
literally 30 years behind
thx AMD

>> No.70961362

forgot to include that hyper-threading buffer data is also up for grabs and is recommended to be disabled in coordination with the fix. Enjoy losing your extra threads.
of course, but you need a payload to do that for you and send it back. it's like you can't think for your self, damn.

>> No.70961380

> i can screencap but can't post links

>> No.70961388

that's not how it works, iTODDLER.

>> No.70961433

that's not how percentages work ya fuck

>> No.70961471

then who'll buy their newer botnet with fresh vulnerabilities?

>> No.70961489

They are cumulative dumbshit.

>> No.70961491

cringe and bluepilled

>> No.70961502
File: 580 KB, 1133x649, cpu_merchant.png [View same] [iqdb] [saucenao] [google] [report]

To ThreadRipper(tm)

>> No.70961504

Just update your kernel??

>> No.70961516

Up to 40% according to Apple

>> No.70961584
File: 763 KB, 1920x1008, 9E2EB270-A527-42DF-9146-0A1E516CF55A.gif [View same] [iqdb] [saucenao] [google] [report]


>> No.70961596

Wow, “only” 40%, that’s a whole lot better than 50%. I guess Intel in the datacenter still makes a lot of sense, what with “only” a 40% slowdown.

>> No.70961603

I really don't want to be the devil's advocate, but apple is moving to their own inhouse cpu's, I'd expect them to say that and give their customerbase the impression they must switch.

>> No.70961604

>used xeon
>same performance as a 2600
have fun with your dud, lmao

>> No.70961666
File: 72 KB, 287x344, 1420357652751.gif [View same] [iqdb] [saucenao] [google] [report]

Nice one

>> No.70961679
File: 239 KB, 500x573, 97B1EBDC-75D6-47F0-A461-7459572ED656.jpg [View same] [iqdb] [saucenao] [google] [report]

Intel Pajeet detected, the performance gains from utilizing hyperthreading are well studied and “about 40%” is accurate.

You should be ashamed of yourself.

>> No.70961717

oy vey

>> No.70961726
File: 361 KB, 2000x1700, master suicide list.jpg [View same] [iqdb] [saucenao] [google] [report]




>> No.70961764

>Anyone who disagrees with me is a shill

>> No.70961793

AMDrones anally raped by Intel for decades. 2019: nothing has changed.

>> No.70961801


>> No.70961813


>> No.70961816

Other threads have said this actually affects processors all the way to Cord Duo (2009) but Intel is gonna get away with ignoring the rest.

>> No.70961824
File: 61 KB, 224x314, debiru.png [View same] [iqdb] [saucenao] [google] [report]

Got a giggle out of me.

>> No.70961836

> he doesn't know amd have to pay intel royalties
AMDrones: anally raped for decades.

>> No.70961851

Intel is using AMD64, Intel has to pay AMD royalties.

>> No.70961884
File: 575 KB, 1140x642, 40e26a0ce64ebfcc169f95be003530ba7d8c393c527fa355e2afed6afad35682.png [View same] [iqdb] [saucenao] [google] [report]

>tfw the only intel cpu I own is in a thinkpad from 2006
Feels good.
By the way, does anybody know how this patch behaves on unaffected CPUs? I certainly hope I won't get a performance penalty on AMD, just because intel was greedy.

>> No.70961896


>To be able to exploit the vulnerability, no more is needed than hiding a few lines of malicious code on for example a website. A visitor that opens this site open, it will leak information.

>> No.70961930

Holy fuck, you are delusional.

>> No.70962011 [DELETED] 
File: 764 KB, 2089x800, 76BB0836-90B3-4F95-9CA2-66A7D3E33FE9.gif [View same] [iqdb] [saucenao] [google] [report]

>Intel Pajeet Cohens are now pretending that having to disable smt is no big deal and fake news
Honestly I’m not shocked, you retards will say anything no matter how bizarre and nonsensical it is.

>> No.70962014

baste and hyperthreaded

>> No.70962025


>> No.70962029

>50 percent is double

The state of your basic fucking math retard.

>> No.70962039

Based Jim. Fucking Lugenpresse

>> No.70962054
File: 1.58 MB, 320x240, welp.gif [View same] [iqdb] [saucenao] [google] [report]


I'd suck Jim's tiny Scottish sausage.

>> No.70962059
File: 218 KB, 576x432, 1554825268984.png [View same] [iqdb] [saucenao] [google] [report]

>Intel will continue raking in money because of their pseudo-monopoly on chipsets

>> No.70962068 [DELETED] 
File: 58 KB, 700x700, Intel30percent.jpg [View same] [iqdb] [saucenao] [google] [report]

Oh no, the iToddlers are going to be FURIOUS

Someone please update this with the 40% figure

>> No.70962072
File: 168 KB, 349x427, 719b7b96c64743a4f60844c3f1683d665d3c09ae897abb04d991e3602a487ac9.png [View same] [iqdb] [saucenao] [google] [report]

It is when you decrease by it. It's a third when add it. And you(?) decreased by it, meaning going from the remaining 50% back to 100% (by enabling ht) would be doubling the performance. Mathlet.

>> No.70962101
File: 18 KB, 632x755, mdstool.png [View same] [iqdb] [saucenao] [google] [report]

Post your processor vulns


>> No.70962144

Ahem, "i5".

>> No.70962184

amd doesn't pay intel royalties since at least 2003 retard

>> No.70962196
File: 132 KB, 837x956, thanks intel.png [View same] [iqdb] [saucenao] [google] [report]

this is pre-kernel update
rebooting now brb

>> No.70962257
File: 132 KB, 846x968, thanks again intel.png [View same] [iqdb] [saucenao] [google] [report]

feeling much safer already

>> No.70962274
File: 61 KB, 640x1012, JUST.png [View same] [iqdb] [saucenao] [google] [report]


>> No.70962280

you can't be this fucking stupid

>> No.70962289

nooooo bros delete this the goyim at the university were supposed to keep quiet

>> No.70962484
File: 319 KB, 1080x1920, Screenshot_20190515-154537.png [View same] [iqdb] [saucenao] [google] [report]

>non-free DBA

>> No.70962873

bad news for the 5 people who can afford intel quality processors and a good OS, yet still choses to use linux.

>> No.70963008

So this is where the tech industry is at.
Years spent building up a false sense of security and performance, with trash firmware on top of trash hardware, along with rising performance cost of running simple programs and websites.
now the quick fixes implemented years ago are catching up to INCEL processors and things will be slower than theyve ever been.
imagine if people actually started caring about optimization again because of this.
I doubt it, though.

>> No.70963033
File: 135 KB, 483x442, 1557693500969.png [View same] [iqdb] [saucenao] [google] [report]

oh no anon

>> No.70963059

>bad news for the 5 people who can afford intel quality processors and a good OS
fucking idiot, those vulnerabilities are on every OS.

>> No.70963080

You should be able to just add a kernel parameter to disable the patch if it behaves negatively on unaffected CPUs.


>> No.70963091

if you dont think 99% of this shit is just a bubble predicated on marking trends and funneling capital into 'tech startups' even though those tech startups are almost entirely predatory venture capitalists trying to make a quick buck

>> No.70963296


>> No.70963309

Don't forget the chiller!

>> No.70963312

Some people are Just retarded

>> No.70963330



>> No.70963368 [DELETED] 
File: 429 KB, 1066x600, 1525353398975.png [View same] [iqdb] [saucenao] [google] [report]

Hyperthreading doesn't matter

>> No.70963380

It's like a list of STDs

>> No.70963459
File: 85 KB, 1316x1634, 1557886015484.png [View same] [iqdb] [saucenao] [google] [report]

Why can't Intel stop being pozzed

>> No.70963480

WHAT IS THIS ? What is effecting storage speeds!?

>> No.70963539

syscall overhead is my guess

>> No.70963632

better: How fucked is Linux?

>> No.70963688

Fucking kikes

>> No.70963717

Debian doesn't upgrade the microcode all they do is upload Intel's patches to their repos.

>> No.70963719
File: 543 KB, 1414x657, 1557889101999.png [View same] [iqdb] [saucenao] [google] [report]

>Apparently Intel attempted to play down the issue by trying to award the researchers with the 40,000 dollar tier reward and a separate 80,000 dollar reward as a "gift" (which the researchers kindly denied) instead of the maximum 100,000 reward for finding a critical vulnerability.
>Intel was also planning to wait for at least another 6 months before bringing this to light if it wasn't for the researchers threatening to release the details in May.

>> No.70963765

>hyper-threading must be disabled
So my first gen i7 without hyperthreading will now perform like a modern i5 now? Nice.

>> No.70963852



>> No.70963858
File: 178 KB, 757x589, swiss_cheese.jpg [View same] [iqdb] [saucenao] [google] [report]

>400000 dollaridoos for finding a hole in the architecture equivalent of pic related
Based. I want that job.

>> No.70963890

40k is nothing, its probably split between an entire team.

>> No.70963912

Wonder why the processors that Jim Keller has worked on don't suffer from these flaws? Does he know something?

>> No.70963931

*modern i3

>> No.70964003

I'll take it.

>> No.70964016

so just setup a rasp pi or alternate desktop as a network connection pass through/filter and then no one can access your exploited intel.

>> No.70964240

AMD have a different kind of development philosophy which probably helps, then there's dumb luck.
PS. Please stop the Keller worship, he's good but is/was just a part of a team.

>> No.70964380

It seems AMD's engineers were more cautious and baked mitigations into the underlying hardware to avoid problems like this to begin with. Adding to that AMD didn't even support a full implementation of SMT until Ryzen. Bulldozer was a partial implementation and I don't think it was affected to the same extent.

>> No.70964435
File: 771 KB, 970x545, 1556152019676.jpg [View same] [iqdb] [saucenao] [google] [report]

I'm so sick of fucking restarting my computer for fixes because of your latest fuck up Jewtel! Get your shit together!

>> No.70964470

The team who discovered ZombieLoad has 4 members. That's still 10 grand each, not bad.

>> No.70964609

Fucking chump change. They can stream on twitch for like a week and get that return easily. Just by virtue of media attention.

>> No.70964626

If Intel offered much more than that for every vulnerability found, they'd be taken to the cleaners.

>> No.70964653

>Multi-Billion dollar company can’t afford to give at least a million in hush money per researcher per exploit.

That would be no more than what 500 million at this point? It's jews being jews. Thats it.

>> No.70964654

WHAT DOES IT MEAN FOR MY OVH KVM VPS I am on kernel 3.16.0-6-amd64

>> No.70964747

does not work here. MDS Tool
crashing during start. Have x5470

>> No.70964852

What does this mean for the i7 6950X?
Oh fuck please no

>> No.70964879

>calls others retards
>can’t even answer the question
Not based.

>> No.70964927

unless that money directly goes to AMD's bank account it literally doesn't matter

>> No.70964953


>> No.70964979

Based bulldozer was cmt, which scales pretty damn good desu.

>> No.70965003

Nothing overall. Keep installing security upgrades for the kernel, and upgrade to stretch before it runs out of support next year.

>> No.70965135


>> No.70965136

Glad debian stable gets buster now so that it will have an older kernel even in 4 years. Nice. I guess I am gonna stay like this for the next 7 years. Fuck the haters, I enjoy my holes.

>> No.70965149

why is arch still on 5.0

>> No.70965159

he doesn't know intel has to pay amd royalties

nu/g/ can't even isa x64

>> No.70965160

It gets backported you dumb incel

>> No.70965202

Linux 5's out already? What the hell they just started 4. Give it a few years and they'll be caught up to Chrome's retarded version numbering.

>> No.70965228

Can't get on my machine without any updates. My win7 install is from 2012 and never got any updates. Comfy shit without telemetry and a browser without javascript, flash or anything else.

>> No.70965234

Is a core 2 duo old enough not to be affected by this?

>> No.70965242

That's not how speculative execution works you stupid nigger.

>> No.70965251

Or just use a browser without scripts.

>> No.70965278

They jumped to 5.0 because they reached some number of commits on Github if I remember right.

>> No.70965296

What does this mean to my 4.9.0-9-amd64 ?

>> No.70965302

how is this even possible anons?
people sperg out screeching, flailing limbs, fiercely defending intel against anything, very concerning and damnable things, latching onto any piece of info that brings them a tiny bit of solace while cryying out that it isn't that bad, just to spite the 4 anons who would be same for the amd's side?

how the fuck can you live that?
what's the maximum amount of shit a fanboy can take from their fav tech company? (there's no maximum apparently, it's fucking infinite)

>> No.70965322

You cheeky bastard

>> No.70965324
File: 82 KB, 508x737, file.png [View same] [iqdb] [saucenao] [google] [report]

Lol, my cpu looks like a swiss-cheese.
Thanks Intel!

>> No.70965331
File: 2.00 MB, 250x158, 1316647238711.gif [View same] [iqdb] [saucenao] [google] [report]

>mfw currently on a core 2 quad from 2008
>mfw thought of upgrading to 9900k just a month ago but decided to wait for ryzen 3000

>> No.70965352

So this shit only affects you if you have hyper threading right?

>> No.70965378

AND no patch.

>> No.70965386

>>x86_64 Core linux 5.1.2.arch1-1
get better mirrors

>> No.70965403

Were the fuck do i find the patch then?

>> No.70965410

install arch

>> No.70965417

i'm not you're bitch and I have a ryzen.

>> No.70965423

>While programs normally only see their own data, a malicious program can exploit the fill buffers to get hold of secrets currently processed by other running programs. These secrets can be user-level secrets, such as browser history, website content, user keys, and passwords, or system-level secrets, such as disk encryption keys.

I don't understand this reasoning. If a malicious program has already made it into my computer, somehow doesn't it already have access to all this, no matter if there is a security hole? What's preventing any program from reading from the filesystem or the ram?

>> No.70965455

I am thinking the same way and I always loved the idea to be able to do this. I tried in the past with various hooks to read text from other programs but never got to do it and never understand the security risks. A program like tinytask combined with the functionality to read from clipboard always got me around.

>> No.70965466

user privileges
if you run your malicious program as root, you're fucked. If you run it as normal user in a reasonably configured system, you're supposed to have a chance to keep your secrets.

>> No.70965476


>> No.70965477
File: 90 KB, 501x918, not gonna update anyways.png [View same] [iqdb] [saucenao] [google] [report]

My whole GUI runs as root because I hate typing my password in.

>> No.70965479

The biggest problem are virtual machines actually.

>> No.70965483

my multihead setup doesn't work with newer kernels.

>> No.70965520

wtf? i tried many different mirrors but only get 5.0.12
whats your top mirror?

>> No.70965570

is this a list of STDs?

>> No.70965572

Everyone is still laughing

>> No.70965573

Never 4get

>> No.70965575

openBSD and Theo are ALWAYS right. They disabled hyper threading months ago and everyone said it was autism. I’m going to have to make a separate thread on all the times they were right.

>> No.70965586

Yeah, my CPU is a fucking slut.

>> No.70965666

>hate typing my password in
does not require
>GUI runs as root
fix your system

>> No.70965703


afterwards, use reflector to generate better mirrorlists whenever you miss something

>> No.70965826
File: 93 KB, 1095x1103, 2019-05-15-181450_241550780.png [View same] [iqdb] [saucenao] [google] [report]

why am I so vulnerable even though I patched :c

>> No.70965863

>fix your system
Yeah I had to fix quite a few lines to be able to login into gnome as root but it works.

>> No.70965916

I still don't understand why you think you need to run gnome as root to skip specific password checks.

>> No.70965995

Because Intel is a retarded piece of shit of a company with infected architecture.

>> No.70966075
File: 68 KB, 628x975, Capture.png [View same] [iqdb] [saucenao] [google] [report]


>> No.70966131
File: 153 KB, 953x1184, AAAHHHHHHH YAAAMAAATEEEEE.png [View same] [iqdb] [saucenao] [google] [report]

I'm fucked aren't I

>> No.70966178
File: 346 KB, 794x955, 1550007178633.jpg [View same] [iqdb] [saucenao] [google] [report]

so what will VPS providers do?
start offering a separate service for those with "sensitive data in memory" and charge a premium for it, everybody else is lumped onto their old unmitigated hardware?
(I apologize for giving them ideas)

>> No.70966179

>A Raspberry Pi 3 is fast enough for basic web browsing and office tasks if you install a lightweight Linux or BSD distro and window manager

What about programming?

>> No.70966194

Clean and beautiful.

>> No.70966211

>does not affect AMD and ARM chips

>> No.70966311

So much red...

>> No.70966322

Feels good to be on Ryzen

>> No.70966329
File: 992 KB, 250x250, 1537498548583.gif [View same] [iqdb] [saucenao] [google] [report]


>> No.70966644

what app is that? i want to check myself ;_;

>> No.70966662


>> No.70966671

Kikes on suicide watch

>> No.70966688
File: 86 KB, 644x1066, Capture.jpg [View same] [iqdb] [saucenao] [google] [report]

Oh fuck, im fucked. Gigabyte won't release any new bios for my mobo...

>> No.70966695
File: 214 KB, 960x847, 1557878302964.jpg [View same] [iqdb] [saucenao] [google] [report]


>> No.70966705

how the fuck do i downlkoad

>> No.70966717

Cloud providers already offer premium plans to customers who process sensitive data, and run them on separate hardware. These vulnerabilities enable cross-VM attacks only if the attacker and victim are running on the same physical core.

>> No.70966721

Microsoft will likely release a patch and intel will release a microcode update, I wouldn't worry too much.

The issue isn't the vulnerability (although that is AN issue), it's the eventual performance hit once the patches are released.

>> No.70966758
File: 33 KB, 486x927, Capture.png [View same] [iqdb] [saucenao] [google] [report]

Try reading whats in the link.

>> No.70966979

>more issues
God, fuck intel. Bunch of jew retards. I'm not giving up on my thinkpad though

>> No.70967099 [DELETED] 


>> No.70967114



>> No.70967194
File: 108 KB, 994x1020, nhel.png [View same] [iqdb] [saucenao] [google] [report]


>> No.70967205


>> No.70967235 [DELETED] 
File: 58 KB, 700x700, Intel30percent.jpg [View same] [iqdb] [saucenao] [google] [report]

Delete this anti-Semitic filth right now!

>> No.70967241

are you diagnosed with autism?

>> No.70967257
File: 1.14 MB, 3120x2945, IMG_20190515_133158.jpg [View same] [iqdb] [saucenao] [google] [report]

When the fuck are the new ryzens coming out I am fucking done with Intel and Nvidia

>> No.70967260
File: 67 KB, 428x961, mdstoolwin7.jpg [View same] [iqdb] [saucenao] [google] [report]


>> No.70967313
File: 40 KB, 600x360, EB07603A-DE31-495E-821C-D04DEAE92B98.jpg [View same] [iqdb] [saucenao] [google] [report]

They spent $450 million on hiring black people without STEM degrees to stand around just 3-4 years ago, just because Obama told them to.

>> No.70967334

Being root allows me to edit any file all over the system whenever I want by just using nautilus. Any terminal instantly opens as root without a password. Any program can write anywhere it wants. It's like in windows when having the UA deactivated. I never had problems with this setup in the last 10 years.

>> No.70967371

It's official: only autists can read

>> No.70967403

>it's another exploit that requires physical and admin access to the machine to be performed
it is exactly this. There is currently nothing that shows how a simple javascript website can read whats going on in another window. As long as this isn't the case I am not going to do anything.

>> No.70967407

i'm about to noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off on all these hoes I don't even care

>> No.70967455

what is a person without deep knowledge of modern kernel architectures supposed to infer from the phrases "speculative computing exploit", "kernel space", "hyper-threading buffer data", the guy asked him a simple question and instead of answering directly he decided to sperg out

>> No.70967479

You only need mitigations=off mds=off

mitigations=off encompasses everything except mds

>> No.70967483
File: 69 KB, 629x969, file.png [View same] [iqdb] [saucenao] [google] [report]

>cleanest intelfag ITT
Surely I'm getting false negatives right?

>> No.70967487

"All users *must* do _____" beats the whole point of using Linux

>> No.70967540

Realistically they will just switch to EPYC and Threadripper.

>> No.70967570

and offer those to premium users?
what will they do about their current hardware?
throw it out?

>> No.70967587

dare I say BASED

>> No.70967594

Well yeah. If your hoster is worth a damn they regularly upgrade their hardware. This one will just be another gradual update with the old hardware either thrown out or rented at a discounted till they are also gone.
I for one wouldn't take the risk or another 40% performance impact. At that point AMD is literally your only choice if you aren't clinically brain dead.

>> No.70967634

Programming can be considered a basic office task. Most text editors (not IDEs) do less than the average word processor. All the standard GNU dev tools and compilers you're able to run on Debian normally will run just fine on ARM. If you want an ARM v8 64-bit environment to work in, try Devuan's Raspberry Pi 3 build. It's quite nice.

>> No.70967651


>> No.70967656


>> No.70967702

Wouldn't it be 42% instead of 28% ?

>> No.70967714

i7oddler5 BTFO!?

>> No.70967778
File: 116 KB, 725x1007, vulns.png [View same] [iqdb] [saucenao] [google] [report]


>> No.70967841

Outside of the security fearmongering:
Was Spectre, meltdown and this vulnerabilities really that bad in the wild?

>> No.70967882

Nice one

>> No.70967902


>> No.70967959

So whats the deal anyways?
I heard that you can implement then in javascript, but also, you had to exploit a javascript bug in first place

>> No.70967961


For the love of god i cant find a download link on that fucking page

>> No.70967987

>Was Spectre, meltdown and this vulnerabilities really that bad in the wild?
They were patched so that they couldn't be exploited, with a painful performance cost.

>> No.70968011
File: 21 KB, 1573x73, 2019-05-15-21:37:11_1573x73_scrot.png [View same] [iqdb] [saucenao] [google] [report]

wew im fine!


>> No.70968095

But ironically no one could exploit them because the vulnerability was too specific

>> No.70968116

They’re doing this shit on purpose. Intel is compromised. Only way forward is power9.

>> No.70968135

You were never fine.

>> No.70968153

I can actually see this as a way for Intel to bail out of CPU sector, or just becoming the Nokia of smartphones

>> No.70968162

Bullshit, if it was then they would never have patched it given the steep performance penalty.

>> No.70968179

>step performance penalty
How much it was anyways?

>> No.70968183

app crashes when i try to open it o well

>> No.70968200

The fuck, I hated Satania in her series but love her now

>> No.70968220

No thanks

>> No.70968236

You are one stupid motherfucker.

>> No.70968277
File: 127 KB, 1200x1187, comfy Kat.jpg [View same] [iqdb] [saucenao] [google] [report]

I gotchuu familia
$ lscpu | grep "Model name"
Model name: AMD Ryzen 7 2700X Eight-Core Processor

>> No.70968296

RIDL, microarchitectural load port data sampling (MLPDS)
RIDL, microarchitectural data sampling uncacheable memory (MDSUM)


>> No.70968305

>check tonkpad
>Launch date: Q3, 2008

>> No.70968310

bad goy

>> No.70968409
File: 40 KB, 1064x988, JUST.png [View same] [iqdb] [saucenao] [google] [report]

First and last time buying israeli

>> No.70968427


>> No.70968443
File: 24 KB, 112x112, 3.png [View same] [iqdb] [saucenao] [google] [report]


>> No.70968508

I can't blame you, I almost bought a 5820k because it was mad value back then. Consider Threadripper if you need more lanes desu, I'm looking selling a 1700 for cheap and going all in on a 3950x if they don't skip TR this time around.

>> No.70968563


>> No.70968573

Hypothetically if I was a richfag with multiple PCs, I could just build with Intel and open up all these holes for dat speed but just do banking on my 2008 AMD laptop, yeah?

>> No.70968577

>apozzed tv

>> No.70968612

Adding poo to words isn't creative or amusing, you sound more mentally challenged than a literal child.

>> No.70968613

according to most of the pictures in this thread, nobody patched anything.
The anon you are refering is right though. There hasn't been any case known where this was used and oh boy, there are millions of unpatched windowx XP, 7, and linux boxes online.

>> No.70968819
File: 32 KB, 513x971, 1548826231971.png [View same] [iqdb] [saucenao] [google] [report]

>tfw vulnerable

>> No.70969003 [DELETED] 

This is also me
Waitfagging wins after all

>> No.70969012

If you want to get all your passwords stolen, sure.

>> No.70969042
File: 475 KB, 1024x573, amd-iedm-2017-35-1024x573.png [View same] [iqdb] [saucenao] [google] [report]

Why not wait for Zen3/4 going tall? Having a bunch of DRAM so close is going to be a huge increase in performance.

>> No.70969070

how will they dissipate all that heat?

>> No.70969077

Fucking kek. Congrats on the (you)s.

>> No.70969230
File: 36 KB, 648x981, oh no no.png [View same] [iqdb] [saucenao] [google] [report]


>> No.70969238

>crashing during start
My Avast kept trashing it so check your virus chest if you're a casual like me and use an AV, probably first time it bloody registered anything since I installed it too.

>> No.70969251
File: 35 KB, 412x441, 0e6.jpg [View same] [iqdb] [saucenao] [google] [report]

We're filled with comedians today, it seems

>> No.70969280

Maybe the ram shit isn't affected by heat that much

>> No.70969281

>there are millions of unpatched windowx XP, 7, and linux boxes online.
LOL! Do you seriously think someone running unpatched windows XP, 7 and Linux boxes online would have the technical know-how to determine that they have been hacked ?

And if they are unpatched there are likely easier exploits than Intel cpu bugs.

>> No.70969294

So we're going to fully integrate the RAM into the CPU? That's really neat.

>> No.70969305

OpenBSD doesn't have this problem because they disabled Intel SMT since 6.4

I still remember some of you spergs laughing about that


>> No.70969314
File: 11 KB, 270x287, 011.jpg [View same] [iqdb] [saucenao] [google] [report]



>> No.70969329


How? Heat management, hello?

>> No.70969378

>tripfag has literal autism

>> No.70969454

I don't have the slightest idea, but Intel is definitely going the same way before going chiplets. Maybe looking at some patents will give you an idea, I hear most of this stuff is already resolved.

>> No.70969471


>> No.70969476

filesystem, yes. ram, not really.

>> No.70969495

Hope not, that's the most recent Intel product I own and its nice to know its relatively unpozzed

>> No.70969585
File: 82 KB, 1280x764, Screenshot_20190515_170802.png [View same] [iqdb] [saucenao] [google] [report]


>> No.70969744

Hyperthreading is already turned off on scientific systems :)

>> No.70969834

They’re unavoidable. These speculation-related bugs will continue to pop up and there is nothing we can do as so much processor performance depends on speculative execution now.


“Spectre is here to stay: An analysis of side-channels and speculative execution”

>> No.70969982

>tfw 5 monitors
I'm using Linux-5.1.2 right now and it works just fine.

>> No.70969984

>“Spectre is here to stay: An analysis of side-channels and speculative execution”

>> No.70970299
File: 74 KB, 655x995, Capture.png [View same] [iqdb] [saucenao] [google] [report]

Fuck yeah

>> No.70970401

The Linux people are always fixing I tell problems in the kernel but does Microsoft do anything about it? I guess this affects any OS running on Intel, right?

>> No.70970666

based phenom

>> No.70970794

I love this meme and how it's used only in the most appropriate possible of postings and not spammed like /pol/, /v/, or /tv/ memes

>> No.70970814

>A Raspberry Pi 3 is fast enough for basic web browsing
if you use a text only browser maybe

>> No.70970837

I think Intel will stay pozzed forever, it's game over.

>> No.70970905


>> No.70970933

Paste and delided.

>> No.70970952


>> No.70970953

These are both terrible.

>> No.70970956

Still ahead of you pajeet.

>> No.70970974

aren't companies still buying intel cpus? apparently no one cares.

>> No.70970978

No, only indians.

>> No.70971031
File: 97 KB, 778x978, 2019-05-15_20-46.png [View same] [iqdb] [saucenao] [google] [report]

wtf amdbros i thought i was safe???????????

>> No.70971065

Slightly better than intel

>> No.70971241

Why am I so vulnerable compared to some other amd people here? Is it my os? bios? unlucky bulldozer cpu? I don't know what most of those vulnerabilities are.

>> No.70971869

Very, bring Linus back too.

Let's make a new kernel actually cos why the fuck not.

>> No.70972974
File: 773 KB, 3840x2086, mds.jpg [View same] [iqdb] [saucenao] [google] [report]


Good to know I've been making the right choice for sticking with AMD over the years. There are vulnerable Intel CPUs going all the way back to 2007 apparently

>> No.70972991

I don't think that's Linux fault tho...

>> No.70973213

>turned off hyperthreading.
why in gods name would I ever do such a thing?
I specifically paid extra to have hyperthreading.

>> No.70973360
File: 36 KB, 640x1022, mdstool-win64_2019-05-16_08-33-14.png [View same] [iqdb] [saucenao] [google] [report]

>ryzen is safe!

>> No.70973373

This a jewish trick, right? My Xeon station is behind a router and allows only signed ssh connections. Fuck your edge case 'hacker' scenarios.

>> No.70973555

lol. 9700k ftw

>> No.70973559

It's a risk if you run untrusted code.
If you don't, then you shouldn't really care. But for VPS providers, cloud services, etc (IE the big boys) their entire business model is running untrusted code.

>> No.70973560

The tool is designed for Intel processors only.

>> No.70973599

>their entire business model is running untrusted code
Anyone really gives a fuck?
Are they not insured?
If one cretin decides to somehow hack a fucking VM in a node somewhere, nuke him and move on. Who in their right mind will play with hacking virtual machines running ubuntu somewhere? This is all bullshit. If Jews decide to hack some machine I assure you they will use something better than a "newly discovered" public exploit.

>> No.70973607

Their customers care about not having their system's data breached, idiot. Insurance doesn't cover customers leaving and going to another provider because you won't install a patch that protects their data from Putin

>> No.70973627

>tfw bought a Xeon 2 weeks ago

>> No.70973644

that's not very free as in freedom of you

>> No.70973714
File: 33 KB, 695x1008, mdskeks.png [View same] [iqdb] [saucenao] [google] [report]

l e g e n d a r y

>> No.70973859

So we all go to amd?

>> No.70973920

never left

>> No.70973951

go read amds patents. they are pretty interesting.

>> No.70974012

based and redpilled

>> No.70974087

Witch cpu
I will look it, thx

>> No.70974376

RIP my i5 750
Well it's not like I'm ever going to get a mitigation in illumos anyway, considering how long it took to get one for meltdown. The ONE GUY who writes kernel patches is gonna have a mental breakdown soon.

>> No.70974385


>> No.70974404

Your CPU doesn't even have hyperthreading.

>> No.70974416

I know, that saves me from the worst of the exploit, but disabling hyperthreading alone doesn't fix it entirely. It'll just take longer to get usable data.

>> No.70974432

you mean kernel firmware? that's what fedora does to patch microcode

>> No.70974481

you have to be so dumb to think this is true

>> No.70974485

it means you will get 4.9.0-10-amd64 earlier!

>> No.70974552

This is a worst case from just disabling hyperthreading. Go look up benchmarks with and without hyperthreading, in the average case the difference is small, it didn't magically become more important because the disabling is a result of security fears. Also, with security fixes its possible to have hyperthreading on, the paranoid advice is to outright disable hyperthreading until kernel fixes/microcode updates address this, which will reduce performance much less

>> No.70974573

And the tool is so good that it can detect vulnerabilities on other processors too? amazing, good job intel!

>> No.70974579

Hyperthreadless 2500K has nothing to worry about right?

>> No.70974596

that's not how it works dumbshit.
reduced by 30% and then by 40% would be multiplying the initial by 0.7 (-30%) and 0.6 (-40%), giving you 0.42 the initial amount, 42%. Still intel is fucking dead

>> No.70974621

Store/fill buffers, and load ports are still needed to be rewritten when core switches between processes (at least untrusted ones), so yeah. Update is still recommended.
HT is just harder to mitigate due to required changes to OS scheduler (and I got no idea if it's implemented yet or not), but it's much harder to exploit too.

>> No.70974645

If you are running windows you have bigger troubles to care about than some CPU vulnerability.

>> No.70974745

You can do all of this by correctly setting up sudo and graphical sudo AND avoid giving root to random new applications. You say you had no problems, but in your setup, if you had some, you wouldn't notice.

>> No.70974881
File: 158 KB, 712x705, 38db29skq02bdbxkwo2ndbd93hq.jpg [View same] [iqdb] [saucenao] [google] [report]

>still using intel

It's like you brainlets were wanting this to happen

>> No.70974898

>tfw still using old i5 750 from 2009

>> No.70974924

It's too late anon, hackers are raping your info as we speak.

>> No.70975035

> bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds

>> No.70975045

One must wonder if they're "fixing" these backdoors because the Chinese found them.

>> No.70975144

welcome to the swiss cheese security hole club

>> No.70975147

Hey, I'm (>>70974376) not the only one.

>> No.70975155

>I don't know what most of those vulnerabilities are.
Probably why you are on /g/ right now.

>> No.70975180
File: 172 KB, 1234x1023, amd fear mongering.png [View same] [iqdb] [saucenao] [google] [report]

>vulnerable since dozens months
>never patched anything
>still secure

Can the AMD faggots stop spewing bullshit? Who cares about those cpu bugs, it's literally unexploitable.

>> No.70975300

Fuck yeah. So my non-hyperthreading i5-6300hq is a goddamn monster now.

>> No.70975311

>run malware JS on browser on X.org
>exploit can read memory of all other programs running on X.org session

>> No.70975367

I'm running Windows you dumb ass.

>> No.70975395


>> No.70975518
File: 66 KB, 605x328, 1557878082802.jpg [View same] [iqdb] [saucenao] [google] [report]


>> No.70975677


Let's say you do gaming. So you need steam. Your steam acct. is worth potentially thousands, and you HAVE to log in. Thus you need passwords, and security in general.

>> No.70975705


And those exact unpatched boxes are part of the glorious collective of botnets nowadays (hey anon why is my computer so slow all the time ? me: shudder)

>> No.70975784


If you somehow think that matters than good luck

>> No.70976032

If Intel didn't pay much for vulnerabilities, they'd sell the information to someone else instead.

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