text
stringlengths
14
502
[1675.88 --> 1676.38] it was.
[1676.58 --> 1677.78] $24 million is quite
[1677.78 --> 1678.22] a bit of money.
[1678.48 --> 1678.94] I also read,
[1679.12 --> 1679.80] this is why this is
[1679.80 --> 1680.24] so confusing.
[1680.50 --> 1681.10] I read a number
[1681.10 --> 1681.92] that was over 40.
[1682.72 --> 1683.06] Okay.
[1683.42 --> 1683.90] But, like,
[1683.92 --> 1684.74] I'm not even saying
[1684.74 --> 1685.44] it's right
[1685.44 --> 1686.72] because I just read that,
[1686.82 --> 1686.92] like...
[1686.92 --> 1687.56] Well, actually,
[1687.82 --> 1688.90] if this program,
[1689.18 --> 1689.98] it could be
[1689.98 --> 1690.74] multiple phases.
[1691.04 --> 1691.16] That's fair.
[1691.16 --> 1691.88] So that's the number
[1691.88 --> 1692.40] that went out
[1692.40 --> 1693.38] recently in December.
[1693.52 --> 1694.12] So it could be
[1694.12 --> 1694.78] over 40,
[1694.90 --> 1695.12] like,
[1695.20 --> 1695.64] since summer,
[1695.72 --> 1696.28] since he's known,
[1696.36 --> 1696.54] maybe.
[1696.66 --> 1696.90] Sure.
[1697.06 --> 1697.24] Yeah.
[1697.24 --> 1697.84] I don't know.
[1700.00 --> 1700.36] Yeah.
[1700.72 --> 1701.56] It's a mess,
[1701.92 --> 1703.90] but potentially
[1703.90 --> 1704.94] looking into
[1704.94 --> 1706.64] his legal
[1706.64 --> 1707.22] ramifications
[1707.22 --> 1708.10] for what that
[1708.10 --> 1708.74] might potentially
[1708.74 --> 1709.30] end up being
[1709.30 --> 1709.68] in terms of
[1709.68 --> 1710.22] insider trading
[1710.22 --> 1710.52] or not,
[1710.76 --> 1711.30] and I'm sure
[1711.30 --> 1712.68] if it was planned,
[1712.82 --> 1713.44] he has tons
[1713.44 --> 1714.00] of documentation
[1714.00 --> 1714.64] for it,
[1714.70 --> 1715.38] and if it goes
[1715.38 --> 1716.34] back before this
[1716.34 --> 1717.02] bug was released
[1717.02 --> 1717.30] to them,
[1717.46 --> 1718.02] he's going to be
[1718.02 --> 1718.30] fine.
[1718.30 --> 1720.36] If it doesn't,
[1720.42 --> 1721.54] that's going to
[1721.54 --> 1722.96] be a little sketch.
[1722.98 --> 1723.56] But if it was planned
[1723.56 --> 1724.38] and it is fine,
[1724.80 --> 1725.18] you're probably
[1725.18 --> 1725.70] not going to hear
[1725.70 --> 1726.04] about it
[1726.04 --> 1726.48] because no one's
[1726.48 --> 1726.80] going to click
[1726.80 --> 1727.44] on that article.
[1727.56 --> 1727.76] Yeah.
[1727.92 --> 1728.22] It's just,
[1728.30 --> 1728.66] it's going to be
[1728.66 --> 1728.98] boring.
[1729.18 --> 1729.80] It's not a story.
[1729.86 --> 1730.52] It'll be too boring
[1730.52 --> 1730.98] to bring up
[1730.98 --> 1731.56] on WAN Show.
[1731.82 --> 1732.22] You know what's
[1732.22 --> 1732.74] not boring?
[1733.54 --> 1734.68] Intel getting sued
[1734.68 --> 1735.68] over this vulnerability.
[1735.94 --> 1736.46] Super hard.
[1736.72 --> 1736.96] Yeah.
[1737.42 --> 1738.04] There are multiple
[1738.04 --> 1738.66] lawsuits.
[1739.28 --> 1739.90] Hold on one quick
[1739.90 --> 1740.78] second before we
[1740.78 --> 1741.18] go forward.
[1741.18 --> 1742.36] This article was
[1742.36 --> 1743.68] posted by SC2
[1743.68 --> 1744.48] Mitch on the
[1744.48 --> 1744.78] forum.
[1745.20 --> 1745.92] The previous one
[1745.92 --> 1747.24] was found by
[1747.24 --> 1747.54] James.
[1748.46 --> 1749.78] And the big
[1749.78 --> 1751.00] whole entire
[1751.00 --> 1751.46] thread,
[1751.64 --> 1752.30] the source that
[1752.30 --> 1752.82] we have for that
[1752.82 --> 1753.56] is Doctor Who
[1753.56 --> 1755.10] 1975 on the
[1755.10 --> 1755.32] forum.
[1755.46 --> 1755.96] He's getting the