[ / / / / / / / / / / / / / ] [ dir / agatha / arepa / fur / general / qanon / sw / vg / vichan ][Options][ watchlist ]

/tech/ - Technology

You can now write text to your AI-generated image at https://aiproto.com It is currently free to use for Proto members.
Email
Comment *
File
Select/drop/paste files here
Password (Randomized for file and post deletion; you may also set your own.)
* = required field[▶ Show post options & limits]
Confused? See the FAQ.
Expand all images

New Volunteer

File (hide): 9628470dafd65f4⋯.png (9.46 KB, 920x500, 46:25, intel-look-inside-logo.png) (h) (u)

[–]

 No.930754>>930756 >>930760 >>933961 >>934623 [Watch Thread][Show All Posts]

https://www.bleepingcomputer.com/news/security/new-lazy-fp-state-restore-vulnerability-affects-all-intel-core-cpus/

New Lazy FP State Restore Vulnerability Affects All Intel Core CPUs

By Brian Fagioli

>What a horrible year in security for Intel. First we had the Meltdown and Spectre vulnerabilities that never seem to go away. Now Intel has announced a new speculative execution side channel vulnerability involving "Lazy FP state restore" that could allow a malicious program to read data being used by other processes.

>According to Intel this new vulnerability affects all Intel Intel Core-based microprocessors and is a bug in the actual CPU, so it does not matter what operating system the user is running. It could be Windows, Linux, BSD, or any other operating running an an Intel Core-based CPU and using "Lazy FPU context switching".

>"Lazy FPU context switching" is a performance optimization feature used by operating systems that only saves and restores the FPU (Floating Point Unit) registers, which are locations in the CPU that are used to store floating point numbers, when needed. A bug in the actual Intel CPUs allows another process to access these registers and the data within them.

>The problem is that these numbers are used for a variety of tasks, including cryptographic equations. This could allow an attacker to sniff out numbers that make it easier to crack an encryption key.

>Thankfully, researchers state that this vulnerability would be difficult to execute via a web browser, so its impact is less than previous speculative execution vulnerabilities such as Meltdown.

>Intel has told BleepingComputer that this vulnerability has been addressed by operating system and hypervisor software for many years.

<"This issue, known as Lazy FP state restore, is similar to Variant 3a. It has already been addressed for many years by operating system and hypervisor software used in many client and data center products. Our industry partners are working on software updates to address this issue for the remaining impacted environments and we expect these updates to be available in the coming weeks. We continue to believe in coordinated disclosure and we are thankful to Julian Stecklina from Amazon Germany, Thomas Prescher from Cyberus Technology GmbH, Zdenek Sojka from SYSGO AG, and Colin Percival for reporting this issue to us. We strongly encourage others in the industry to adhere to coordinated disclosure as well."

Vendors rush to release advisories

>Rumors about this bug have been circulating since OpenBSD and DragonFlyBSD posted notices about patches that fixed rumored Intel vulnerabilities. These notices indicated that there was a supposed hardware issue related to the FPU registers in Intel CPUs and decided to proactively patch their operating systems.

>The good news is that this vulnerability does not require new CPU microcodes from Intel, but can be fixed instead by operating system updates. Since Intel's advisory was posted, various Linux distributions and Microsoft have posted advisories related to this new vulnerability.

https://slashdot.org/submission/8290070/intel-x86-processors-affected-by-lazy-fpu-saverestore-security-flaw

"Reportedly, AMD processors are not affected with this vulnerability"

This is the part where we throw our heads back and laugh.

 No.930756>>930851 >>930990 >>931134 >>933861

>>930754 (OP)

Is there no end to these?


 No.930760

>>930754 (OP)

>(((coordinated disclosure)))


 No.930764

Man I so regret buying an Intel cpu. I always buy AMD but I was making a gaming rig and needed an Intel because AMD was focusing on the budget segment(value).


 No.930770>>930777 >>930925 >>931369 >>940154

Using a core2duo still. I'll be moving to POWER soon enough.


 No.930777

>>930770

good choice. I will be doing the same for my next PC


 No.930778>>930780

Fuck all modern shit tbh. I'm moving to Z80 and 68000.


 No.930780

>>930778

>Fuck all modern shit tbh.

>I'm moving to Z80 and 68000.

Bro do u even try? I'm moving to a slide rule and abacus.


 No.930781>>930786

File (hide): 1cef117ddaa3ea8⋯.png (114.05 KB, 601x508, 601:508, 1488019789339.png) (h) (u)

>intel

more like retar


 No.930786

File (hide): 7cfb1a19e26c613⋯.jpg (15.07 KB, 480x270, 16:9, 1466094732357.jpg) (h) (u)


 No.930788

we already know modern CPUs are bloatware. only the most oblivious person would be surprised about a side channel vuln. there are literally tens of thousands


 No.930851>>930958

>>930756

>fill CPU with vulns

>sell said vulns to NSA/GHCQ

>pump dollars into review padding

alternatively

>fuck security, we can't let AMD get ahead

>five months later

>look at how fast our procs are!

>nobody knows for a decade

>no negative reprocussions


 No.930925

>>930770

I have a large collection of Thinkpads and I'm going to be selling them all off excepting a few '90s units to fund a Talos. Fuck this shit.


 No.930957

Not building your own microprocessors, you're all absolute plebs.

>inb4 it only runs 100MHz

There's even crumbs out there for you peasants, such as project oberon, and yet you still keep going back to intel to be abused another time.


 No.930958

>>930851

It's probably both.


 No.930990>>931003

>>930756

intel relies on the memory hole.

the average goy will never remember or care about these, the only consequence is they will love windows update even more thinking the constant updates to the botnet spying on him are actually protecting him. it will also encourage users to buy newer processors that don't have these vulnerabilities even though they do, and these processors will be filled with even more botnet than before.


 No.931003

>>930990

>I-I-it feels snappier!


 No.931035>>931086 >>931464

MUH SECURITY LARP

Threadly reminder none of these speculative execution bugs has any relevance to anything other than running a sandboxed VM, which 99.999% of CPU time isn't.


 No.931054>>933851


 No.931086>>931111

>>931035

> Intel shill tries to hide with Apple logo

heh heh heh


 No.931111

>>931086

>implying post-PPC unironic Applefags aren't Intel's greatest customers


 No.931133>>931157

>muh intel muh muh intel m-muh intel shill s-shill shill shill

this isn't an intel problem you niggerfaggots, x86 is bloated as fuck no matter how you implement it. fuck off back to /pol/. stop shitting up the board.


 No.931134>>931157

>>930756

yes there is no end. this is what happens when your CPU architecture is bloated and you try to run sidechannel-sensitive applications on it


 No.931157>>931386

>>931133

>>931134

>It's not Intel's fault, it's that x86 is bloated!

>Even though they had market dominance for x86 for a decade and were adding said bloat themselves


 No.931369>>931420 >>931582 >>940302

File (hide): 7725beb3ff9653a⋯.jpg (4.65 MB, 4160x3120, 4:3, 20180615_112119.jpg) (h) (u)

>>930770

Am I doing it right?


 No.931386

>>931157

Your posting in a LARPthread nigger just hide it and ignore it


 No.931420>>940232

File (hide): 8078949cd0e811b⋯.jpg (214.14 KB, 1592x2048, 199:256, 8078949cd0e811b2d1ee23ac8d….jpg) (h) (u)

>>931369

Pretty good. Ironic how some Apple products have became the least gay tech in existence now.


 No.931464

>>931035

>web browser

>anything else than a sandboxed JavaScript VM


 No.931582

File (hide): 6992eddf6b3b5a6⋯.jpg (96.5 KB, 1024x1024, 1:1, 1024px-Osborne_1_open.jpg) (h) (u)

>>931369

That's a start, but this is how real men do it.


 No.932659>>933963

File (hide): 0a43dcb1393c89f⋯.png (1.15 MB, 1265x1080, 253:216, 0ni_smug.png) (h) (u)

Mildy related news: https://archive.fo/Orwpl

The ride never ends.


 No.933851>>933905

>>931054

Is there any easy way to do this with Linux?


 No.933861

>>930756

You misspelled 'tiddie'.


 No.933905>>934609

>>933851

BIOS dipshit


 No.933933>>933942

>affects all Intel Intel Core-based microprocessors

How do i upgrade my thinkpad to amd?

Fuck you intel.


 No.933942

>>933933

You can't. The sockets aren't the same.

Just get Ryzen based laptop.


 No.933961

>>930754 (OP)

Is there no sensible option for high performance in single threaded applications on the market?

AMD's pozzed with the backdoor shit but at least they're not ridden with vulnerabilities as badly as Intel. The problem is their single threaded performance is around 20% worse in comparable price-point models.


 No.933963>>937433

>>932659

Disabling multithreading altogether? That's fucking insane.


 No.933970>>937445

File (hide): a403fb8b6537a29⋯.jpg (540.79 KB, 1500x1200, 5:4, bsdtans.jpg) (h) (u)

Here's an unofficial video of Theo's latest talk: https://youtube.com/watch?v=UaQpvXSa4X8

It freezes in some spots for a few seconds, but otherwise it's not too bad.


 No.934609

>>933905

>BIOS is Linux


 No.934623

>>930754 (OP)

>cryptographic equations

>equations

Why is Brian Fagioli pretending to understand cryptography?


 No.937432

So how in the hell is this mitigated on Linux? Are there patches yet?


 No.937433

>>933963

No, they're disabling virtual threads.


 No.937445>>937518

>>933970

>That sperg rage at 19:40


 No.937518

>>937445

I get that an NDA keeps you from revealing certain information but does it also require you to sperg out like an autist when people figure out what's under embargo too?

https://marc.info/?l=openbsd-misc&m=152883510311011&w=2


 No.937776>>937797

So at which point do we all begin suspecting that these security flaws are deliberate?


 No.937797

>>937776

[post redacted] tbh


 No.940001

FAGIOLI


 No.940154

>>930770

Power isn't better. It's all shit! All of it.

https://github.com/paboldin/meltdown.git

You run away from one shithole to find yourself in another one.


 No.940232

>>931420

The gayness came later, after they went x86. or at least that's what I tell myself.


 No.940302

>>931369

Your life is full of constant mistakes.


 No.940350

Little by little, the performance gains are reversed. I wonder if it will reach a point where it's comparable to alternative architectures. Would be hilarious if that happened.

Whatever happened to optimization that doesn't change program behavior?




[Return][Go to top][Catalog][Screencap][Nerve Center][Cancer][Update] ( Scroll to new posts) ( Auto) 5
50 replies | 10 images | Page ???
[Post a Reply]
[ / / / / / / / / / / / / / ] [ dir / agatha / arepa / fur / general / qanon / sw / vg / vichan ][ watchlist ]