text
stringlengths
7
369
[2184.96 --> 2185.56] you plug in a
[2185.56 --> 2186.30] hardware device
[2186.30 --> 2187.38] that does something
[2187.38 --> 2188.32] feels like you'd
[2188.32 --> 2188.68] really want to
[2188.68 --> 2189.86] combine a two
[2189.86 --> 2190.96] factor code on
[2190.96 --> 2192.28] authentication app
[2192.28 --> 2193.16] with a hardware
[2193.16 --> 2194.40] device with a
[2194.40 --> 2195.30] password potentially
[2195.30 --> 2197.08] or as a backup
[2197.08 --> 2197.56] you know when
[2197.56 --> 2198.66] places do SMS
[2198.66 --> 2199.40] phishing attacks
[2199.40 --> 2200.04] and stuff that's
[2200.04 --> 2200.50] one of the most
[2200.50 --> 2201.20] common attack
[2201.20 --> 2202.92] vectors is people
[2202.92 --> 2203.98] steal your SMS
[2203.98 --> 2206.08] access send a
[2206.08 --> 2206.92] two factor code
[2206.92 --> 2208.02] there whilst they
[2208.02 --> 2208.80] have the temporary
[2208.80 --> 2210.08] access before you
[2210.08 --> 2211.66] notice and this
[2211.66 --> 2212.34] would completely
[2212.34 --> 2213.40] negate that as an
[2213.40 --> 2214.00] attack vector
[2214.00 --> 2215.02] but only if
[2215.02 --> 2215.42] supported
[2215.42 --> 2216.90] only if supported
[2216.90 --> 2217.92] this takes me
[2217.92 --> 2219.44] back to a few
[2219.44 --> 2220.26] years ago where
[2220.26 --> 2221.24] the company I
[2221.24 --> 2221.88] worked at used
[2221.88 --> 2223.10] YubiKeys and
[2223.10 --> 2224.56] in Slack multiple
[2224.56 --> 2225.30] times a day
[2225.30 --> 2225.96] different people
[2225.96 --> 2226.94] accidentally touch
[2226.94 --> 2227.78] their YubiKeys
[2227.78 --> 2228.66] and put in
[2228.66 --> 2230.54] their 40
[2230.54 --> 2231.40] character long
[2231.40 --> 2232.76] string
[2232.76 --> 2235.10] most of the
[2235.10 --> 2235.44] days
[2235.44 --> 2237.14] yeah I have
[2237.14 --> 2237.82] seen that I
[2237.82 --> 2238.24] see that in our
[2238.24 --> 2239.04] chat room sometimes
[2239.04 --> 2239.30] too
[2239.30 --> 2240.34] I did it one
[2240.34 --> 2240.64] time
[2240.64 --> 2241.92] and Alex
[2241.92 --> 2242.86] you've sent
[2242.86 --> 2243.34] some of your
[2243.34 --> 2244.56] passwords to
[2244.56 --> 2245.24] GitHub if I
[2245.24 --> 2245.84] remember correctly
[2245.84 --> 2246.50] oh well that's
[2246.50 --> 2247.08] that's different
[2247.08 --> 2247.66] that's just me
[2247.66 --> 2248.46] being being an
[2248.46 --> 2249.74] idiot but that's
[2249.74 --> 2250.12] different
[2250.12 --> 2250.82] what's the
[2250.82 --> 2251.20] difference
[2251.20 --> 2252.16] well these
[2252.16 --> 2253.04] strings aren't
[2253.04 --> 2253.76] useful on their
[2253.76 --> 2254.24] own because
[2254.24 --> 2254.74] they're attached
[2254.74 --> 2255.32] to a specific
[2255.32 --> 2256.28] service and
[2256.28 --> 2256.80] they're time
[2256.80 --> 2257.46] limited and all
[2257.46 --> 2257.90] that kind of
[2257.90 --> 2259.08] stuff so if
[2259.08 --> 2259.72] you happen to
[2259.72 --> 2260.58] know exactly
[2260.58 --> 2261.28] what service I'm
[2261.28 --> 2262.04] logging into at
[2262.04 --> 2262.54] that specific
[2262.54 --> 2263.40] moment in history
[2263.40 --> 2265.14] maybe it's useful
[2265.14 --> 2265.84] for about the
[2265.84 --> 2267.10] next 25 seconds
[2267.10 --> 2268.36] but otherwise it's
[2268.36 --> 2269.70] useless well I
[2269.70 --> 2270.24] want to talk about
[2270.24 --> 2270.92] something you came
[2270.92 --> 2272.50] across that really
[2272.50 --> 2273.38] piques my interest
[2273.38 --> 2274.50] because I'm often
[2274.50 --> 2275.60] using reddit as a
[2275.60 --> 2276.24] way to discover
[2276.24 --> 2277.18] topics that seem