Why aren't we talking about this?
theinquirer.net
theregister.co.uk
pcgamer.com
hothardware.com
and a lot more...
Why aren't we talking about this?
theinquirer.net
theregister.co.uk
pcgamer.com
hothardware.com
and a lot more...
Other urls found in this thread:
techpowerup.com
techpowerup.com
youtube.com
youtube.com
techpowerup.com
twitter.com
Dude it's fucking over, Intel is dying and they know it. They're working on GPUs now and abandon CPU market.
they sacked a brian
well, that's was kinda too easy.
lul what the fuck
fuck intel, how are they so incompetent?
What is there to talk about?
Intel making themselves worthless to enterprise because of their pricing scheme and being as secure as a Bluetooth enabled "smart" lock.
>Why aren't we talking about this?
BECAUSE THIS IS ANTI-SEMITIC
DELETE THIS THREAD RIGHT NOW
complacency due to market dominance. it's a common cycle--so common that you'd think that big businesses would watch out for it. complacency kills.
But these flaws existed since fucking core2duo
But user innovation costs money and we need to cut costs to appease the shareholders so why invest billions into new architectures or whatever your company happens to produce when you dominate the market with ease right now?
Oh user why are we suddenly not competitive anymore? Why did we fall behind and get fucked in literally one generation of processors by our basically only competitor worth mentioning? How could this happen to us?
Big business is always retarded and short sighted and will fuck itself over in the long run to appease the shareholders for 5 minutes.
--and they had decades to find and correct these mistakes. they "should" have been constantly testing their products for these types of issues, never assuming any part of their products were perfect.
Since the flaws existed since Core2Duo, they were just lazy and wanted to get even more performance by taking security risks. Then they became complacent.
why are you 2 days late? lmao
based mommy
July cannot come soon enough.
>Invite the devil with "Devils Canyon"
>the devil kills paul, makes brian a rapist, implements spectre(v2), Meltdown(v2), thunderclap, rowhammer, foreshadow(ng), did I miss something? I bet it did
Never forget: 2 days after there's been a talk about a hidden operating system (Minix) running on all core iX CPUs/NBs, which Intel told nobody about (probably a backdoor) at the chaos communication congress, the msm is all over spectre instead.
media.ccc.de for the talks, search for "intel"
Oh and there's also hidden instructions on x86 CPUs Intel didn't tell us about: search for sandsifter on youtube.com
What? Are you clinging onto the typo or what?
there was a typo?
nah :^)
It sounds schizo, but all of this is actually factual. Check out exploiting flash memory if you really want some tinfoil.
Explain what is happening and what the problem with Intel is to a layperson.
one day one flaw in intel architectures, it's a game now there is no reason to make a thread each time
Because this affects only servers and not the end user
Sage
>it only affects the by far most important business sector, so I don't see a reason why it'd be important.
>it also affects the end user but I am retarded so that doesn't matter either
Show me one person getting hacked from this
>it only affects the segment where intel has 95% + market share.
are you even trying to shill?
besides, you're lying trough your teeth:
>"Spoiler is not a Spectre attack. The root cause for Spoiler is a weakness in the address speculation of Intel's proprietary implementation of the memory subsystem which directly leaks timing behaviour due to physical address conflicts," the researchers write.
>"The leakage can be exploited by a limited set of instructions, which is visible in all Intel generations starting from the first generation of Intel Core processors, independent of the operating system, and also works from within virtual machines and sandboxed environments."
oh boy, I think it's been more than 5 years since I last wrote the following: sage goes in all fields.
And why should I engage you when with your first post you made entirely clear that you have no idea what the fuck you are talking about, have nothing to add to the discussion and are a consumer faggot larping around on Jow Forums.
Fuck back off to whatever rock you crawled out from.
>It only affects end users and not the end user
Yeah user it doesn't affect "the" end user. You know the one.
Kek rip intel.
So it's nothing. Everyone will still use intel
>i have no argument so I will shitpost instead
>he thinks it affects random people that have an intel desktop like me
imagine being this brainwashed
>>i have no argument so I will shitpost instead
You know it'd be truly impressive how you lack any and all self awareness if I hadn't seen retards like you a few times today already.
>>i have no argument so I will shitpost instead
You greentexted on accident
it's just quite impressive isn't it. Somehow I know he's not just baiting, but that's just how he is.
the overuse of just was on purpose, just fyi.
>have nothing to add to the discussion
>meanwhile he spams "intel is finished" and wojaks
>a weakness in the address speculation of Intel's proprietary implementation of the memory subsystem
>which is visible in all Intel generations starting from the first generation of Intel Core processors
>which is visible in all Intel generations starting from the first generation of Intel Core processors
>which is visible in all Intel generations starting from the first generation of Intel Core processors
What part of that was exactly "nothing"? I beg for your answer.
before you even finish the utter bs you must be typing right now, mind the following from the register article:
>This security shortcoming can be potentially exploited by malicious JavaScript within a web browser tab, or malware running on a system, or rogue logged-in users, to extract passwords, keys, and other data from memory. An attacker therefore requires some kind of foothold in your machine in order to pull this off. The vulnerability, it appears, cannot be easily fixed or mitigated without significant redesign work at the silicon level.
i'll just repeat to make sure you see before embarassing yourself even further itt:
potentially exploited by malicious JavaScript within a web browser tab
potentially exploited by malicious JavaScript within a web browser tab
potentially exploited by malicious JavaScript within a web browser tab
got it?
does it still amounts to nothing as you said before?
>100% of all people on Jow Forums* affected
>17 posters
i'll ely47c, because i'm sure it'll be the needful
>if affects everything intel has manufactured since 2006
>it can be exploited through web based scrips
>it can't be mitigated by software/firmware/microcode updates
>it demands a completely new hardware re design
>mistakes
user, those weren't mistakes, some of the ''''flaws''''' were point blank intentional desing decisions because moar ''''performance''''/better benchmarks etc
Holy fuck man, i am jumping to AMD ASAP
Just bought i5-9600K, enjoying the performance, laughing at FUD
>FUD
it's real, zoomer
Mobile Pentium-III M master race.
Hack me
Reminder that Arm is the future
youtube.com
lmao
If you're a layperson, you're too brainlet to understand what's happening. The outcome is visiting a website with JavaScript on could get you fucked as if you were using IE 6 on Windows XP. This probably can't be fixed in software. You simply need to buy an AMD CPU.
Actual explanation:
Something called "rowhammer" can be used to corrupt memory in computers, but security measures make it so you can't really choose what gets corrupted, so doing it is pointless. This attack makes it possible to discover where interesting things are in memory (like bits that set security on what your program is allowed to read and write to), so you can try to corrupt things in your favor without just crashing the browser tab instantly. Fixing this in software would result in an absolute tremendous amount of performance loss.
>Why aren't we talking about this?
Because it keeps happening and it's becoming apparent that buying anything other than AMD CPUs at this point is absolutely retarded.
Unless you want to give the world root access to your system.
>it's been over ten years since this exact same vuln was discovered in firewire
kek
I don't have any intel product
Public corporations and shareholders were mistakes
>snapdragon 835 can't keep up with celery
>snapdragon 855 not even twice as powerful as the 835
>8cx probably just OC'd by 100MHz
>"arm is le future guis!"
ok, retard
And AMD is safe?
>safer
ftfy
The researchers couldn't exploit a bulldozer, and Intel had months to test literally every CPU AMD has ever made so they could say AMD is vulnerable too in their press release.
AMD is safe. Their memory management model is, simply put, fundamentally more secure
So is this only vulnerable to browser based attacks in theory or has someone done it yet?
Not necessarily just browser based attacks, any form of scripting or program a hacker could get you to run on your system could get them access. You are merely more likely to run malicious javascript than anything else, as most people don't hit the big green download button on tpb.
>PC can be infected by Thunderbolt devices and peripheral
>USB4 will be based on TB3
>Your PC will be infected by USB devices and peripheral
Was this Brian's master plan all along?
> test literally every CPU AMD has ever made so they could say AMD is vulnerable too in their press release
motherfucking this.
if they couldn't throw anything to even cloud the waters even if for a bit, rest assured amd is safe. The best brains intel has to offer are probably still trying as hard as they can.
It's one thing to have a security that affects all cpu's, even if if marginally as we can clearly remember with specter/meltdown, it's another game entirely to have a flaw that affects only your cpu's.
inb4 (((CTS labs))) reveals more AMD (((vulnerabilities)))
fuck off shill.
80% of the articles are very explicitly saying this only affects intel core uarch, the remainder leave it between the lines for anyone above 70 iq to understand clearly. Even they won't dare to shill that hard and they're on a motherfucking payrole.
so far its only modern intel core chips. bulldozer was tested, ryzen was not.
if you want one authoritative argument
>A new security vulnerability has been found that only affects Intel CPUs - AMD users need not concern regarding this issue.
techpowerup.com
nifty charts from TPU
yeah but we're posting on Intel based load balancers, servers, switches etc.
I went with "safer" because I haven't heard that Spectre suddenly didn't work on AMD.
I doubt it affect Ryzen because the reports explicitly state that SPOILER is a consequence of Intel's shitty proprietary memory controller
some spectre variants work on amd, but this is not spectre
sauce, because I feel like you're trying to muddy the waters. regardless, haven't seen mention of tested amd cpu's yet, but since it's the case that this exploit is specialy designed aroun intel's memory subsystem I doubt it'll be possible to deploy on amd, which is quite different seeing how it would require working the same exploit around the ccx's, infinity fabric and other exclusive amd implementations.
second chart
I mean, specific amd cpu's.
Everything I've read so far only mentioned it in general terms.
not on ryzen.
especially not on ryzen+
and by modern, dontcha mean every intel cpu since 2006, but itanium.
>2006 was 13 years ago.
damn.
IIRC, the only company that ever found an AMD-exclusive vulnerability was based in Israel (just like Intel) and not a single independent study was able to reproduce the claims made. Am I remembering wrong?
they were related to PSP and were fixed a while after CTS kikes (((disclosed))) it
here
and that one amd security flaw was a literal short selling scam that failed so hard it was funny. I think mama Lisa wasn't even mad at them, really, seeing how they fucked up so royally she must have felt just pitty for them.
Ryzen isn't safe from spectre but some variants are harder to exploit, potentially impossible in some cases.
that 22 needs an update, also.
more like 22++++++++++++++
just like their fab nodes.
(isn't it beatiful, though?)
This is what AMD cope looks like
we went through so many times before.
I don't feel like bringing it up again.
Anyway.
You got bigger flaws to fry right now brian. I mean bob... or pierre?
nah, sorry for the pierre that was uncalled for, your writing manner seemed congruent enough.
>2006 was 37 intel cpu security risks ago.
Intlel the botnet thickens.. I dont understand how their stock price is still not taking a nose dive..
a jewish short selling scam.
Straight out of a 5x5 rental office space in Tel Aviv, unironically.
Is there a website which lists all the spectre, meltdown and other attacks on Intel, AMD and ARM? All the ones I know of have outdated info.
who knows.
ask Wendell.
or just google since you already came up with a series of keywords that'll probably hit in the very first links.
tell me of your findings, I also got a bit curious about it myself.
That's what I was saying ~4 months ago, but here's the problem:
Israel will keep funding Intel. Intel will never die, even if it really seems that they're doing terribly. They must be making a lot of money from "vulnerabilities" to still be supported this way.
Because the real world is different than the AMD-funded dystopia that Jow Forums lives in.
This flaw requires an already-compromised system to work. People aren't worried because no real world applications have resulted from these flaws.
user Israel can fund Intel all the money in the universe, that won't make 10nm magically work
OH NONONONONONOOOOOOOO
what exactly is amd coping for?
But it will keep them alive until they make it happen. Their 10nm will be more popular, and also backdoored, because of this huge financial backing.
your selective reading is showing.
also, your talking about spectre, I'm pretty sure desu.
This is a new thing, if you haven't noticed. Disclosed on yesterday, march 6th 2019.
Intel was notified december 2018.
That user is not me, but yes, very clearly selectively reading the negative parts without fully understanding how the exploit works.
Again, your system has to be compromised before this exploit will work.
some days it hurts to go to work.
t. intel 17 years.
Is it all the Israeli money causing all these security flaws or are their engineers that bad?
because it's not interesting news anymore all modern processors use speculative execution and probably have 100s of undiscovered exploits like this