text
stringlengths
14
502
[284.50 --> 287.92] They source from the same type of area.
[288.10 --> 289.60] So jumping to the Ars article.
[291.24 --> 294.00] Modern processors perform speculative execution.
[294.22 --> 295.58] That's where a lot of this is based on.
[295.84 --> 301.06] That is where a processor will assume what needs to be done next and do that thing,
[301.48 --> 302.52] do those calculations.
[303.04 --> 306.56] And then if it is wrong and that isn't what's happening next, that is fine.
[306.60 --> 307.10] It doesn't matter.
[307.22 --> 308.76] It ditches all that code.
[309.06 --> 309.56] No big deal.
[309.90 --> 311.88] If it's right, then, hey, it's already done it,
[311.92 --> 313.56] and it's able to execute that thing faster.
[313.56 --> 315.72] This is a great thing.
[316.04 --> 317.44] It makes things run a lot faster.
[317.92 --> 321.66] It's not a big deal that it's running some code and coming up with some answers
[321.66 --> 325.14] and then ditching those answers because it's making a lot of other things faster
[325.14 --> 326.32] when it does guess correctly.
[326.38 --> 327.44] It's pretty much only upside.
[328.86 --> 329.26] Yeah.
[329.66 --> 332.92] This is a property of modern CPUs.
[332.92 --> 336.34] So that would be a reason why, spoiler alert,
[336.78 --> 342.76] these vulnerabilities don't really have as much of an impact on much older chips.
[343.14 --> 343.48] Yeah.
[343.48 --> 347.72] So Spectre and Meltdown that we're going to be talking about today,
[347.84 --> 353.84] it perturbs the processor state in detectable ways, which is bad.
[354.24 --> 356.26] That essentially, when you break that down,
[356.32 --> 359.50] means that these vulnerabilities can watch,
[360.22 --> 363.44] even though it doesn't have access to these code paths,
[363.58 --> 365.08] these speculative execution code paths,
[365.26 --> 369.72] it can figure out what they're doing, which is bad because it gives them more information.
[369.72 --> 372.82] And it could result in more things down the line.
[373.02 --> 374.62] Meltdown and Spectre is what we know of right now.
[375.00 --> 377.32] So again, to break down what Meltdown and Spectre are,
[377.74 --> 382.74] Meltdown, it's applicable to every Intel chip made for many years.
[382.88 --> 384.52] I don't think we know necessarily right now.
[384.62 --> 385.56] There is a list.
[385.92 --> 386.88] We should show the list.
[387.02 --> 389.34] I don't entirely know if the list is...
[389.34 --> 390.06] You don't believe my list?
[390.20 --> 390.40] Oh.
[391.80 --> 392.92] We didn't do screen sharing.
[392.94 --> 394.14] We have an HDMI right here.
[394.24 --> 398.10] The classic meme of Wancho, which is it's late.
[398.10 --> 399.38] Screen sharing is never set up.
[399.38 --> 399.88] Not prepared.
[400.08 --> 401.02] And audio doesn't work.
[402.38 --> 403.38] Yes, except...
[405.00 --> 406.36] What screen is that?
[408.34 --> 408.82] What?
[409.40 --> 410.90] That's not up on either.
[413.48 --> 414.58] That's awesome.
[415.66 --> 416.42] Hold on.
[417.68 --> 419.04] Anyways, there is a list.
[419.22 --> 422.04] I can post it in the Twitch chat,
[422.18 --> 423.78] so you guys can check it out yourselves.
[423.94 --> 427.16] Suffice to say, it's basically every Intel chip for the last 15 years.
[427.36 --> 428.94] Yeah, kind of a big deal.
[428.94 --> 431.84] And it's going to affect different chips in different ways,
[431.92 --> 433.88] which is another interesting part.
[434.30 --> 435.88] Newer chips have certain standards,
[435.88 --> 441.14] which will actually help them deal with this a little bit better than certain older chips.
[441.22 --> 443.98] It also affects different programs differently.
[443.98 --> 447.12] So certain programs are going to get hit by this really heavily.
[448.02 --> 449.32] Microsoft has found...
[449.32 --> 450.78] We'll go into that more later.
[450.88 --> 456.24] But Microsoft has found that certain antiviruses have been using things in undocumented ways
[456.24 --> 459.36] that utilize this type of stuff.
[459.56 --> 460.98] So when they try to turn it off...
[460.98 --> 462.64] Again, we're going to get into that more later.
[462.64 --> 464.66] I'm trying to be vague because we'll go more deeply into that later.
[465.00 --> 468.66] It causes problems for the antivirus programs, which is a nightmare.
[469.40 --> 471.48] But anyways, it's all a whole mess.
[471.74 --> 471.98] But Meltdown...
[471.98 --> 474.28] That was basically a verbal table of contents.
[474.92 --> 475.72] Thank you.
[475.72 --> 477.72] Meltdown...
[477.72 --> 478.62] Chapter one.
[478.72 --> 480.98] ...applicable to every Intel chip for many years,
[481.10 --> 482.46] listed in the Twitch chat,
[482.82 --> 487.26] and will be in the doc if you access the forum.
[487.56 --> 488.82] So if you're watching this on YouTube,
[489.24 --> 490.90] or you're listening to this on SoundCloud,
[491.40 --> 493.66] which a few people do,
[494.00 --> 495.50] it does actually happen.
[495.84 --> 497.54] Some people do listen to this on SoundCloud.
[497.90 --> 499.14] You can go into the description,
[499.64 --> 501.18] and there will be a forum link.
[501.18 --> 503.04] If you go to that, that'll show the doc.
[503.12 --> 506.06] And in the doc, there will be a link with all capital letters
[506.06 --> 508.02] that says List of Effected Intel CPUs.
[508.50 --> 509.56] Anyways, moving on.
[509.74 --> 511.08] Every Intel chip for many years,
[511.26 --> 513.72] along with certain high-performance ARM designs,
[513.84 --> 515.20] only high-performance ARM designs,
[515.68 --> 519.18] this flaw depends on the way that operating systems share memory
[519.18 --> 521.04] between user programs and the kernel.
[521.34 --> 525.56] And the solution right now carries some performance penalty.
[525.82 --> 528.12] In certain cases, really brutal ones.
[528.12 --> 531.26] I believe the highest reported that I've seen is about 30%.
[531.26 --> 533.34] Yeah, but I think that's more anonymous.