text stringlengths 14 502 |
|---|
[533.68 --> 536.08] I think it's usually, especially if you have a newer CPU, |
[536.22 --> 537.20] it's about 5%. |
[537.20 --> 537.84] Yeah, yeah. |
[537.94 --> 539.74] It's very rarely that bad. |
[539.96 --> 542.60] It's also only certain processes and programs |
[542.60 --> 544.02] that are going to get affected by it. |
[544.26 --> 547.58] And it's also less as impactful if you have newer chips. |
[547.88 --> 549.28] And it's going to depend on what you're doing, too. |
[549.30 --> 553.90] I've heard in gaming, it can result in like three frames per second. |
[554.08 --> 554.42] Yeah. |
[554.64 --> 556.76] But it really is going to depend. |
[556.76 --> 565.48] But the answer to this is to put an end to that sharing of memory |
[565.48 --> 567.14] between user programs and the kernel, |
[567.46 --> 569.40] which is why there's that performance penalty. |
[569.86 --> 575.32] And then Spectre, it's applicable to chips from Intel, AMD, and ARM. |
[575.88 --> 577.62] This is where some of the confusion came in |
[577.62 --> 578.72] that we're going to talk about soon, |
[578.88 --> 582.04] where AMD didn't think they were susceptible to anything, |
[582.04 --> 586.00] and then now it's just Intel's susceptible to more stuff, |
[586.16 --> 588.02] and everyone's susceptible to some things. |
[588.04 --> 591.78] And each company is trying to minimize the optics. |
[592.70 --> 595.78] AMD said this is a near zero chance of affecting us, |
[596.32 --> 598.44] and Intel doesn't want their stock to drop, |
[598.52 --> 600.26] so they're saying, yes, it does affect you. |
[600.44 --> 600.72] Yeah. |
[601.48 --> 603.10] There's a lot of politics involved as well. |
[603.10 --> 604.94] There's a huge amount of politics in this. |
[605.04 --> 607.26] We'll get into that a little bit more in the future. |
[608.80 --> 611.26] Yeah, it even says Intel, AMD, ARM, |
[611.36 --> 613.54] and probably every other processor on the market |
[613.54 --> 615.36] that offers speculative execution, |
[615.52 --> 616.76] which is like all of them. |
[618.22 --> 619.74] It's also more subtle. |
[619.90 --> 622.48] It encompasses a trick testing array bounds |
[622.48 --> 624.60] to read memory within single processes, |
[624.60 --> 627.90] which can be used to attack the integrity |
[627.90 --> 629.88] of virtual machines and sandboxes, |
[629.98 --> 631.56] which is rough. |
[631.56 --> 633.14] That's a big deal for the cloud. |
[633.46 --> 633.70] Yeah. |
[634.58 --> 639.16] And cross-process attacks using processors branch predictors, |
[639.20 --> 640.80] which is the thing that I was mentioning earlier, |
[641.10 --> 644.48] where it can take little bits of resulting information |
[644.48 --> 645.68] to figure out what it was actually doing. |
[646.48 --> 648.30] Fixes for some aspects of Spectre |
[648.30 --> 650.14] appear to have been developed already, |
[650.58 --> 652.94] but protecting against the whole range of fixes |
[652.94 --> 654.26] will require modification |
[654.26 --> 657.42] or at least recompilation of at-risk programs, |
[657.42 --> 660.82] and that is also a very rough part |
[660.82 --> 663.66] because that brings way more players into the space |
[663.66 --> 665.56] because now you're talking about programs too. |
[665.94 --> 667.24] Do you think it's fair to say |
[667.24 --> 669.62] that the only true fix is new chip architecture? |
[673.34 --> 673.82] No. |
[677.54 --> 679.04] One, it depends on what we're talking about. |
[679.24 --> 680.78] Unfortunately, the sketchy one |
[680.78 --> 683.48] that requires the most amount of tinkery level fixing |
[683.48 --> 685.74] for the most amount of people is Spectre, |
[685.88 --> 686.80] which affects everybody. |
[687.46 --> 689.92] Everybody that has speculative processing. |
[691.14 --> 693.24] So that's really annoying. |
[693.66 --> 696.54] But you can, on a single system, |
[697.04 --> 698.24] know that you're okay |
[698.24 --> 701.70] if you go through everything. |
[702.12 --> 705.22] Make sure everything has been modified or recompiled |
[705.22 --> 706.84] that is affected by this. |
[707.08 --> 708.86] Make sure your OS level is happy, |
[709.12 --> 709.96] all that kind of stuff. |
[709.96 --> 711.60] Turn on Windows updates, guys. |
[712.48 --> 713.38] At least. |
[714.58 --> 715.10] Yeah. |
[716.46 --> 719.42] It's kind of a nightmare. |
[719.66 --> 722.26] So how did this first get discovered? |
[722.54 --> 723.36] You want to jump us there? |
[724.14 --> 726.08] I thought I was going to be an interviewer. |
[726.20 --> 728.56] But I can clarify some things because you know. |
[728.86 --> 729.20] Okay. |
[729.66 --> 731.04] So the way this was discovered |
[731.04 --> 732.76] was through Google Project Zero. |
[733.42 --> 734.94] Project Zero is one of those |
[734.94 --> 737.02] little Google subsidiaries |
[737.02 --> 739.40] companies that has a specific task. |
[739.64 --> 740.82] Their task is to find |
[740.82 --> 742.78] what are called zero-day bugs |
[742.78 --> 743.60] or vulnerabilities. |
[743.86 --> 744.46] That's where the zero |
[744.46 --> 745.56] from Project Zero comes from. |
[745.76 --> 746.26] That's right. |
[746.38 --> 748.04] So basically, you're finding a bug |
[748.04 --> 749.16] as soon as you can, |
[749.26 --> 749.84] as fast as you can, |
[749.96 --> 751.56] and fixing it as soon as it's found. |
[752.00 --> 753.38] So the way this works is |
[753.38 --> 755.00] there are bug bounties, |
[755.08 --> 757.26] a certain amount of money put up |
[757.26 --> 758.24] if bugs are found. |
[758.46 --> 759.58] So all these freelancers, |
[759.72 --> 760.56] Joe Schmoes, hackers, |
[761.32 --> 762.86] white hats around the world, |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.