[–]▶ No.847487>>847507 >>847513 >>847537 >>847599 >>847611 >>847620 >>847694 >>847748 >>847749 >>848301 >>849503 >>863684 [Watch Thread][Show All Posts]
Intel was aware of the chip vulnerability when its CEO sold off $24 million in company stock
https://archive.fo/rwC7y
It's all tumbling down now. AMD better take advantage of this moment.
▶ No.847488>>847505 >>847533 >>847701 >>849093
AMD has their own exploits they need to worry about
Still, this is a clear case of Insider Trading, which is illegal. I smell lawsuits up the fucking ass
▶ No.847490>>847499 >>847748
I'm tired of these rich faggots always getting away with their crimes. Hopefully justice catches up to him this time.
▶ No.847497>>847501 >>847747
i think nsa should just fuck up intel company, take a fuck load of money and use some money taken from intel and use it to have their guys patch it and distribute it for free
▶ No.847499>>847508 >>847722
>>847490
>rich faggots
Jews.
▶ No.847501>>847503 >>847635 >>847641
>>847497
You can't patch this vulnerability. It's in the hardware.
▶ No.847503>>847598
>>847501
Not him, but couldn't one possibly patch this on a UEFI-level? Would that make any major difference vs OS-level?
▶ No.847505>>848000
>>847488
They won't let anything happen to obedient goyim.
>“We think of ourselves as an Israeli company as much as a US company,”
t. shabbos goy and Intel CEO Brian Krzanich
▶ No.847507>>847513
>>847487 (OP)
> AMD better take advantage of this moment.
>wanting botnet
POWER 9
POWER 9
POWER 9
https://raptorcs.com/TALOSII/
▶ No.847508>>847510 >>873965
>>847499
>Jews
Bourgeoisie Jews
▶ No.847510>>847614 >>873965
>>847508
You'll be surprised how much "Bourgeoisie" jews exist.
▶ No.847513>>847521
>>847487 (OP)
>AMD
This is VIA's big chance to make it back into the western market, even if its just low end laptop crap.
>>847507
>vaporware that was supposed to ship last year
I want to believe in raptor, but they're making it really hard.
▶ No.847521>>847528 >>847706
>>847513
>vaporware that was supposed to ship last year
>vaporware
IBM has not yet released the POWER9 CPU to the general public yet raptor has to wait for IBM to release them.
Also since when google knows the intel cpu problem ?
https://siliconangle.com/blog/2016/04/07/in-blow-to-intels-data-center-reign-google-endorses-ibms-power-chips/
▶ No.847528>>847563
>>847521
IBM still makes microchip-hardware?
▶ No.847531>>847536 >>847538
red hat has already patched that
https://access.redhat.com/errata/RHSA-2018:0007
got my rpms, worked perfectly fine
▶ No.847533>>848139
>>847488
>AMD has their own exploits they need to worry about
like?
▶ No.847535
▶ No.847537>>847542
>>847487 (OP)
I was about to buy an amd computer, now I think I'll switch to intél
▶ No.847538>>847542 >>847545
>>847531
>tfw pajeets are the first to fix it
▶ No.847542
>>847538
Redhat is cianiggers ofcourse they already knew about it and had priot knowledge from jewtel.
>>847537
Don't get x86 CPUs from them.
▶ No.847545
>>847538
>to fix it
it's no fix it's mitigation
It also fix only half of it the other half is impossible to patch.
▶ No.847548>>847549
>bug in the physical workspace of a CPU
<fixed by software
plz
▶ No.847549>>847550
>>847548
yes, but you can prevent some things so that exploit could not be run on system
▶ No.847550
>>847549
The second it gets code execution it is over though. You would need perfect software security to achieve that.
▶ No.847555>>847561
>tfw poorfag
>tfw got a new intel cpu and was happy
>tfw I can never have anything nice happen to me
▶ No.847561
>>847555 checked
>trips confirm, absolute poorfag
▶ No.847563>>847565 >>847574
>>847528
>IBM still makes microchip-hardware?
Why wouldn't they ?
They just concentrated on specific branches of the market instead of the average user market like intel.
▶ No.847565
>>847563
I thought they just made shit using other companies microprocessors.
▶ No.847574>>847575 >>847579
>>847563
>I thought they just made shit using other companies microprocessors.
That's what AMD those silly.
AMD sold there manufacturing plants long ago.
To be honest IBM made their CPU via Global foundries until 2015 now they do it themselves.
▶ No.847575>>847579
>>847574
>those
>there
GET OUT PAJEET REEEE
▶ No.847579
▶ No.847598>>847621
>>847503
No. It's at the very core of the way the processor executes code. Nothing but new silicon will fix this.
▶ No.847599>>847601 >>847667
▶ No.847601>>847659 >>847662
>>847599
Power9 has spectre, but not meltdown.
▶ No.847611
>>847487 (OP)
>AMD better take advantage of this moment.
oy vey, that's so antisemitic! Remember 5.97288937464 gorillions!
▶ No.847614
>>847510
one bougie gentile disproves your entire worldview, but you are too retarded to see what is right in front of your face.
▶ No.847620
>>847487 (OP)
Finally made the decision to install uMatrix and set it up to allow only CSS and images by default, because these news triggered me.
Browsing with uMatrix is a lot better, it's really nice extension. Should be in every browser tbh.
▶ No.847621>>847629 >>847642
>>847598
is there any way possible to configure a router to block its connection or would that just block the whole connection? like say have your router block all botnet servers. i dont know much about networking and routers, my skill are more like bring pcs back from the dead...well the people that have handed me it thought it was dead so i just go along with it and i cant have them pay me cause i feel its kinda like getting out of your car to help a person fix a flat tire and that person knows nothing about cars and when your done you tell him to give you money...i cant/wont do that shit to anyone.
▶ No.847629>>847632
>>847621
You are getting into real security territory pajeet, lurk two years and you might figure it out.
▶ No.847632>>847634 >>847637 >>847671
>>847629
or you could be a good anon and just post a link that explains or explain yourself...
▶ No.847634>>847636 >>847637
▶ No.847635>>847638 >>847642
>>847501
what about a good router made for exactly intel and some how loop back the info to strip away the "bugs"{if you wanna call it that}?
▶ No.847636
▶ No.847637>>847642
>>847632
This >>847634 was not me who told you to lurk. But have some infos. Idealistically you could trust the software on the router, but you can't. So your router needs to act like a physical one way gate instead. Like a switch you can toggle on and off, but for data instead. You want to be able to request data at one point, and recieve it at another in a one way stream that is enforced at the hardware level. Look for ways or routers/hardware that enforce data transfers to be one way at the hardware level for a start. No more spoonfeeding, lurk now.
▶ No.847638>>847642
>>847635
lol do you have any idea what you are talking about
▶ No.847641>>847644
>>847501
You can patch it with a microcode update to simply disable the hardware and work with Microsoft Apple and the Linux community to make modifications at the OS level to not try and use that hardware, which is the option they are going with from what I understand.
▶ No.847642>>847643
>>847638
both me, does that answer your question?
>>847621
>>847635
___
>>847637
posting a link isnt spoonfeeding, after all this is /tech/ or am i on the wrong board, but thanks for the bits of info....
▶ No.847643
>>847642
>or am i on the wrong board
yes, you are on the wrong board. try a different imageboard entirely, in fact.
▶ No.847644>>847657
>>847641
You can't patch away the memory management unit MMU you gigantic faggot. It literally maps the memory of every device on the system. Without that you would have to manually specify the memory ranges in the program/kernel for every single type and variation of hardware out there. Including on hardware changes such as plugging in a USB drive or some such shit.
You might as well invent a new computing architecture while you are at it, seriously that is what is needed at this point.
▶ No.847652>>847664
i got nothing else to use fags! come at me!
▶ No.847657>>847661
>>847644
>MMU
https://en.wikipedia.org/wiki/Spectre_(security_vulnerability)
>Spectre is a hardware vulnerability with implementations of branch prediction that affects modern microprocessors with speculative execution
https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability)
>every Intel processor which implements out-of-order execution is potentially affected
Both are to do with branching and out-of-order execution logic, therefore it can be most likely patched with a microcode update and kernel modifications at the expense of system performance.
▶ No.847659>>847660 >>847665
>>847601
So rouge Javascript can only read all of user space memory and not kernel and user space memory? Preordering right now
▶ No.847660>>849096
>>847659
it won't be able to run that javascript with good enough performance anyway. you'll be waiting forever for pages to load.
▶ No.847661
>>847657
>where does the microcode reside in memory, the post
▶ No.847662>>847679
>>847601
>Power9 has spectre
Not a problem it can be patched via a firmware upgrade to the contrary of intel.
▶ No.847664>>847691
>>847652
>intel-microcode
>open source
Not possible. You can't update your microcode without a signed binary. Tell me how you got it.
▶ No.847665
>>847659
Javascript already does that with all devices. You shouldn't use Javascript in the first place, aspie.
▶ No.847667>>847679
>>847599
To the contrary of intel, power can upgrade it's firmware (no mandatory signature from IBM asked).
▶ No.847671>>847673
>>847632
>Thinking anyone here knows what they're talking about
Everyone here is LARPing
▶ No.847673>>847679
▶ No.847679>>847681 >>847682 >>847710
>>847662
>>847667
Read the spectre pdf
Part of it can be fixed with instructions upgrade (yes power can do that) but if IBM implemented branch prediction and speculative execution to maximize performance they are likely affected has well.
>>847673
not the anon you responded too
>>While makeshift processor-specific countermeasures are possible in some cases, sound solutions will require fixes to processor designs as well as updates to instruction set architectures (ISAs) to give hardware architects and software developers a common understanding as to what computation state CPU implementations are (and are not) permitted to leak.
-spectre pdf
▶ No.847681
>>847679
note:
I don't think that power is affected (But that's just speculation) tho since:
-it can be upgraded by anyone
-the architecture is very different
-google dumped intel in 2015 (and google researchers are partly responsible for the discovery of this)
-(((redhat)))
▶ No.847682>>847685
>>847679
>permitted to leak.
Wow, where do you think it is leaking from? From, memory perhaps?
▶ No.847685
▶ No.847691>>847692
>>847664
some good friend online
>You can't update your microcode without a signed binary. Tell me how you got it.
if you say so. what you want another screen shot?
▶ No.847692>>847693
>>847691
Hell yeah, pretty fucking big if you found the source to intel's microcode. Can you put up torrent or share a mixtape.moe link?
▶ No.847693
>>847692
That's those niggers at ubuntu, they mislabled the linux kernel ME communication driver for the actual microcode as a PCI device. There's no way in hell this nigger has the intel cpu microcode. Just absolutely no fucking way.
▶ No.847694
>>847487 (OP)
>The vulnerability, which affects processors from Intel, AMD, and ARM
Lol wat? Could they suck jew dick any harder?
▶ No.847701>>847710 >>847712
>>847488
That Intel shill posting here first.
Reuters is trying to spin this as a "global technology problem" which affects all computers.
The media in my country copy pastes that so now everyone thinks their AMD is affected by the performance drop as well when the security patches for Windows are released.
It isn't surprising that the CEO of Reuters is a Zionist.
▶ No.847706>>847712
>>847521
PCworld reported that the Google’s Project Zero security team first found the bugs and reported that to Intel in juli 2017.
(couldnt use archive for some reason)
▶ No.847707>>847711 >>847712 >>847800 >>848510 >>849212
>le cianiggers
>le pajeets
>le spooky parentheses
>le jews
Holy shit, this has become /g/.
▶ No.847710>>847732 >>849528
>>847701
Stop behaving like a nigger and read the spectre pdf >>847679
AMD is affected but not has much has intel, same for ARM.
POWER isn't mentioned at all in the PDF and only redhat said something about it but since redhat is gets money from intel I don't trust what they say.
▶ No.847711>>847713
>>847707
Your new is showing kiddo
Back to cuckchan
▶ No.847712
>>847707
No, more like anyone who cares and understands this issue ever so slightly isn't a kike or a pajeet. If you had lurked two years you would realise the cianigger thing is real.
>>847706
That would make sense since jewgle has been trying to switch to powerpc on their data servers since 2016.
>>847701
Well one bug affects all proccessors and the other only affects intel, for now.
▶ No.847713>>847714 >>847919
>>847711 (double-checked)
Since last month there's an influx of cuck/g/ refugees and ledditors on this board.
▶ No.847714
>>847713
Yea some faggot linked the old cpu bug thread straight onto plebbit. They mentioned it in the thread.
▶ No.847722
▶ No.847725>>847728 >>847872 >>848057
1.) Please do not listen to retarded Redditors, this has nothing to do with syscalls, the performance penalty only comes from Usermode Programs that need to access Kernel Mode memory through virtual memory
2.) Video game benchmarks show a 0 percent performance hit since video games do not need to access kernel mode memory, it's likely 99 percent of normal users will both notice a difference in performance whatsoever. Gaming, web browsing, even software compilation and video editing, are generally not seeing any performance penalty
3.) Database programs like SQL that need to access kernel mode memory from usermode many times a minute will see the biggest impacts on performance. SSDs in Nvme mode will also see a performance hit
4.) The largest performance overhead seen, the ballpark number of 30 percent, was seen through synthetic benchmarks and may not reflect real-world use cases.
5.) PTI and FUCKWIT (Forcefully Unmap Complete Kernel With Interrupt Trampolines) are likely a quick and dirty solution to the problem and better optimization of user and kernel memory partitioning can mitigate performance impact
6.) This is less a bug and more of an oversight by Intel (which is almost worse depending on how you look at it) basically Intel CPUs prefetch memory for performance reasons but do not consider what memory in the prefetcher is otherwise marked as protected by the OS kernel, bypassing kernel read checks to userland.
▶ No.847728
>>847725
Well how are they meant to spy on you if they let things be properly protected?
▶ No.847732>>847734
>>847710
Kike pls.
The spectre vulnerability isnt the bug responsible for the performance drop of up to 30% on the Intel processors.
▶ No.847734>>847737
>>847732
Neither bug is responsible for the 30% performance drop. The "fixes" are responsible.
▶ No.847737>>847738
>>847734
Since leaving the vulnerability on Intel unpatched is a huge security risk, I see the cause in Intel's design flaw, not the patch.
▶ No.847738
>>847737
>huge
Huge isn't the word to describe this shit.
"Point blank gun to your head" is better
▶ No.847747
>>847497
>implying men on NSA's payroll aren't the ones who devised the exploit
Are you really this naive, or..
▶ No.847748>>847765 >>847945
>>847487 (OP)
>>847490
Porky at's finnest.
▶ No.847749>>847750
>>847487 (OP)
This is why I don't understand why people don't want to hang the bourgeoisie.
▶ No.847751>>847756
>>847750
Steinbeck never said that but it is a pretty true quote whoever did.
▶ No.847756
▶ No.847763>>847825
This is why there should be a law, a tax, on devices which contain computers possessing re-writable software memories but which either actively prevent user writing via hardware means (if user had the JTAG hardware) or via cryptographic signature, and/or also fail to publish interface specs (hiding such specs would be anti-competitive/monopolistic behavior). If I wrote that tax law, the tax would be 100% on FINAL PRODUCTS so even Tesla cars have to open their computers or suffer their basement models never ever starting under $60K ever, and iPhones no less than $1.5K. This tax needs to apply to everything. It, basically, won't ban such proprietary hardware, but it will make it so expensive that normal users won't buy it and therefore companies like Google doing things like "No root for user" Android couldn't pull that shit anymore. It should even apply to firmware on motherboards: cryptographic keys must be replace-able and even the CPU microcode must be editable by the user. That doesn't mean source code released, it simply means the user can replace the binary firmware with his own and not have the computer 'fail' simply because it didn't pass the OEM-approved firmware check. The money from this tax would be legally limited to going toward funding FOSS projects.
If anyone is serious about national security, this tax plan will happen.
▶ No.847764>>858168
This would never have happened if people used rust.
▶ No.847765>>847769
▶ No.847766>>848025
>>847750
Steinbeck books were garbage. All of 'em! Hated every single one. Shakespeare is football fields above this dingus in writing and story telling!
▶ No.847771>>847773 >>847860
>>847769
ow my eyes
>supporting starbucks, which is owned by a known zionist
▶ No.847772
https://web.archive.org/web/20180104131631/https://reviews.llvm.org/D41723
Enjoy recompiling everything with a performance loss for virtual calls gentoofags
▶ No.847773>>848633 >>874267
>>847771
>think that leftypol or leftpol are liberal
▶ No.847800
>>847707
Back to cuckchan.
▶ No.847825>>847827
>>847763
>The money from this tax would be legally limited to going toward funding FOSS projects.
Google has had this fixed in their back end systems for almost a year. Apple rolled out the patch in OSX last month.
>https://9to5mac.com/2018/01/03/mac-fix-for-intel-kernel-bug/
Like normal freetards are behind the curve again when it comes to security.Why reward shitty performance?
▶ No.847827>>847830
>>847825
>Like normal freetards are behind the curve again when it comes to security.Why reward shitty performance?
Linux kernel was the first to patch the intel bug, faggot. Go suck proprietarydick somewhere else
▶ No.847830>>847833 >>847837
>>847827
Wrong. OSX patched this last month. It was part of 10.13.2 on 12/6/2017.
▶ No.847833>>847837
>>847830
Great, maybe they can patch the rest of the OS to not be a huge botnet.
▶ No.847837>>847838 >>848329
>>847830
What the fuck? How did Apple know about this vulnerability before Microsoft and the Linux developers?
>>847833
>doesn't know any actual lingo so he just spams the word "bontet"
Go away.
▶ No.847838>>847843
>>847837
>Go away.
Are you too stupid to know what botnet means?
▶ No.847846>>847851
>>847843
No, but considering I typed it and it triggered you so badly that I didn't use "lingo" and list everything wrong with macOS I'd say you are the double digit IQ autist.
▶ No.847851
>>847846
macos may have shitty UI and userspace devs but their kernel team is clearly topnotch. They beat linux by a month on this. Linux didn't get a patch out until the same day M$ did. That has to be humiliating if your a linux-kernal dev.
▶ No.847860>>848169
>>847771
You have poor reading comprehension, like most of your ilk.
▶ No.847872>>847910
>>847725
Thank you Purch Media Friend. I am glad all this FUD is dying down and I can enjoy my new Intel™ Core i7™ 8700k for superior gaming performance. I knew this would only affect a few people and it was all being overhyped.
Thank you for being a sane voice in all the chaos. I sure would hate to be a stupid redditor™. But thanks to your post, I can buy Intel™ Core i7™ products with out any worries or concerns about my gaming performance. I thought I would have to switch to AMD, but it seems I don't have to settle for an inferior CPU and I can purchase an Intel™ Core i7™ CPU with confidence!
▶ No.847904
Martha Stewart got in jail for much, much less.
▶ No.847910>>848022
>>847872
Don't even jokingly reply to the retard
▶ No.847919
>>847713
Saifag can stay, but the rest have to go back.
▶ No.847945
>>847748
>Porky at's finnest.
Yes. (((Porky)))
>>847769
Pic related
On a thread related note, being busted for insider trading is not a good look. He will probably go down because he is not a company.
▶ No.847955
>>847947
>>hurr I bought something and it wasnt perfect fuck rich people n shit
Go back to /pol/, you illiterate bootlicker.
▶ No.847962>>847964
>>847947
>how dare you dislike criminals! Off to jail with you for your thoughtcrimes!
▶ No.847964>>847971
>>847962
>selling faulty products is criminal
▶ No.847971>>847976 >>847981
>>847964
>false advertising and insider trading is legal
▶ No.847976
>>847971
It's legal when the US government gets a piece of the pie.
▶ No.847981>>848026
>>847971
Basically, yes. There are various ways to structure share sales to let you get away with insider trading - see rule 10b5-1.
False advertising is similarly easy to get around as seen at every E3.
▶ No.848000
>>847505
that's because Occupied Palestine and the USA are the same by now
▶ No.848022
>>847910
> reply to the retard
say,anon,what's a cpu?
▶ No.848025
>>847766
I think this is more yor level
▶ No.848026
>>847981
t. literal inbred
▶ No.848057
>>847725
>Someone reposted the post I made on /newsplus/ (or was it /n/?)
Well that's unexpected
▶ No.848093>>848104
<tfw have three functioning P4 machines from the early 2000s
<unseal the hushed casket
▶ No.848104>>848106 >>848129 >>848179 >>848271 >>858173
>>848093
Still fucked by spectre.
P3s MIGHT be okay but P2s are the last known safe Intel CPU.
▶ No.848106>>848119 >>848143
>>848104
Any suggestions beyond giving up computing forever.
▶ No.848119
>>848106
wait for intels next gen :^)
▶ No.848129
>>848104
I gave a p2 to a friend for safe keeping and the faggot lost it. How the fuck do you lose an entire desktop computer?
▶ No.848139
▶ No.848143>>848266
>>848106
Switch to newer RISC-V chips or older powerpc chips and ignore the cianigger A.I. Newer jewgle CPU's are most certainly botnets by design.
▶ No.848169
>>847860
If you say so, sheklestein
▶ No.848179>>848180 >>848265 >>848271
>>848104
THE FUTURE IS NOW
▶ No.848180
>>848179
Year of the Linux Desktop.
▶ No.848265
>>848179
AMIGA WILL RISE AGAIN
▶ No.848266
▶ No.848268
>>848267
stop shilling your pay to view site kike
▶ No.848271
>>848104
>>848179
>P2s are safe
Try again, every Intel processor since the Pentium Pro has had speculative execution.
▶ No.848296>>848300
>>848267
If intel isn't the only one affected why is it only intel pursuing this? Pretty sure AMD not affected here. No I didn't read your pay to view article. Also no one should trust the ft.
▶ No.848300>>848303
>>848296
>Don't trust one of the world's most prestigious news sites, trust some faggot on a chan instead!
▶ No.848301
▶ No.848303>>848304 >>848307
>>848300
>(((prestigious news sites)))
I never heard of it till today, but your nose is showing
▶ No.848304>>848310
>>848303
>Never heard of the Financial Times
No excuse unless you're a nigger living in the middle of the Sahara desert, dumbfuck.
▶ No.848307>>848310
>>848303
>I've never heard of the Financial Times.
How's Middle School treating you.
▶ No.848310>>848311
>>848304
>>848307
>caring this much about what kikes think
▶ No.848311
>>848310
This isn't /pol/. If you actually care you can read more about it from here.
https://meltdownattack.com/
▶ No.848329
>>847837
>What the fuck? How did Apple know about this vulnerability before Microsoft and the Linux developers?
I know Linux developers were aware at least a month ago, since I heard about the CVE back then. I wasn't told what the issue was, just that it was coming down the pipe.
▶ No.848510
>>847707
Look at you, you are so smart! I wish I could be as ignorant intelligent as you!
▶ No.848523>>848547
Lol. OpenBSD patched this in 2007
▶ No.848547
>>848523
Lol. No. And they'll probably never patch it because they'll call fixing this "bloat" like they usually do. Then a decade later they'll patch it and call it new, revolutionary, never-before-seen, and the first os to have the patch.
▶ No.848552>>848558 >>848564 >>848594 >>849100
So why aren't Windows users seeing any real performance penalty as a result of the patch?
My theories are as follows;
1.) Windows is technically a microkernel A very monolithic-like microkernel do to decades of "integration" between components but they could very well still have more flexibility, obviously we'll never know as to the extent since Windows is proprietary so that means in theory its possible to minimize any possible reads/writes to kernel memory from userspace. Linux conversely is monolithic so that means a huge chunk of the system must be dedicated to kernel memory
And theory number 2.) Microsoft simply put any entrypoints for the exploit under a blacklist and called it a day
▶ No.848558>>848560
>>848552
Theory #3: Your wife orbits my dick and you're a retard. It's been talked to death already that this "30%" figure is bogus, and only applies to specific workloads of the sort you see in servers. Most tasks are only affected marginally.
▶ No.848559>>848599
I would not be surprised if this was brought on by these companies. Now governments will be buying supposedly "fixed" chips and creating a surge in profits for these companies.
▶ No.848560>>848564
>>848558
Benchmarks prove that there is a hit with FS I/O in synthetic benchmarks, but only for SSDs, in addition SQL also took a hit, but again, that was only a synthetic benchmark.
The performance hit is there, but 99.9 percent of users will never see it since it only effects usermode programs that want to access kernel memory, and most applications do not need to do this. I think there was a big scare in the Linux community simply because of Linux' monolithic nature so it was speculated this would happen a lot. A big aspect of the performance hit is system design. That's why OSX patched it awhile ago and nobody noticed a difference. OSX is a microkernel in a manner similar to Windows
▶ No.848562
This is definitely anti-Schematic
▶ No.848564
>>848552
>>848560
holy shit when will you finally fuck off
▶ No.848594>>848598
>>848552
>So why aren't Windows users seeing any real performance penalty as a result of the patch?
Theory #4
They haven't actually enabled the patch, despite thinking that downloading it does the job?
PS: don't forget to fuck around in the Registry to make sure AV suites don't barf...
▶ No.848598
>>848594
The patch comes from an update
▶ No.848599>>848603
>>848559
They could just like build their own SPARC systems instead, like Russia.
▶ No.848603
>>848599
The US sockpuppets ruling the EU won't.
▶ No.848633
>>847773
>thinking youre special
You guys sure sound like them.
▶ No.849093
>>847488
AMD's exploits aren't nearly as big of a deal as Intel's, you butt fucking shill.
▶ No.849096
>>847660
Why would you just go on the Internet and lie like this?
▶ No.849100>>849102 >>849106
>>848552
>So why aren't Windows users seeing any real performance penalty as a result of the patch?
They do, for IO. SSDs can get bottlenecked by intel CPUs now.
▶ No.849102>>849115
>>849100
Also consider that most people have massively overpowered hardware for light browsing / email / office tasks.
What kind of ordinary user pegs their hardware these days anyway?
▶ No.849106>>849117 >>849120 >>849139 >>849240
>>849100
Even on synthetic benchmarks SSD performance is well above HDD performance. I sincerely doubt anyone will notice a difference in SSD I/O now either
▶ No.849115>>849118
>>849102
> light browsing / email / office task
which are all using massively bloated web frameworks now.
the average goy does this all in the cloud in javascript which pins these cpu's on a regular basis.
▶ No.849117>>849119
>>849106
>Even on synthetic benchmarks SSD performance is well above HDD performance.
What has that to do with anything? Just because SSDs are still faster than HDDs doesn't mean they aren't affected. I/O is affected, that's a fact.
▶ No.849118
>>849115
>the average goy does this all in the cloud in javascript which pins these cpu's on a regular basis.
I think I'll take this statement with a grain of salt and say that you're talking out your ass and much to the dismay of corporate giants who want your data, the average end-user uses "DA CLOUD!" a lot less than you probably think
▶ No.849119>>849122
>>849117
Didn't say they weren't you gigantic sperg, but the average user will likely never see the difference. The average program does not require synthetic-benchload levels of I/O that pegs your SSD to 100 percent
▶ No.849120>>849121
>>849106
browser cache performance is going to get wrecked by this. they all use memory cache obviously but they also write this shit all over the hard drive, and the browser will stop the whole show if the disk cache hasn't responded yet. try pinning you I/O and surfing the web in pozfox.
▶ No.849121
>>849120
web cache fetching and filesystem paging would likely get bottlenecked by software way before they get bottlenecked by the security patch
▶ No.849122>>849125
>>849119
sure your not going to see the IO drop in light use your just going to see 30% more cpu usage doing it.
▶ No.849125>>849163
>>849122
In practice the actual performance impact is a lot less than 30 percent and you know it
▶ No.849139>>849153
>>849106
I'm not sure where you're going with that goalpost.
▶ No.849153
>>849139
I said any real performance penalty, the goalpost is still firmly planted in the grass
▶ No.849157>>849158 >>849167
>>849147
The collage would be perfect if it didn't have that subtle shill for ARMshit
▶ No.849158>>849167
>>849157
>>849147
The retard who made it also did a really shitty job at cropping some of his screens
That fuck does South Korea trying to appeal to the Norks have to do with Shitel?
▶ No.849159
Also, who do I hear a lot of retards saying this is a microcode update? I thought meltdown couldn't be fixed in microcode
▶ No.849163>>849165 >>849327
>>849125
>320x180 PNG
>still 4.05MB
Either it's animated and my browser can't display it, or there's something hidden in that file.
▶ No.849165>>849327
>>849163
>His browser can't read animated .pngs
Update your shit Jesus
▶ No.849167>>849169 >>849176
>>849158
>>849157
>>849147
Fixed, also don't know what compression the retard was using but that file doesn't need to be 15 megs
▶ No.849169>>849172
>>849167
>not liking a polyglot file with a bootable dosbox image which plays initial d midi files included with your image
▶ No.849176>>849177
>>849167
If this were endchan, I would've posted the entire 60mb
https://chiru.no/u/intel_collage.png
▶ No.849177>>849181
>>849176
>I would've posted the entire 60mb
but...why?
▶ No.849181>>849182
>>849177
it's 60mb worth of images
▶ No.849182>>849184
>>849181
How do you measure this when it can just as easily be compressed to 10MBs with negligible loss in quality?
Do you have brain damage?
▶ No.849183>>849186
probably a stupid question but what's the difference between the current layer of protection for intel and a vm? they both restrict access in the same way near as i can tell.
▶ No.849184>>849186
>>849182
it all looks like shit if you've seen/worked with the source
▶ No.849186>>849187 >>849190
>>849183
It really all depends on how the VM accesses kernel memory from usermode
>>849184
wtf you're right I'm just going to upload my 60MB RAWs to image sharing websites from now on because that's sure practical for all parties involved and totally worth the extra 2% resolution
▶ No.849187>>849189
>>849186
wow great argument fagtron you sure convinced me with those hot opinions
▶ No.849189>>849191 >>863670
>>849187
>Actual, measurable memory space and bandwidth being wasted
>opinions
▶ No.849190>>849192
>>849186
well cisco has been patching their esxi machines for months now where there's essentially (it's a linux kernel) no host, but i can't imagine the base instructions for the processor being that bad.
▶ No.849191
▶ No.849192>>849194
>>849190
Aren't those essentially hypervisors? I would imagine any potential performance penalty s far as hypervisors go would be no different than bare metal
▶ No.849194>>849198
>>849192
i hate the term bare metal, because it's still just a kernel.
the added overhead from the patch seems pretty low, but it looks like stacking vms to me.
▶ No.849198
>>849194
It pretty much is in essence
▶ No.849212
>>847707
>le back to reddit
▶ No.849240>>849242
>>849106
Except, you know, the people who would notice, who will notice a lot.
Like video editors for instance.
▶ No.849242>>849488
>>849240
Even in video editors, the video decoder would ultimately bottleneck you well before filesystem I/O does. And video decoding is not affected by PTI whatsoever if the benchmarks mean anything
▶ No.849327
▶ No.849476
>>849147
chiru back at it again
▶ No.849488
>>849242
>decoder
Decoding isn't the intensive part you dipshit.
▶ No.849503>>849531
>>847487 (OP)
So will a BIOS update be needed as well as a kernel/OS update?
▶ No.849510
▶ No.849528
>>847710
If you have armv7 on OpenBSD, then you're basically not affected at all.
https://marc.info/?l=openbsd-tech&m=151527717000808&w=2
armv7 port is these boards:
https://www.openbsd.org/armv7.html
BTW, the Beagleboard and Pandaboard are good choices, as they can be used without non-free software.
https://www.fsf.org/resources/hw/single-board-computers
▶ No.849531
>>849503
>BIOS
kek nobody's making computers with BIOS any more kid
▶ No.858102
▶ No.858168>>863619
>>847764
CPU written in Rust when?
▶ No.858173>>859702
>>848104
P3 was basically P2 with SSE vector units added you humongous faggot. Literally identical core otherwise.
▶ No.858231
I find it ironic that intel is getting wrecked by AMD Bulldozers.
▶ No.858797>>858818 >>858821
>Leo: It was kind of funny last week because you talked about what were later to be dubbed Spectre and Meltdown. And you were kind of matter-of-fact about it. I mean, I heard it. In fact, I even mentioned, gee, that sounds kind of like Rowhammer. But I don't know. You must have understood its impact, but I didn't.
>Steve: I did. And as you know, I don't like to go, like, overhyping things and running around with my hair on fire. So I got a little down into the weeds about the performance impact of being forced to flush the virtual memory, the so-called Translation Lookaside Buffer caches, whenever you made a switch from the app to the OS, which is potentially huge. And I got into, like, explaining what this meant, that it was possible with the Meltdown attack. And so this was the day before then the full disclosures came out that there was so-called Meltdown and also something called Spectre.
>Leo: Yeah, we didn't know that much on Tuesday because it was just a hint. We hadn't seen the full report till Wednesday.
>Steve: Yes, it was from looking - it was like weird footprints in the Unix source where comments had been redacted that normally wouldn't be, and the explainer page for the changes was missing. And it was like, and then news that Microsoft had been scurrying around, I mean, there wasn't anything definitive. Now we know way more. So I titled today's podcast "The Speculation Meltdown" because, sort of taking more of the 10,000-foot view of this, believe it or not, there was a paper written in 1992 which recognized this problem.
>Leo: What? What?
>Steve: Twenty-five years ago.
>Leo: Oh, that's not good.
>Steve: And it was then referred to in more detail three years later, in '95, about like how this kind of thing could happen. And back then it was, oh, but, you know, that would be too hard. Or no one's going to bother with that. And so we, the industry, and not just Intel, but as we know now all of the major chip vendors, AMD and ARM, are all subject to these problems.
>The reason is that this has been the way, the so-called "speculation" has been the way all high-performance modern processor architectures are able to continue to squeeze phenomenal performance out of the system. And so this is not just Intel, as we know. And in fact, I was distressed to see that there were some class-action suits that were being filed immediately in kneejerk reaction to this, which I regard as absolutely unfortunate. But anyway, we'll get to all that.
>I formulated a general law of cross-task information leakage which reads: "In any setting where short-term performance optimizations have global effect, a sufficiently clever task can infer the recent history of other tasks by observing its own performance." And I worked on that for a while. "In any setting where short-term performance optimizations have global effect, a sufficiently clever task can infer the recent history of other tasks by observing its own performance." Which that's like the meta statement of the problem of how there has always been, and that's what's so interesting about this, there has always been this problem.
>And what happened was that sort of, I mean, and this is classic security paradigm that we see over and over and over, is that something that was sitting there for a long time, somebody stubbed their toe on and said, "Ow, wait a minute, what's that doing?" And suddenly it's a big deal. So we're going to have fun at the end of the podcast talking about, again, sort of not like which patch to apply or what to do immediately, but where this problem came from. What's the origin of something which, without overhyping it, is probably not overstating it to call it an "industry-wide catastrophe."
https://www.grc.com/sn/sn-645.htm
https://media.grc.com/sn/sn-645-lq.mp3
▶ No.858818
>>858797
>I was distressed to see that there were some class-action suits that were being filed immediately in kneejerk reaction to this, which I regard as absolutely unfortunate.
oy vey
>so-called "speculation"
speculations sounds bad let's call it something else to confuse the goyim
>I formulated a general law
all computers have this problem goy!
> this is classic security paradigm
this is nothing new! intel didn't do anything wrong!
> there has always been this problem
don't worry about this goy, it's always been there, keep logging into facebook
> we, the industry, and not just Intel, but as we know now all of the major chip vendors, AMD and ARM, are all subject to these problems.
you can't blame intel goy the entire industry is suffering you should go out and buy more products to (((empower))) us to create more solutions.
▶ No.858821
>>858797
http://seclists.org/nmap-announce/2001/25
"
Steve Gibson is a media slut and should be treated as such. If you look
at how he writes up things on his own web site, you can see they're made
to look just like how they might in print. In my surveying of what he's
done, he's done...well...nothing very exciting. His "nanoprobes" were
really lame (a different spin on what nmap does) and if people would
just start ignoring him, we'd be much better off.
[ Moderator note: I agree 100% with Darren & Andy. Gibson is a
charlatan whose "research" is written for clueless media reporters
(for press attention) and the teeming masses of internet newbies (to
whom he sells various products). His "findings" are not new, are
always filled with massive hyperbole, and are frequently completely
false. Instead of presenting evidence to prove his points, he tends
to just state them using goofy blue or green fonts as if that
somehow adds credibility. We recommend avoiding this guy!
-Fyodor ]
"
▶ No.859702
>>858173
>P3 was basically P2 with SSE vector units added
And Pentium II was basically Pentium Pro with MMX added. That's why all of Pentium Pro/II/III are considered the same architecture (P6/686).
▶ No.859730>>859734
What will be the endgame for all the hardware that will remain vulnerable to Spectre? Viable usage only airgapped and Faraday-caged (to prevent WLAN/Bluetooth etc. compromise) environments? Connecting to the internets viable only on whatever new ""safe"" platforms are going to be provided in the future? Considering the gravity of changes that will need to be made, and the impending final end of support for BIOS in 2020, could the outcome be the death of the x86(-64) platforms and the PC in general? Will the 40th anniversary of the Personal Computer be celebrated at its freshly-dug grave?
▶ No.859734>>859742
>>859730
Spectre can easily be fixed with software updates. Embedded shit vulnerable to Spectre will die in 2038 anyways do to the Linux time_t overflow since most embedded shit is 32-bit still
>could the outcome be the death of the x86(-64) platforms and the PC in general?
Kill urself my man
▶ No.859742>>859743 >>859748 >>873869
>>859734
You do realize that a PC is to people born after 2010 like a typewriter was to people born after 1980? Something that still exists and is in more or less widepread use, but on its way out and about to be replaced by something else. For those now growing up the natural computing devices of choice are smartphones, tablets, chromebooks, or macbooks at best. They don't care about having control over the hardware or software they're using and don't care about having a copy of the media files they consume, being perfectly fine with doing so via Youtube, Netflix or Spotify. The world has changed very much and is still changing. In the 80s we had a major shift from the "teletype and mainframe" to the "personal computer and open internet" paradigm, and now the change from the latter to the "smartphone and cloud" one. Dunno about you, but to me seeing the PC platform's future as threatened in the coming years seems not overly farfetched.
▶ No.859743>>859756
>>859742
>You do realize that a PC is to people born after 2010 like a typewriter was to people born after 1980?
The retard is still talking...
▶ No.859748>>859757
>>859742
I'm sorry but you are 100 percent wrong and have no idea what you're talking about. PCs and Smartphones aren't mutually exclusive markets. And there is absolutely nothing as far as real world industry trends to reflect that. PCs aren't going anywhere. There are roughly 2 billion PCs in use and there's no signs of that changing. Smartphones aren't killing PCs, the problem is the average normalfag household of 5 people will have 5 Smartphones, one per person, and typically a single PC for the whole house. PCs also have a longer service life than Smartphones. The PC market slowed down considerably in the 2010s but that has more to do with the market stabilizing than anything else. Laptops have been aggressively driving growth in the PC market for at least the past 5 years now, with Nvidia reporting sales of over 20 million GTX series Laptops in 2015 alone. The average of which is well over a thousand bucks mind you.
Now fuck off you're actively lowering the IQ of this board
▶ No.859821
>>859757
Wew lad that's some top notch shitposting
▶ No.863670
>>849189
>implying I'm not allowed to waste bandwidth in the name of quality
▶ No.863684>>873875
>>847487 (OP)
>AMD better take advantage of this moment
Unfortunately they can't get over not including the PSP.
▶ No.873869
>>859742
You're like last century's idiots who thought that in the year 2000 we would have jetpacks and hovercars. Computers aren't about to be replaced anytime soon, idiot. They're too useful for that. It's true that a lot of computer functionality is being coopted into smaller hand-held devices but that doesn't mean that the PC itself is on its way out. There's too much shit you can't reasonably do without a PC.
▶ No.873875>>874236
>>863684
They updated their chipset drivers to include the option to disable PSP. It's just that NONE, and I mean FUCKING NONE of the motherboard manufacturers will fucking god damn touch it.
▶ No.873965
>>847508
>>847510
bourgeoisie is a noun, you retarded faggots. bourgeois is an adjective. and, I'll give anyone $10grand to show me a Jew that's not bourgeois. PS. champagne socialists and religious extremists don't count (and/or are actually still bourgeois despite their pretensions)
▶ No.874236
>>873875
Interesting is there any way to do this manually as a user?
▶ No.874264
>>847769
>the far right
>proceeds to describe centre right alt-kikes who routinely suck jew cock
The far right is national socialism, not national capitalism.
▶ No.874267
>>847773
The only difference between /leftypol/ and liberals is the former hates liberals.