WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:12.749 align:start position:0% [Music] 00:00:12.749 --> 00:00:12.759 align:start position:0% [Music] 00:00:12.759 --> 00:00:15.990 align:start position:0% [Music] okay<00:00:13.519> uh<00:00:13.639> so<00:00:13.880> Makai<00:00:14.519> everybody<00:00:15.360> uh<00:00:15.519> today 00:00:15.990 --> 00:00:16.000 align:start position:0% okay uh so Makai everybody uh today 00:00:16.000 --> 00:00:17.750 align:start position:0% okay uh so Makai everybody uh today we'll<00:00:16.160> be<00:00:16.320> talking<00:00:16.600> about<00:00:16.880> pasis<00:00:17.439> we'll<00:00:17.600> be 00:00:17.750 --> 00:00:17.760 align:start position:0% we'll be talking about pasis we'll be 00:00:17.760 --> 00:00:20.429 align:start position:0% we'll be talking about pasis we'll be talking<00:00:18.039> about<00:00:18.359> security<00:00:19.160> and<00:00:19.359> memes<00:00:19.920> as<00:00:20.080> well 00:00:20.429 --> 00:00:20.439 align:start position:0% talking about security and memes as well 00:00:20.439 --> 00:00:22.630 align:start position:0% talking about security and memes as well so<00:00:20.680> you'll<00:00:20.920> see<00:00:21.359> it<00:00:21.480> will<00:00:21.640> be<00:00:21.800> entertaining<00:00:22.480> I 00:00:22.630 --> 00:00:22.640 align:start position:0% so you'll see it will be entertaining I 00:00:22.640 --> 00:00:24.910 align:start position:0% so you'll see it will be entertaining I hope<00:00:23.400> I'll<00:00:23.599> be<00:00:23.720> going<00:00:24.039> fast<00:00:24.400> because<00:00:24.560> I<00:00:24.680> have<00:00:24.800> a 00:00:24.910 --> 00:00:24.920 align:start position:0% hope I'll be going fast because I have a 00:00:24.920 --> 00:00:26.990 align:start position:0% hope I'll be going fast because I have a lot<00:00:25.039> of<00:00:25.199> slides<00:00:25.760> so<00:00:26.240> don't 00:00:26.990 --> 00:00:27.000 align:start position:0% lot of slides so don't 00:00:27.000 --> 00:00:29.630 align:start position:0% lot of slides so don't sleep<00:00:28.000> um<00:00:28.240> so<00:00:28.480> first<00:00:28.760> you<00:00:28.880> might<00:00:29.080> be<00:00:29.199> wondering 00:00:29.630 --> 00:00:29.640 align:start position:0% sleep um so first you might be wondering 00:00:29.640 --> 00:00:31.630 align:start position:0% sleep um so first you might be wondering what<00:00:29.759> you<00:00:30.039> are<00:00:30.160> doing<00:00:30.359> in<00:00:30.519> this<00:00:30.720> room<00:00:31.320> uh<00:00:31.480> why 00:00:31.630 --> 00:00:31.640 align:start position:0% what you are doing in this room uh why 00:00:31.640 --> 00:00:33.790 align:start position:0% what you are doing in this room uh why are<00:00:31.759> we<00:00:31.960> talking<00:00:32.320> about<00:00:32.840> identity<00:00:33.280> and<00:00:33.480> access 00:00:33.790 --> 00:00:33.800 align:start position:0% are we talking about identity and access 00:00:33.800 --> 00:00:36.229 align:start position:0% are we talking about identity and access management<00:00:34.360> protocol<00:00:35.239> Pho<00:00:35.640> means<00:00:35.960> fast 00:00:36.229 --> 00:00:36.239 align:start position:0% management protocol Pho means fast 00:00:36.239 --> 00:00:38.630 align:start position:0% management protocol Pho means fast identity<00:00:36.719> online<00:00:37.239> so<00:00:37.559> why<00:00:37.719> are<00:00:37.960> we<00:00:38.200> here<00:00:38.520> it 00:00:38.630 --> 00:00:38.640 align:start position:0% identity online so why are we here it 00:00:38.640 --> 00:00:41.110 align:start position:0% identity online so why are we here it looks<00:00:38.920> very<00:00:39.160> complex<00:00:39.960> server<00:00:40.399> blocks<00:00:40.760> client 00:00:41.110 --> 00:00:41.120 align:start position:0% looks very complex server blocks client 00:00:41.120 --> 00:00:43.110 align:start position:0% looks very complex server blocks client blocks<00:00:41.840> a<00:00:42.000> lot<00:00:42.120> of<00:00:42.280> stuff<00:00:42.520> we<00:00:42.600> don't<00:00:42.800> do<00:00:42.960> with 00:00:43.110 --> 00:00:43.120 align:start position:0% blocks a lot of stuff we don't do with 00:00:43.120 --> 00:00:47.110 align:start position:0% blocks a lot of stuff we don't do with ethereum<00:00:43.920> but<00:00:44.920> uh<00:00:45.280> if<00:00:45.520> we<00:00:45.680> are<00:00:46.039> dents<00:00:46.760> like<00:00:46.960> we 00:00:47.110 --> 00:00:47.120 align:start position:0% ethereum but uh if we are dents like we 00:00:47.120 --> 00:00:49.150 align:start position:0% ethereum but uh if we are dents like we all<00:00:47.440> are<00:00:47.879> we<00:00:48.000> don't<00:00:48.199> really<00:00:48.480> care<00:00:48.719> about<00:00:48.960> all 00:00:49.150 --> 00:00:49.160 align:start position:0% all are we don't really care about all 00:00:49.160 --> 00:00:51.029 align:start position:0% all are we don't really care about all the<00:00:49.320> part<00:00:49.520> on<00:00:49.640> the<00:00:49.760> server<00:00:50.239> we<00:00:50.399> care<00:00:50.600> about<00:00:50.840> the 00:00:51.029 --> 00:00:51.039 align:start position:0% the part on the server we care about the 00:00:51.039 --> 00:00:53.229 align:start position:0% the part on the server we care about the fact<00:00:51.280> that<00:00:51.399> with<00:00:51.680> pass<00:00:51.960> Keys<00:00:52.239> we<00:00:52.399> can<00:00:52.680> generate 00:00:53.229 --> 00:00:53.239 align:start position:0% fact that with pass Keys we can generate 00:00:53.239 --> 00:00:56.069 align:start position:0% fact that with pass Keys we can generate keys<00:00:53.800> on<00:00:54.000> a<00:00:54.160> web<00:00:54.320> browser<00:00:55.000> and<00:00:55.399> this<00:00:55.559> is<00:00:55.840> very 00:00:56.069 --> 00:00:56.079 align:start position:0% keys on a web browser and this is very 00:00:56.079 --> 00:00:58.029 align:start position:0% keys on a web browser and this is very interesting<00:00:56.520> for<00:00:56.760> us<00:00:57.000> because<00:00:57.280> we<00:00:57.440> like<00:00:57.680> keys 00:00:58.029 --> 00:00:58.039 align:start position:0% interesting for us because we like keys 00:00:58.039 --> 00:01:03.670 align:start position:0% interesting for us because we like keys of<00:00:58.239> course<00:00:59.239> um<00:01:00.359> so<00:01:00.920> next<00:01:01.480> slide<00:01:02.480> yes<00:01:03.199> so<00:01:03.440> if<00:01:03.559> I 00:01:03.670 --> 00:01:03.680 align:start position:0% of course um so next slide yes so if I 00:01:03.680 --> 00:01:06.070 align:start position:0% of course um so next slide yes so if I want<00:01:03.840> to<00:01:04.000> go<00:01:04.199> through<00:01:04.760> a<00:01:05.320> presentation<00:01:05.799> of<00:01:05.920> the 00:01:06.070 --> 00:01:06.080 align:start position:0% want to go through a presentation of the 00:01:06.080 --> 00:01:08.109 align:start position:0% want to go through a presentation of the pho<00:01:06.439> protocol<00:01:06.799> in<00:01:06.920> one<00:01:07.159> slide<00:01:07.600> I<00:01:07.680> would<00:01:07.880> say 00:01:08.109 --> 00:01:08.119 align:start position:0% pho protocol in one slide I would say 00:01:08.119 --> 00:01:10.830 align:start position:0% pho protocol in one slide I would say that<00:01:08.320> Pho<00:01:08.680> is<00:01:08.799> an<00:01:08.920> Authentication<00:01:09.840> Protocol 00:01:10.830 --> 00:01:10.840 align:start position:0% that Pho is an Authentication Protocol 00:01:10.840 --> 00:01:12.590 align:start position:0% that Pho is an Authentication Protocol uh<00:01:10.960> you<00:01:11.119> have<00:01:11.240> a<00:01:11.400> registration<00:01:12.040> phase<00:01:12.439> where 00:01:12.590 --> 00:01:12.600 align:start position:0% uh you have a registration phase where 00:01:12.600 --> 00:01:14.190 align:start position:0% uh you have a registration phase where you<00:01:12.680> will<00:01:12.920> create<00:01:13.159> a<00:01:13.320> key<00:01:13.560> you<00:01:13.640> will<00:01:13.799> bind<00:01:14.080> it 00:01:14.190 --> 00:01:14.200 align:start position:0% you will create a key you will bind it 00:01:14.200 --> 00:01:16.950 align:start position:0% you will create a key you will bind it to<00:01:14.360> a<00:01:14.520> web<00:01:14.920> origin<00:01:15.920> and<00:01:16.280> then<00:01:16.479> you<00:01:16.640> have<00:01:16.840> an 00:01:16.950 --> 00:01:16.960 align:start position:0% to a web origin and then you have an 00:01:16.960 --> 00:01:18.550 align:start position:0% to a web origin and then you have an authentication<00:01:17.640> phase<00:01:17.960> where<00:01:18.119> you<00:01:18.240> will<00:01:18.439> get 00:01:18.550 --> 00:01:18.560 align:start position:0% authentication phase where you will get 00:01:18.560 --> 00:01:20.510 align:start position:0% authentication phase where you will get a<00:01:18.720> challenge<00:01:19.159> you<00:01:19.280> will<00:01:19.439> sign<00:01:19.759> it<00:01:20.079> and<00:01:20.200> so<00:01:20.400> you 00:01:20.510 --> 00:01:20.520 align:start position:0% a challenge you will sign it and so you 00:01:20.520 --> 00:01:22.350 align:start position:0% a challenge you will sign it and so you can<00:01:20.759> verify<00:01:21.280> that<00:01:21.439> you<00:01:21.600> are<00:01:21.799> in<00:01:21.920> the<00:01:22.119> right 00:01:22.350 --> 00:01:22.360 align:start position:0% can verify that you are in the right 00:01:22.360 --> 00:01:25.350 align:start position:0% can verify that you are in the right place<00:01:23.320> uh<00:01:23.479> we<00:01:23.640> have<00:01:23.960> recent<00:01:24.400> gas<00:01:24.640> optimization 00:01:25.350 --> 00:01:25.360 align:start position:0% place uh we have recent gas optimization 00:01:25.360 --> 00:01:27.749 align:start position:0% place uh we have recent gas optimization that<00:01:25.560> allow<00:01:25.880> us<00:01:26.079> to<00:01:26.320> run<00:01:26.600> the<00:01:26.720> pho<00:01:27.159> protocol<00:01:27.560> on 00:01:27.749 --> 00:01:27.759 align:start position:0% that allow us to run the pho protocol on 00:01:27.759 --> 00:01:29.670 align:start position:0% that allow us to run the pho protocol on chain<00:01:28.200> which<00:01:28.320> is<00:01:28.479> why<00:01:28.600> it's<00:01:28.799> interesting<00:01:29.520> and 00:01:29.670 --> 00:01:29.680 align:start position:0% chain which is why it's interesting and 00:01:29.680 --> 00:01:31.749 align:start position:0% chain which is why it's interesting and there<00:01:30.040> a<00:01:30.119> lot<00:01:30.240> of<00:01:30.360> abstraction<00:01:30.920> going<00:01:31.119> in<00:01:31.280> Pho 00:01:31.749 --> 00:01:31.759 align:start position:0% there a lot of abstraction going in Pho 00:01:31.759 --> 00:01:33.510 align:start position:0% there a lot of abstraction going in Pho so<00:01:31.920> a<00:01:32.040> lot<00:01:32.159> of<00:01:32.360> different<00:01:32.759> implementation<00:01:33.360> of 00:01:33.510 --> 00:01:33.520 align:start position:0% so a lot of different implementation of 00:01:33.520 --> 00:01:36.469 align:start position:0% so a lot of different implementation of this<00:01:33.720> protocol<00:01:34.159> going<00:01:34.399> on<00:01:35.399> um<00:01:35.840> why<00:01:36.159> this<00:01:36.280> is 00:01:36.469 --> 00:01:36.479 align:start position:0% this protocol going on um why this is 00:01:36.479 --> 00:01:40.230 align:start position:0% this protocol going on um why this is interesting<00:01:37.200> again<00:01:37.880> we<00:01:38.079> got<00:01:38.520> a<00:01:38.799> go<00:01:39.079> tier<00:01:39.399> ux<00:01:39.960> on 00:01:40.230 --> 00:01:40.240 align:start position:0% interesting again we got a go tier ux on 00:01:40.240 --> 00:01:42.670 align:start position:0% interesting again we got a go tier ux on mobile<00:01:40.640> with<00:01:40.799> a<00:01:41.159> abstraction<00:01:41.799> with<00:01:42.000> pass<00:01:42.280> keys 00:01:42.670 --> 00:01:42.680 align:start position:0% mobile with a abstraction with pass keys 00:01:42.680 --> 00:01:44.429 align:start position:0% mobile with a abstraction with pass keys if<00:01:42.799> you<00:01:42.920> have<00:01:43.079> not<00:01:43.280> tried<00:01:43.560> it<00:01:43.759> already<00:01:44.119> I<00:01:44.240> will 00:01:44.429 --> 00:01:44.439 align:start position:0% if you have not tried it already I will 00:01:44.439 --> 00:01:46.550 align:start position:0% if you have not tried it already I will suggest<00:01:44.880> trying<00:01:45.240> the<00:01:45.399> coinbase<00:01:45.880> smart<00:01:46.079> wallet 00:01:46.550 --> 00:01:46.560 align:start position:0% suggest trying the coinbase smart wallet 00:01:46.560 --> 00:01:49.310 align:start position:0% suggest trying the coinbase smart wallet which<00:01:46.680> is<00:01:46.840> very<00:01:47.280> impressive<00:01:48.280> uh<00:01:48.439> but<00:01:48.560> you<00:01:48.799> get 00:01:49.310 --> 00:01:49.320 align:start position:0% which is very impressive uh but you get 00:01:49.320 --> 00:01:51.429 align:start position:0% which is very impressive uh but you get something<00:01:49.840> that<00:01:50.000> is<00:01:50.240> very<00:01:50.439> close<00:01:50.719> to<00:01:51.000> web<00:01:51.200> to 00:01:51.429 --> 00:01:51.439 align:start position:0% something that is very close to web to 00:01:51.439 --> 00:01:54.310 align:start position:0% something that is very close to web to experience<00:01:52.000> you<00:01:52.200> just<00:01:52.360> use<00:01:52.680> your<00:01:53.320> Biometrics 00:01:54.310 --> 00:01:54.320 align:start position:0% experience you just use your Biometrics 00:01:54.320 --> 00:01:56.990 align:start position:0% experience you just use your Biometrics and<00:01:54.719> you<00:01:54.880> are<00:01:55.640> you<00:01:55.840> have<00:01:56.200> a<00:01:56.360> wallet<00:01:56.840> this 00:01:56.990 --> 00:01:57.000 align:start position:0% and you are you have a wallet this 00:01:57.000 --> 00:01:59.149 align:start position:0% and you are you have a wallet this wallet<00:01:57.280> is<00:01:57.360> self<00:01:57.680> custodial<00:01:58.560> so<00:01:58.719> you<00:01:58.880> can 00:01:59.149 --> 00:01:59.159 align:start position:0% wallet is self custodial so you can 00:01:59.159 --> 00:02:01.190 align:start position:0% wallet is self custodial so you can pretty<00:01:59.399> much<00:01:59.600> do<00:01:59.960> whatever<00:02:00.280> you<00:02:00.399> want<00:02:00.920> and 00:02:01.190 --> 00:02:01.200 align:start position:0% pretty much do whatever you want and 00:02:01.200 --> 00:02:02.789 align:start position:0% pretty much do whatever you want and well<00:02:01.399> it's<00:02:01.600> super<00:02:02.000> it's<00:02:02.159> super<00:02:02.439> easy<00:02:02.640> to 00:02:02.789 --> 00:02:02.799 align:start position:0% well it's super it's super easy to 00:02:02.799 --> 00:02:04.350 align:start position:0% well it's super it's super easy to create<00:02:03.079> an<00:02:03.240> account<00:02:03.439> on<00:02:03.600> mobile<00:02:03.920> with<00:02:04.119> pass 00:02:04.350 --> 00:02:04.360 align:start position:0% create an account on mobile with pass 00:02:04.360 --> 00:02:07.069 align:start position:0% create an account on mobile with pass Keys<00:02:05.159> uh<00:02:05.399> on<00:02:05.640> desktop<00:02:06.079> it's<00:02:06.200> a<00:02:06.360> bit<00:02:06.600> different 00:02:07.069 --> 00:02:07.079 align:start position:0% Keys uh on desktop it's a bit different 00:02:07.079 --> 00:02:09.469 align:start position:0% Keys uh on desktop it's a bit different but<00:02:07.240> it's<00:02:07.399> standard<00:02:07.920> as<00:02:08.080> well<00:02:08.599> so<00:02:09.000> it's<00:02:09.200> good 00:02:09.469 --> 00:02:09.479 align:start position:0% but it's standard as well so it's good 00:02:09.479 --> 00:02:11.430 align:start position:0% but it's standard as well so it's good because<00:02:09.679> you<00:02:09.800> have<00:02:09.879> a<00:02:10.000> common<00:02:10.319> interface<00:02:11.280> you 00:02:11.430 --> 00:02:11.440 align:start position:0% because you have a common interface you 00:02:11.440 --> 00:02:13.190 align:start position:0% because you have a common interface you have<00:02:11.560> a<00:02:11.720> QR<00:02:12.160> you<00:02:12.239> can<00:02:12.400> redirect<00:02:12.879> to<00:02:13.000> your 00:02:13.190 --> 00:02:13.200 align:start position:0% have a QR you can redirect to your 00:02:13.200 --> 00:02:15.390 align:start position:0% have a QR you can redirect to your mobile<00:02:14.000> uh<00:02:14.160> if<00:02:14.280> you<00:02:14.400> have<00:02:14.519> an<00:02:14.680> Android<00:02:15.080> phone 00:02:15.390 --> 00:02:15.400 align:start position:0% mobile uh if you have an Android phone 00:02:15.400 --> 00:02:18.430 align:start position:0% mobile uh if you have an Android phone you<00:02:15.560> can<00:02:16.080> just<00:02:16.519> avoid<00:02:17.280> scanning<00:02:17.680> the<00:02:17.840> QR<00:02:18.200> every 00:02:18.430 --> 00:02:18.440 align:start position:0% you can just avoid scanning the QR every 00:02:18.440 --> 00:02:20.630 align:start position:0% you can just avoid scanning the QR every time<00:02:18.640> you<00:02:18.760> can<00:02:18.920> scan<00:02:19.200> it<00:02:19.400> once<00:02:19.920> and<00:02:20.120> then<00:02:20.519> it 00:02:20.630 --> 00:02:20.640 align:start position:0% time you can scan it once and then it 00:02:20.640 --> 00:02:23.030 align:start position:0% time you can scan it once and then it will<00:02:20.840> be<00:02:21.200> recognized<00:02:22.200> automatically<00:02:22.920> but 00:02:23.030 --> 00:02:23.040 align:start position:0% will be recognized automatically but 00:02:23.040 --> 00:02:25.589 align:start position:0% will be recognized automatically but it's<00:02:23.440> proprietary<00:02:24.440> so<00:02:24.720> it's<00:02:24.920> not<00:02:25.080> a<00:02:25.319> great 00:02:25.589 --> 00:02:25.599 align:start position:0% it's proprietary so it's not a great 00:02:25.599 --> 00:02:27.550 align:start position:0% it's proprietary so it's not a great interface<00:02:26.120> but<00:02:26.280> at<00:02:26.400> least<00:02:26.560> it's<00:02:26.720> standard<00:02:27.360> on 00:02:27.550 --> 00:02:27.560 align:start position:0% interface but at least it's standard on 00:02:27.560 --> 00:02:29.350 align:start position:0% interface but at least it's standard on all<00:02:27.760> the<00:02:27.879> implementation<00:02:28.680> so<00:02:28.840> you<00:02:28.959> have<00:02:29.080> a<00:02:29.239> way 00:02:29.350 --> 00:02:29.360 align:start position:0% all the implementation so you have a way 00:02:29.360 --> 00:02:31.229 align:start position:0% all the implementation so you have a way to<00:02:29.519> connect<00:02:29.920> your<00:02:30.040> desktop<00:02:30.400> to<00:02:30.519> your<00:02:30.720> mobile 00:02:31.229 --> 00:02:31.239 align:start position:0% to connect your desktop to your mobile 00:02:31.239 --> 00:02:34.229 align:start position:0% to connect your desktop to your mobile and<00:02:31.599> it's<00:02:31.800> not<00:02:32.000> too<00:02:32.239> confusing<00:02:32.800> let's<00:02:33.040> say<00:02:33.920> um 00:02:34.229 --> 00:02:34.239 align:start position:0% and it's not too confusing let's say um 00:02:34.239 --> 00:02:35.910 align:start position:0% and it's not too confusing let's say um regarding<00:02:34.640> a<00:02:34.800> web 00:02:35.910 --> 00:02:35.920 align:start position:0% regarding a web 00:02:35.920 --> 00:02:38.470 align:start position:0% regarding a web developer<00:02:36.920> the<00:02:37.120> experience<00:02:37.720> is<00:02:38.200> pretty 00:02:38.470 --> 00:02:38.480 align:start position:0% developer the experience is pretty 00:02:38.480 --> 00:02:40.270 align:start position:0% developer the experience is pretty standardized<00:02:39.200> pretty<00:02:39.440> simple<00:02:39.840> as<00:02:40.000> well 00:02:40.270 --> 00:02:40.280 align:start position:0% standardized pretty simple as well 00:02:40.280 --> 00:02:43.229 align:start position:0% standardized pretty simple as well because<00:02:40.560> this<00:02:40.760> was<00:02:41.080> acquired<00:02:41.599> by<00:02:41.760> web<00:02:42.159> 10<00:02:43.000> by 00:02:43.229 --> 00:02:43.239 align:start position:0% because this was acquired by web 10 by 00:02:43.239 --> 00:02:46.509 align:start position:0% because this was acquired by web 10 by the<00:02:43.440> w3c<00:02:44.280> sorry<00:02:44.680> under<00:02:44.959> the<00:02:45.120> name<00:02:45.319> web<00:02:45.680> 10<00:02:46.319> so 00:02:46.509 --> 00:02:46.519 align:start position:0% the w3c sorry under the name web 10 so 00:02:46.519 --> 00:02:48.149 align:start position:0% the w3c sorry under the name web 10 so you<00:02:46.680> pass<00:02:46.959> common<00:02:47.280> parameters<00:02:47.840> when<00:02:47.959> you 00:02:48.149 --> 00:02:48.159 align:start position:0% you pass common parameters when you 00:02:48.159 --> 00:02:50.390 align:start position:0% you pass common parameters when you register<00:02:49.040> like<00:02:49.239> the<00:02:49.360> user<00:02:49.680> information<00:02:50.239> the 00:02:50.390 --> 00:02:50.400 align:start position:0% register like the user information the 00:02:50.400 --> 00:02:53.190 align:start position:0% register like the user information the key<00:02:50.599> type<00:02:50.840> the<00:02:51.000> challenge<00:02:51.640> so<00:02:51.959> two<00:02:52.239> API<00:02:52.840> super 00:02:53.190 --> 00:02:53.200 align:start position:0% key type the challenge so two API super 00:02:53.200 --> 00:02:55.470 align:start position:0% key type the challenge so two API super simple<00:02:53.959> I've<00:02:54.159> been<00:02:54.360> going<00:02:54.599> through<00:02:54.920> this<00:02:55.200> very 00:02:55.470 --> 00:02:55.480 align:start position:0% simple I've been going through this very 00:02:55.480 --> 00:02:57.630 align:start position:0% simple I've been going through this very very<00:02:55.720> quickly<00:02:56.200> because<00:02:56.599> we<00:02:56.720> are<00:02:56.879> not<00:02:57.159> yet<00:02:57.440> at 00:02:57.630 --> 00:02:57.640 align:start position:0% very quickly because we are not yet at 00:02:57.640 --> 00:02:59.910 align:start position:0% very quickly because we are not yet at the<00:02:57.840> interesting<00:02:58.400> part<00:02:59.080> the<00:02:59.239> interesting 00:02:59.910 --> 00:02:59.920 align:start position:0% the interesting part the interesting 00:02:59.920 --> 00:03:01.790 align:start position:0% the interesting part the interesting part<00:03:00.120> is<00:03:00.239> going<00:03:00.440> to<00:03:00.599> start<00:03:00.959> now<00:03:01.400> because<00:03:01.680> you 00:03:01.790 --> 00:03:01.800 align:start position:0% part is going to start now because you 00:03:01.800 --> 00:03:03.550 align:start position:0% part is going to start now because you are<00:03:02.040> all<00:03:02.319> wondering<00:03:02.879> where<00:03:03.080> the<00:03:03.239> key<00:03:03.440> is 00:03:03.550 --> 00:03:03.560 align:start position:0% are all wondering where the key is 00:03:03.560 --> 00:03:06.750 align:start position:0% are all wondering where the key is stored<00:03:04.400> we<00:03:04.519> say<00:03:04.799> we<00:03:04.920> have<00:03:05.159> keys<00:03:05.720> but<00:03:06.040> well 00:03:06.750 --> 00:03:06.760 align:start position:0% stored we say we have keys but well 00:03:06.760 --> 00:03:08.149 align:start position:0% stored we say we have keys but well where<00:03:06.920> is<00:03:07.040> it<00:03:07.159> stored<00:03:07.519> this<00:03:07.640> is<00:03:07.799> the<00:03:07.920> real 00:03:08.149 --> 00:03:08.159 align:start position:0% where is it stored this is the real 00:03:08.159 --> 00:03:10.550 align:start position:0% where is it stored this is the real question<00:03:09.120> and<00:03:09.319> unfortunately<00:03:10.000> to<00:03:10.159> answer 00:03:10.550 --> 00:03:10.560 align:start position:0% question and unfortunately to answer 00:03:10.560 --> 00:03:12.309 align:start position:0% question and unfortunately to answer this<00:03:10.760> we<00:03:10.879> have<00:03:11.000> to<00:03:11.200> go<00:03:11.319> through<00:03:11.599> a<00:03:11.799> very<00:03:12.040> very 00:03:12.309 --> 00:03:12.319 align:start position:0% this we have to go through a very very 00:03:12.319 --> 00:03:14.910 align:start position:0% this we have to go through a very very large<00:03:12.599> bit<00:03:12.799> of<00:03:13.000> History<00:03:13.879> so<00:03:14.280> I<00:03:14.360> will<00:03:14.519> be<00:03:14.720> just 00:03:14.910 --> 00:03:14.920 align:start position:0% large bit of History so I will be just 00:03:14.920 --> 00:03:17.509 align:start position:0% large bit of History so I will be just doing<00:03:15.280> this<00:03:16.040> uh<00:03:16.159> the<00:03:16.280> pho<00:03:16.680> story<00:03:16.959> starts<00:03:17.280> in 00:03:17.509 --> 00:03:17.519 align:start position:0% doing this uh the pho story starts in 00:03:17.519 --> 00:03:20.110 align:start position:0% doing this uh the pho story starts in 2013<00:03:18.519> with<00:03:18.680> two<00:03:18.920> protocols<00:03:19.440> the<00:03:19.599> universal 00:03:20.110 --> 00:03:20.120 align:start position:0% 2013 with two protocols the universal 00:03:20.120 --> 00:03:21.750 align:start position:0% 2013 with two protocols the universal second<00:03:20.599> factor<00:03:21.120> and<00:03:21.280> Universal 00:03:21.750 --> 00:03:21.760 align:start position:0% second factor and Universal 00:03:21.760 --> 00:03:24.149 align:start position:0% second factor and Universal authentication<00:03:22.519> Factor<00:03:23.480> um<00:03:23.640> Universal 00:03:24.149 --> 00:03:24.159 align:start position:0% authentication Factor um Universal 00:03:24.159 --> 00:03:27.710 align:start position:0% authentication Factor um Universal second<00:03:24.560> factor<00:03:24.840> is<00:03:24.959> the<00:03:25.480> best<00:03:26.200> known<00:03:27.200> and<00:03:27.480> both 00:03:27.710 --> 00:03:27.720 align:start position:0% second factor is the best known and both 00:03:27.720 --> 00:03:29.789 align:start position:0% second factor is the best known and both protocol<00:03:28.120> are<00:03:28.280> mostly<00:03:28.720> State<00:03:29.040> class 00:03:29.789 --> 00:03:29.799 align:start position:0% protocol are mostly State class 00:03:29.799 --> 00:03:32.070 align:start position:0% protocol are mostly State class stateless<00:03:30.280> meaning<00:03:30.720> that<00:03:31.000> all<00:03:31.239> credentials 00:03:32.070 --> 00:03:32.080 align:start position:0% stateless meaning that all credentials 00:03:32.080 --> 00:03:34.750 align:start position:0% stateless meaning that all credentials are<00:03:32.400> not<00:03:32.680> saved<00:03:33.480> uh<00:03:33.599> in<00:03:33.720> the<00:03:33.959> device 00:03:34.750 --> 00:03:34.760 align:start position:0% are not saved uh in the device 00:03:34.760 --> 00:03:36.589 align:start position:0% are not saved uh in the device credentials<00:03:35.319> are<00:03:35.519> generated<00:03:35.959> in<00:03:36.080> the<00:03:36.280> device 00:03:36.589 --> 00:03:36.599 align:start position:0% credentials are generated in the device 00:03:36.599 --> 00:03:38.949 align:start position:0% credentials are generated in the device saved<00:03:36.920> on<00:03:37.040> the<00:03:37.200> server<00:03:37.760> so<00:03:38.120> the<00:03:38.319> device<00:03:38.640> can<00:03:38.799> be 00:03:38.949 --> 00:03:38.959 align:start position:0% saved on the server so the device can be 00:03:38.959 --> 00:03:41.830 align:start position:0% saved on the server so the device can be used<00:03:39.239> to<00:03:40.120> generate<00:03:40.720> an<00:03:40.959> infinite<00:03:41.360> number<00:03:41.599> of 00:03:41.830 --> 00:03:41.840 align:start position:0% used to generate an infinite number of 00:03:41.840 --> 00:03:44.190 align:start position:0% used to generate an infinite number of credentials<00:03:42.840> uh<00:03:42.959> it<00:03:43.080> was<00:03:43.239> supported<00:03:43.760> launched 00:03:44.190 --> 00:03:44.200 align:start position:0% credentials uh it was supported launched 00:03:44.200 --> 00:03:47.589 align:start position:0% credentials uh it was supported launched initially<00:03:44.680> by<00:03:44.799> Google<00:03:45.080> and<00:03:45.360> ubo<00:03:46.360> 2014<00:03:47.360> this<00:03:47.480> is 00:03:47.589 --> 00:03:47.599 align:start position:0% initially by Google and ubo 2014 this is 00:03:47.599 --> 00:03:49.229 align:start position:0% initially by Google and ubo 2014 this is a<00:03:47.760> real<00:03:48.040> commercial<00:03:48.480> launch<00:03:48.879> with<00:03:49.040> two 00:03:49.229 --> 00:03:49.239 align:start position:0% a real commercial launch with two 00:03:49.239 --> 00:03:52.429 align:start position:0% a real commercial launch with two devices<00:03:50.000> uh<00:03:50.159> UB<00:03:50.560> key<00:03:50.840> and<00:03:51.120> one<00:03:51.439> device<00:03:52.159> uh<00:03:52.239> on 00:03:52.429 --> 00:03:52.439 align:start position:0% devices uh UB key and one device uh on 00:03:52.439 --> 00:03:54.509 align:start position:0% devices uh UB key and one device uh on which<00:03:52.640> I<00:03:52.799> worked<00:03:53.079> on<00:03:53.720> if<00:03:53.840> you<00:03:53.959> look<00:03:54.120> at<00:03:54.239> it<00:03:54.360> you 00:03:54.509 --> 00:03:54.519 align:start position:0% which I worked on if you look at it you 00:03:54.519 --> 00:03:57.350 align:start position:0% which I worked on if you look at it you might<00:03:54.799> recognize<00:03:55.319> the<00:03:55.640> early<00:03:55.959> Ledger<00:03:56.439> design 00:03:57.350 --> 00:03:57.360 align:start position:0% might recognize the early Ledger design 00:03:57.360 --> 00:04:01.470 align:start position:0% might recognize the early Ledger design very<00:03:57.640> similar<00:03:58.519> 2018<00:03:59.400> f<00:03:59.920> 2<00:04:00.079> is<00:04:00.159> launched<00:04:00.680> pH<00:04:01.120> 2 00:04:01.470 --> 00:04:01.480 align:start position:0% very similar 2018 f 2 is launched pH 2 00:04:01.480 --> 00:04:04.069 align:start position:0% very similar 2018 f 2 is launched pH 2 introduces<00:04:02.200> something<00:04:02.599> new<00:04:03.439> it's<00:04:03.640> basically 00:04:04.069 --> 00:04:04.079 align:start position:0% introduces something new it's basically 00:04:04.079 --> 00:04:06.830 align:start position:0% introduces something new it's basically a<00:04:04.239> fusion<00:04:04.760> between<00:04:05.079> newf<00:04:05.599> and<00:04:05.720> UF<00:04:06.640> and 00:04:06.830 --> 00:04:06.840 align:start position:0% a fusion between newf and UF and 00:04:06.840 --> 00:04:09.069 align:start position:0% a fusion between newf and UF and introduces<00:04:07.360> a<00:04:07.560> concept<00:04:08.000> of<00:04:08.200> resident<00:04:08.640> or 00:04:09.069 --> 00:04:09.079 align:start position:0% introduces a concept of resident or 00:04:09.079 --> 00:04:10.190 align:start position:0% introduces a concept of resident or discoverable 00:04:10.190 --> 00:04:10.200 align:start position:0% discoverable 00:04:10.200 --> 00:04:12.949 align:start position:0% discoverable credential<00:04:11.200> those<00:04:11.400> credential<00:04:11.920> are<00:04:12.120> stored 00:04:12.949 --> 00:04:12.959 align:start position:0% credential those credential are stored 00:04:12.959 --> 00:04:14.750 align:start position:0% credential those credential are stored into<00:04:13.239> the<00:04:13.480> device<00:04:13.959> so<00:04:14.159> this<00:04:14.360> completely 00:04:14.750 --> 00:04:14.760 align:start position:0% into the device so this completely 00:04:14.760 --> 00:04:16.349 align:start position:0% into the device so this completely changes<00:04:15.200> the<00:04:15.360> state<00:04:15.599> of<00:04:15.760> the<00:04:15.879> protocol 00:04:16.349 --> 00:04:16.359 align:start position:0% changes the state of the protocol 00:04:16.359 --> 00:04:19.949 align:start position:0% changes the state of the protocol because<00:04:16.639> now<00:04:17.160> it<00:04:17.280> goes<00:04:17.519> State<00:04:17.919> full<00:04:18.959> 2019 00:04:19.949 --> 00:04:19.959 align:start position:0% because now it goes State full 2019 00:04:19.959 --> 00:04:23.830 align:start position:0% because now it goes State full 2019 Weber<00:04:20.359> 10<00:04:21.359> uh<00:04:21.519> is<00:04:21.720> launched<00:04:22.160> by<00:04:22.400> w3c<00:04:23.400> so<00:04:23.600> it's 00:04:23.830 --> 00:04:23.840 align:start position:0% Weber 10 uh is launched by w3c so it's 00:04:23.840 --> 00:04:26.790 align:start position:0% Weber 10 uh is launched by w3c so it's basically<00:04:24.199> Pho<00:04:24.680> but<00:04:24.840> acquired<00:04:25.240> by<00:04:25.400> w3c<00:04:26.400> and<00:04:26.680> at 00:04:26.790 --> 00:04:26.800 align:start position:0% basically Pho but acquired by w3c and at 00:04:26.800 --> 00:04:29.270 align:start position:0% basically Pho but acquired by w3c and at the<00:04:26.960> same<00:04:27.240> time<00:04:27.960> on<00:04:28.199> Android<00:04:28.759> you<00:04:28.880> have<00:04:29.000> the 00:04:29.270 --> 00:04:29.280 align:start position:0% the same time on Android you have the 00:04:29.280 --> 00:04:32.310 align:start position:0% the same time on Android you have the strong<00:04:29.440> box<00:04:30.039> API<00:04:30.639> which<00:04:30.960> appears<00:04:31.680> and<00:04:31.919> it<00:04:32.080> is 00:04:32.310 --> 00:04:32.320 align:start position:0% strong box API which appears and it is 00:04:32.320 --> 00:04:34.469 align:start position:0% strong box API which appears and it is the<00:04:32.520> equivalent<00:04:33.039> of<00:04:33.160> the<00:04:33.280> secure<00:04:33.560> Enclave<00:04:34.160> on 00:04:34.469 --> 00:04:34.479 align:start position:0% the equivalent of the secure Enclave on 00:04:34.479 --> 00:04:36.710 align:start position:0% the equivalent of the secure Enclave on iOS<00:04:34.919> devices<00:04:35.479> so<00:04:35.800> very<00:04:36.039> secure<00:04:36.400> place<00:04:36.600> to 00:04:36.710 --> 00:04:36.720 align:start position:0% iOS devices so very secure place to 00:04:36.720 --> 00:04:40.790 align:start position:0% iOS devices so very secure place to store<00:04:37.000> keys<00:04:37.800> and<00:04:37.960> Android<00:04:38.360> got<00:04:38.600> pH 00:04:40.790 --> 00:04:40.800 align:start position:0% store keys and Android got pH 00:04:40.800 --> 00:04:43.150 align:start position:0% store keys and Android got pH 235<00:04:41.800> I<00:04:41.919> think<00:04:42.120> you<00:04:42.199> are<00:04:42.360> getting<00:04:42.560> a<00:04:42.720> trend 00:04:43.150 --> 00:04:43.160 align:start position:0% 235 I think you are getting a trend 00:04:43.160 --> 00:04:47.189 align:start position:0% 235 I think you are getting a trend there<00:04:43.919> uh<00:04:44.160> we<00:04:44.400> get<00:04:44.800> ios<00:04:45.280> support<00:04:45.680> in<00:04:46.080> 2020<00:04:47.080> and 00:04:47.189 --> 00:04:47.199 align:start position:0% there uh we get ios support in 2020 and 00:04:47.199 --> 00:04:49.230 align:start position:0% there uh we get ios support in 2020 and we<00:04:47.320> see<00:04:47.560> that<00:04:47.720> Pho<00:04:48.199> starts<00:04:48.520> to<00:04:48.639> be<00:04:48.800> supported 00:04:49.230 --> 00:04:49.240 align:start position:0% we see that Pho starts to be supported 00:04:49.240 --> 00:04:51.590 align:start position:0% we see that Pho starts to be supported in<00:04:49.440> devices<00:04:49.960> which<00:04:50.120> are<00:04:50.360> very<00:04:50.600> secure<00:04:51.199> so<00:04:51.440> it 00:04:51.590 --> 00:04:51.600 align:start position:0% in devices which are very secure so it 00:04:51.600 --> 00:04:53.710 align:start position:0% in devices which are very secure so it all<00:04:51.880> looks<00:04:52.240> very<00:04:52.479> good<00:04:52.919> at<00:04:53.039> the<00:04:53.199> moment 00:04:53.710 --> 00:04:53.720 align:start position:0% all looks very good at the moment 00:04:53.720 --> 00:04:55.710 align:start position:0% all looks very good at the moment because<00:04:54.080> we<00:04:54.199> have<00:04:54.479> dedicated<00:04:55.039> device<00:04:55.440> with 00:04:55.710 --> 00:04:55.720 align:start position:0% because we have dedicated device with 00:04:55.720 --> 00:04:57.990 align:start position:0% because we have dedicated device with secure<00:04:56.160> Hardware<00:04:56.479> to<00:04:56.639> support<00:04:56.960> Pho<00:04:57.759> we<00:04:57.880> have 00:04:57.990 --> 00:04:58.000 align:start position:0% secure Hardware to support Pho we have 00:04:58.000 --> 00:05:00.189 align:start position:0% secure Hardware to support Pho we have it<00:04:58.120> in<00:04:58.240> phones<00:04:58.600> with<00:04:58.880> strong<00:04:59.080> security 00:05:00.189 --> 00:05:00.199 align:start position:0% it in phones with strong security 00:05:00.199 --> 00:05:03.070 align:start position:0% it in phones with strong security and<00:05:00.360> in<00:05:00.720> 2022<00:05:01.720> things<00:05:02.120> start<00:05:02.520> changing 00:05:03.070 --> 00:05:03.080 align:start position:0% and in 2022 things start changing 00:05:03.080 --> 00:05:04.670 align:start position:0% and in 2022 things start changing because<00:05:03.320> we<00:05:03.440> shared<00:05:03.919> we<00:05:04.039> get<00:05:04.199> a<00:05:04.280> shared 00:05:04.670 --> 00:05:04.680 align:start position:0% because we shared we get a shared 00:05:04.680 --> 00:05:06.350 align:start position:0% because we shared we get a shared announcement<00:05:05.240> from<00:05:05.479> Google<00:05:05.919> Apple<00:05:06.160> and 00:05:06.350 --> 00:05:06.360 align:start position:0% announcement from Google Apple and 00:05:06.360 --> 00:05:08.550 align:start position:0% announcement from Google Apple and Microsoft<00:05:07.000> saying<00:05:07.680> this<00:05:07.840> protocol<00:05:08.240> looks 00:05:08.550 --> 00:05:08.560 align:start position:0% Microsoft saying this protocol looks 00:05:08.560 --> 00:05:10.310 align:start position:0% Microsoft saying this protocol looks nice<00:05:08.919> we<00:05:09.000> are<00:05:09.160> going<00:05:09.320> to<00:05:09.479> support<00:05:09.800> it<00:05:09.919> a<00:05:10.080> lot 00:05:10.310 --> 00:05:10.320 align:start position:0% nice we are going to support it a lot 00:05:10.320 --> 00:05:12.950 align:start position:0% nice we are going to support it a lot more<00:05:11.320> and<00:05:11.639> usually<00:05:12.120> when<00:05:12.240> you<00:05:12.360> get<00:05:12.560> this<00:05:12.759> kind 00:05:12.950 --> 00:05:12.960 align:start position:0% more and usually when you get this kind 00:05:12.960 --> 00:05:14.550 align:start position:0% more and usually when you get this kind of<00:05:13.120> announcement<00:05:13.639> it's<00:05:13.800> the<00:05:13.960> beginning<00:05:14.320> of 00:05:14.550 --> 00:05:14.560 align:start position:0% of announcement it's the beginning of 00:05:14.560 --> 00:05:17.670 align:start position:0% of announcement it's the beginning of assimilation<00:05:15.560> and<00:05:16.400> this<00:05:16.680> assimilation<00:05:17.360> has<00:05:17.479> a 00:05:17.670 --> 00:05:17.680 align:start position:0% assimilation and this assimilation has a 00:05:17.680 --> 00:05:19.309 align:start position:0% assimilation and this assimilation has a name<00:05:18.080> Pas 00:05:19.309 --> 00:05:19.319 align:start position:0% name Pas 00:05:19.319 --> 00:05:23.430 align:start position:0% name Pas keys<00:05:20.319> so<00:05:21.000> well<00:05:21.319> first<00:05:21.600> thing<00:05:21.840> we<00:05:21.960> can<00:05:22.280> say<00:05:23.160> in 00:05:23.430 --> 00:05:23.440 align:start position:0% keys so well first thing we can say in 00:05:23.440 --> 00:05:27.510 align:start position:0% keys so well first thing we can say in 20123<00:05:24.440> it<00:05:24.639> starts<00:05:25.160> with<00:05:26.000> uh<00:05:26.720> the<00:05:26.880> introduction 00:05:27.510 --> 00:05:27.520 align:start position:0% 20123 it starts with uh the introduction 00:05:27.520 --> 00:05:30.230 align:start position:0% 20123 it starts with uh the introduction of<00:05:27.680> thinkable<00:05:28.240> credentials<00:05:29.240> um<00:05:29.319> so<00:05:29.919> show<00:05:30.120> that 00:05:30.230 --> 00:05:30.240 align:start position:0% of thinkable credentials um so show that 00:05:30.240 --> 00:05:33.150 align:start position:0% of thinkable credentials um so show that can<00:05:30.360> be<00:05:30.479> synced<00:05:30.919> to<00:05:31.280> to<00:05:31.520> different<00:05:31.960> devices<00:05:32.960> uh 00:05:33.150 --> 00:05:33.160 align:start position:0% can be synced to to different devices uh 00:05:33.160 --> 00:05:34.950 align:start position:0% can be synced to to different devices uh either<00:05:33.440> with<00:05:33.560> a<00:05:33.720> propriatary<00:05:34.120> scheme<00:05:34.680> or 00:05:34.950 --> 00:05:34.960 align:start position:0% either with a propriatary scheme or 00:05:34.960 --> 00:05:37.309 align:start position:0% either with a propriatary scheme or password<00:05:35.520> manager<00:05:36.520> um<00:05:36.720> so<00:05:36.960> here's<00:05:37.160> the 00:05:37.309 --> 00:05:37.319 align:start position:0% password manager um so here's the 00:05:37.319 --> 00:05:39.950 align:start position:0% password manager um so here's the illustration<00:05:38.120> is<00:05:38.280> a<00:05:38.440> big<00:05:38.639> Temple<00:05:39.520> because<00:05:39.800> we 00:05:39.950 --> 00:05:39.960 align:start position:0% illustration is a big Temple because we 00:05:39.960 --> 00:05:43.230 align:start position:0% illustration is a big Temple because we are<00:05:40.199> in<00:05:40.680> Bangkok<00:05:41.479> temples<00:05:41.880> are<00:05:42.039> called<00:05:42.280> wat<00:05:43.080> so 00:05:43.230 --> 00:05:43.240 align:start position:0% are in Bangkok temples are called wat so 00:05:43.240 --> 00:05:45.230 align:start position:0% are in Bangkok temples are called wat so this<00:05:43.360> is<00:05:43.520> wat<00:05:43.759> for<00:05:44.000> I<00:05:44.120> didn't<00:05:44.400> visit<00:05:44.680> it<00:05:44.919> yet 00:05:45.230 --> 00:05:45.240 align:start position:0% this is wat for I didn't visit it yet 00:05:45.240 --> 00:05:49.350 align:start position:0% this is wat for I didn't visit it yet but<00:05:45.520> yeah<00:05:45.919> what<00:05:46.919> uh<00:05:47.120> and<00:05:47.240> in<00:05:47.840> 2024<00:05:48.840> the<00:05:48.960> pho 00:05:49.350 --> 00:05:49.360 align:start position:0% but yeah what uh and in 2024 the pho 00:05:49.360 --> 00:05:51.670 align:start position:0% but yeah what uh and in 2024 the pho Alliance<00:05:49.960> finally<00:05:50.800> uh<00:05:51.039> performed<00:05:51.560> the 00:05:51.670 --> 00:05:51.680 align:start position:0% Alliance finally uh performed the 00:05:51.680 --> 00:05:53.909 align:start position:0% Alliance finally uh performed the general<00:05:52.000> rebounding<00:05:52.520> iron<00:05:52.880> pass<00:05:53.120> keys<00:05:53.360> so<00:05:53.520> no 00:05:53.909 --> 00:05:53.919 align:start position:0% general rebounding iron pass keys so no 00:05:53.919 --> 00:05:56.830 align:start position:0% general rebounding iron pass keys so no pasy<00:05:54.680> is<00:05:54.919> just<00:05:55.120> describing<00:05:55.560> a<00:05:55.680> phyto 00:05:56.830 --> 00:05:56.840 align:start position:0% pasy is just describing a phyto 00:05:56.840 --> 00:05:58.629 align:start position:0% pasy is just describing a phyto credential<00:05:57.840> and<00:05:58.039> we'll<00:05:58.199> start<00:05:58.440> a 00:05:58.629 --> 00:05:58.639 align:start position:0% credential and we'll start a 00:05:58.639 --> 00:06:00.309 align:start position:0% credential and we'll start a specification<00:05:59.759> uh<00:05:59.880> to<00:06:00.000> make<00:06:00.199> the 00:06:00.309 --> 00:06:00.319 align:start position:0% specification uh to make the 00:06:00.319 --> 00:06:02.990 align:start position:0% specification uh to make the synchronization<00:06:01.000> a<00:06:01.120> bit<00:06:01.360> less 00:06:02.990 --> 00:06:03.000 align:start position:0% synchronization a bit less 00:06:03.000 --> 00:06:05.749 align:start position:0% synchronization a bit less proprietary<00:06:04.000> so<00:06:04.319> we<00:06:04.520> might<00:06:04.880> ask<00:06:05.120> ourselves 00:06:05.749 --> 00:06:05.759 align:start position:0% proprietary so we might ask ourselves 00:06:05.759 --> 00:06:07.510 align:start position:0% proprietary so we might ask ourselves what<00:06:05.880> is<00:06:06.000> a<00:06:06.120> syncable<00:06:06.599> credential<00:06:07.160> because<00:06:07.360> if 00:06:07.510 --> 00:06:07.520 align:start position:0% what is a syncable credential because if 00:06:07.520 --> 00:06:09.430 align:start position:0% what is a syncable credential because if we<00:06:07.720> search<00:06:08.000> for<00:06:08.240> this<00:06:08.360> in<00:06:08.479> the<00:06:08.680> documentation 00:06:09.430 --> 00:06:09.440 align:start position:0% we search for this in the documentation 00:06:09.440 --> 00:06:11.950 align:start position:0% we search for this in the documentation we<00:06:09.560> won't<00:06:09.919> find<00:06:10.280> any<00:06:10.520> reference<00:06:10.960> to<00:06:11.160> it<00:06:11.800> uh 00:06:11.950 --> 00:06:11.960 align:start position:0% we won't find any reference to it uh 00:06:11.960 --> 00:06:13.510 align:start position:0% we won't find any reference to it uh that's<00:06:12.160> because<00:06:12.400> the<00:06:12.560> proper<00:06:12.840> name<00:06:13.039> for<00:06:13.199> it<00:06:13.400> is 00:06:13.510 --> 00:06:13.520 align:start position:0% that's because the proper name for it is 00:06:13.520 --> 00:06:15.589 align:start position:0% that's because the proper name for it is Multi-Device<00:06:14.240> credential<00:06:15.000> so<00:06:15.199> that's<00:06:15.360> one 00:06:15.589 --> 00:06:15.599 align:start position:0% Multi-Device credential so that's one 00:06:15.599 --> 00:06:18.390 align:start position:0% Multi-Device credential so that's one thing<00:06:16.440> and<00:06:16.599> if<00:06:16.720> we<00:06:16.880> want<00:06:17.160> to<00:06:17.440> Define<00:06:17.800> it<00:06:18.000> we<00:06:18.160> can 00:06:18.390 --> 00:06:18.400 align:start position:0% thing and if we want to Define it we can 00:06:18.400 --> 00:06:20.909 align:start position:0% thing and if we want to Define it we can say<00:06:18.599> it's<00:06:18.720> a<00:06:19.240> discoverable<00:06:20.240> or<00:06:20.479> resident 00:06:20.909 --> 00:06:20.919 align:start position:0% say it's a discoverable or resident 00:06:20.919 --> 00:06:22.950 align:start position:0% say it's a discoverable or resident credential<00:06:21.520> in<00:06:21.599> the<00:06:21.759> context<00:06:22.080> of<00:06:22.160> a 00:06:22.950 --> 00:06:22.960 align:start position:0% credential in the context of a 00:06:22.960 --> 00:06:25.390 align:start position:0% credential in the context of a smartphone<00:06:23.960> but<00:06:24.120> the<00:06:24.319> only<00:06:24.639> way<00:06:24.800> to<00:06:24.960> know<00:06:25.160> if<00:06:25.240> a 00:06:25.390 --> 00:06:25.400 align:start position:0% smartphone but the only way to know if a 00:06:25.400 --> 00:06:28.710 align:start position:0% smartphone but the only way to know if a credential<00:06:25.960> is<00:06:26.240> really<00:06:27.199> um<00:06:27.400> thinkable<00:06:28.319> is<00:06:28.440> to 00:06:28.710 --> 00:06:28.720 align:start position:0% credential is really um thinkable is to 00:06:28.720 --> 00:06:30.189 align:start position:0% credential is really um thinkable is to look<00:06:28.919> at<00:06:29.080> the<00:06:29.199> answers<00:06:29.639> that<00:06:29.759> you<00:06:29.880> get<00:06:30.080> when 00:06:30.189 --> 00:06:30.199 align:start position:0% look at the answers that you get when 00:06:30.199 --> 00:06:32.350 align:start position:0% look at the answers that you get when you<00:06:30.400> register<00:06:30.880> it<00:06:31.400> uh<00:06:31.479> you<00:06:31.599> will<00:06:31.759> get<00:06:31.880> a<00:06:32.000> flag 00:06:32.350 --> 00:06:32.360 align:start position:0% you register it uh you will get a flag 00:06:32.360 --> 00:06:34.029 align:start position:0% you register it uh you will get a flag which<00:06:32.479> is<00:06:32.599> called<00:06:32.880> backup<00:06:33.240> eligibility<00:06:33.960> if 00:06:34.029 --> 00:06:34.039 align:start position:0% which is called backup eligibility if 00:06:34.039 --> 00:06:35.710 align:start position:0% which is called backup eligibility if it's<00:06:34.199> set<00:06:34.400> to<00:06:34.560> one<00:06:34.840> then<00:06:34.960> the<00:06:35.120> credential<00:06:35.599> can 00:06:35.710 --> 00:06:35.720 align:start position:0% it's set to one then the credential can 00:06:35.720 --> 00:06:37.870 align:start position:0% it's set to one then the credential can be<00:06:35.840> synced<00:06:36.400> so<00:06:36.560> it's<00:06:36.759> something<00:06:37.240> on<00:06:37.560> top<00:06:37.759> of 00:06:37.870 --> 00:06:37.880 align:start position:0% be synced so it's something on top of 00:06:37.880 --> 00:06:41.950 align:start position:0% be synced so it's something on top of the<00:06:38.039> spec<00:06:38.840> not<00:06:39.039> super<00:06:39.360> easy<00:06:39.639> to<00:06:40.039> to<00:06:40.360> to 00:06:41.950 --> 00:06:41.960 align:start position:0% the spec not super easy to to to 00:06:41.960 --> 00:06:45.390 align:start position:0% the spec not super easy to to to get<00:06:42.960> the<00:06:43.520> real<00:06:43.919> problem<00:06:44.240> starts<00:06:44.720> now<00:06:45.120> because 00:06:45.390 --> 00:06:45.400 align:start position:0% get the real problem starts now because 00:06:45.400 --> 00:06:47.230 align:start position:0% get the real problem starts now because we<00:06:45.599> have<00:06:45.759> several<00:06:46.120> security<00:06:46.560> misconceptions 00:06:47.230 --> 00:06:47.240 align:start position:0% we have several security misconceptions 00:06:47.240 --> 00:06:50.550 align:start position:0% we have several security misconceptions in<00:06:47.400> Pho<00:06:48.319> um<00:06:48.520> the<00:06:48.680> first<00:06:48.919> one<00:06:49.199> is<00:06:49.440> that<00:06:49.840> well<00:06:50.080> Pho 00:06:50.550 --> 00:06:50.560 align:start position:0% in Pho um the first one is that well Pho 00:06:50.560 --> 00:06:54.189 align:start position:0% in Pho um the first one is that well Pho protects<00:06:51.240> against<00:06:52.240> fishing<00:06:52.800> not<00:06:53.000> malware<00:06:54.000> so 00:06:54.189 --> 00:06:54.199 align:start position:0% protects against fishing not malware so 00:06:54.199 --> 00:06:56.150 align:start position:0% protects against fishing not malware so we<00:06:54.400> can't<00:06:54.759> really<00:06:55.039> expect<00:06:55.360> that<00:06:55.520> Pho<00:06:55.879> is<00:06:56.000> going 00:06:56.150 --> 00:06:56.160 align:start position:0% we can't really expect that Pho is going 00:06:56.160 --> 00:06:57.990 align:start position:0% we can't really expect that Pho is going to<00:06:56.240> be<00:06:56.400> good<00:06:56.520> to<00:06:56.680> protect<00:06:57.080> against<00:06:57.280> malware 00:06:57.990 --> 00:06:58.000 align:start position:0% to be good to protect against malware 00:06:58.000 --> 00:07:00.749 align:start position:0% to be good to protect against malware but<00:06:58.400> at<00:06:58.560> the<00:06:58.680> same<00:06:58.960> time<00:06:59.759> it<00:06:59.919> is<00:07:00.240> implemented 00:07:00.749 --> 00:07:00.759 align:start position:0% but at the same time it is implemented 00:07:00.759 --> 00:07:04.029 align:start position:0% but at the same time it is implemented on<00:07:00.919> secure<00:07:01.319> devices<00:07:02.199> so<00:07:02.520> we<00:07:02.680> have 00:07:04.029 --> 00:07:04.039 align:start position:0% on secure devices so we have 00:07:04.039 --> 00:07:06.830 align:start position:0% on secure devices so we have strong<00:07:05.039> uh<00:07:05.280> we<00:07:05.560> we<00:07:05.759> we<00:07:05.879> think<00:07:06.160> that<00:07:06.319> the<00:07:06.479> key<00:07:06.720> is 00:07:06.830 --> 00:07:06.840 align:start position:0% strong uh we we we think that the key is 00:07:06.840 --> 00:07:08.550 align:start position:0% strong uh we we we think that the key is going<00:07:07.000> to<00:07:07.120> be<00:07:07.360> strongly<00:07:07.720> protected<00:07:08.280> because 00:07:08.550 --> 00:07:08.560 align:start position:0% going to be strongly protected because 00:07:08.560 --> 00:07:11.309 align:start position:0% going to be strongly protected because this<00:07:08.680> is<00:07:08.800> the<00:07:08.960> way<00:07:09.160> that<00:07:09.319> Pho<00:07:09.680> was<00:07:10.319> defined 00:07:11.309 --> 00:07:11.319 align:start position:0% this is the way that Pho was defined 00:07:11.319 --> 00:07:13.309 align:start position:0% this is the way that Pho was defined then<00:07:11.560> we<00:07:11.680> can<00:07:11.919> ask<00:07:12.319> what<00:07:12.479> is<00:07:12.599> the<00:07:12.800> consequence 00:07:13.309 --> 00:07:13.319 align:start position:0% then we can ask what is the consequence 00:07:13.319 --> 00:07:16.710 align:start position:0% then we can ask what is the consequence of<00:07:13.520> introducing<00:07:14.479> thinkable<00:07:15.039> credentials<00:07:15.680> to 00:07:16.710 --> 00:07:16.720 align:start position:0% of introducing thinkable credentials to 00:07:16.720 --> 00:07:20.029 align:start position:0% of introducing thinkable credentials to this<00:07:17.720> and<00:07:18.440> to<00:07:18.680> get<00:07:18.840> even<00:07:19.120> worse<00:07:19.599> when<00:07:19.720> you<00:07:19.879> look 00:07:20.029 --> 00:07:20.039 align:start position:0% this and to get even worse when you look 00:07:20.039 --> 00:07:22.469 align:start position:0% this and to get even worse when you look at<00:07:20.160> the<00:07:20.319> implementation<00:07:20.919> on<00:07:21.120> Pho<00:07:21.879> by<00:07:22.080> crypto 00:07:22.469 --> 00:07:22.479 align:start position:0% at the implementation on Pho by crypto 00:07:22.479 --> 00:07:25.830 align:start position:0% at the implementation on Pho by crypto people<00:07:23.319> um<00:07:23.879> we<00:07:24.160> abuse<00:07:24.520> it<00:07:24.919> routinely<00:07:25.560> because 00:07:25.830 --> 00:07:25.840 align:start position:0% people um we abuse it routinely because 00:07:25.840 --> 00:07:28.150 align:start position:0% people um we abuse it routinely because Pho<00:07:26.280> is<00:07:26.520> only<00:07:26.840> designed<00:07:27.199> for<00:07:27.360> authentication 00:07:28.150 --> 00:07:28.160 align:start position:0% Pho is only designed for authentication 00:07:28.160 --> 00:07:29.909 align:start position:0% Pho is only designed for authentication when<00:07:28.280> you<00:07:28.400> use<00:07:28.560> it<00:07:28.680> to<00:07:28.840> sign<00:07:29.120> transaction<00:07:29.800> we 00:07:29.909 --> 00:07:29.919 align:start position:0% when you use it to sign transaction we 00:07:29.919 --> 00:07:32.390 align:start position:0% when you use it to sign transaction we can't<00:07:30.199> really<00:07:30.440> verify<00:07:30.919> what<00:07:31.039> we<00:07:31.120> are<00:07:31.400> signing 00:07:32.390 --> 00:07:32.400 align:start position:0% can't really verify what we are signing 00:07:32.400 --> 00:07:34.830 align:start position:0% can't really verify what we are signing and<00:07:32.720> if<00:07:32.840> we<00:07:32.960> lose<00:07:33.160> a<00:07:33.400> key<00:07:33.879> the<00:07:34.039> impact<00:07:34.360> is<00:07:34.520> going 00:07:34.830 --> 00:07:34.840 align:start position:0% and if we lose a key the impact is going 00:07:34.840 --> 00:07:36.790 align:start position:0% and if we lose a key the impact is going much<00:07:35.000> more<00:07:35.240> important<00:07:35.720> for<00:07:35.960> crypto<00:07:36.440> than<00:07:36.639> it 00:07:36.790 --> 00:07:36.800 align:start position:0% much more important for crypto than it 00:07:36.800 --> 00:07:38.710 align:start position:0% much more important for crypto than it is<00:07:37.000> for<00:07:37.319> authentication<00:07:38.160> because<00:07:38.360> you<00:07:38.479> can 00:07:38.710 --> 00:07:38.720 align:start position:0% is for authentication because you can 00:07:38.720 --> 00:07:40.909 align:start position:0% is for authentication because you can always<00:07:39.080> revoke<00:07:39.440> an<00:07:39.599> account<00:07:40.120> and<00:07:40.319> you<00:07:40.520> can't 00:07:40.909 --> 00:07:40.919 align:start position:0% always revoke an account and you can't 00:07:40.919 --> 00:07:44.309 align:start position:0% always revoke an account and you can't revoke<00:07:41.440> a<00:07:41.599> transaction<00:07:42.120> on<00:07:42.280> the 00:07:44.309 --> 00:07:44.319 align:start position:0% revoke a transaction on the 00:07:44.319 --> 00:07:46.670 align:start position:0% revoke a transaction on the blockchain<00:07:45.319> then<00:07:45.560> Pho<00:07:45.960> is<00:07:46.080> designed<00:07:46.400> to<00:07:46.520> be 00:07:46.670 --> 00:07:46.680 align:start position:0% blockchain then Pho is designed to be 00:07:46.680 --> 00:07:49.430 align:start position:0% blockchain then Pho is designed to be bound<00:07:47.080> by<00:07:47.199> the<00:07:47.360> web<00:07:47.840> origin<00:07:48.840> if<00:07:49.000> we<00:07:49.120> want<00:07:49.280> to 00:07:49.430 --> 00:07:49.440 align:start position:0% bound by the web origin if we want to 00:07:49.440 --> 00:07:51.029 align:start position:0% bound by the web origin if we want to build<00:07:49.639> a<00:07:49.800> common<00:07:50.080> web<00:07:50.280> wallet<00:07:50.639> we<00:07:50.720> are<00:07:50.879> going 00:07:51.029 --> 00:07:51.039 align:start position:0% build a common web wallet we are going 00:07:51.039 --> 00:07:53.309 align:start position:0% build a common web wallet we are going to<00:07:51.159> break<00:07:51.440> this<00:07:51.639> property<00:07:52.080> by<00:07:52.280> Design<00:07:53.000> so<00:07:53.199> we 00:07:53.309 --> 00:07:53.319 align:start position:0% to break this property by Design so we 00:07:53.319 --> 00:07:55.070 align:start position:0% to break this property by Design so we have<00:07:53.479> to<00:07:53.680> hack<00:07:53.879> around<00:07:54.199> it<00:07:54.360> but<00:07:54.479> it's<00:07:54.599> a<00:07:54.800> hack 00:07:55.070 --> 00:07:55.080 align:start position:0% have to hack around it but it's a hack 00:07:55.080 --> 00:07:57.510 align:start position:0% have to hack around it but it's a hack around<00:07:55.360> the<00:07:55.680> specification<00:07:56.680> and<00:07:56.879> just<00:07:57.039> to<00:07:57.280> say 00:07:57.510 --> 00:07:57.520 align:start position:0% around the specification and just to say 00:07:57.520 --> 00:07:59.029 align:start position:0% around the specification and just to say that<00:07:57.680> we<00:07:57.800> have<00:07:57.960> been<00:07:58.120> abusing<00:07:58.520> this<00:07:58.680> protocol 00:07:59.029 --> 00:07:59.039 align:start position:0% that we have been abusing this protocol 00:07:59.039 --> 00:08:00.909 align:start position:0% that we have been abusing this protocol for<00:07:59.120> a<00:07:59.199> long<00:07:59.639> time<00:07:59.840> I'm<00:08:00.000> not<00:08:00.199> specially<00:08:00.680> proud 00:08:00.909 --> 00:08:00.919 align:start position:0% for a long time I'm not specially proud 00:08:00.919 --> 00:08:03.830 align:start position:0% for a long time I'm not specially proud of<00:08:01.080> it<00:08:01.240> but<00:08:01.400> just<00:08:01.599> mentioning<00:08:02.120> it<00:08:02.840> I<00:08:02.960> used<00:08:03.280> youf 00:08:03.830 --> 00:08:03.840 align:start position:0% of it but just mentioning it I used youf 00:08:03.840 --> 00:08:05.350 align:start position:0% of it but just mentioning it I used youf to<00:08:04.000> communicate<00:08:04.599> between<00:08:04.840> Ledger<00:08:05.199> and 00:08:05.350 --> 00:08:05.360 align:start position:0% to communicate between Ledger and 00:08:05.360 --> 00:08:08.869 align:start position:0% to communicate between Ledger and metamask<00:08:06.159> and<00:08:06.319> sorry<00:08:06.720> and<00:08:06.919> my<00:08:07.360> wallet<00:08:07.800> in<00:08:07.960> 2016 00:08:08.869 --> 00:08:08.879 align:start position:0% metamask and sorry and my wallet in 2016 00:08:08.879 --> 00:08:10.469 align:start position:0% metamask and sorry and my wallet in 2016 because<00:08:09.120> there<00:08:09.240> was<00:08:09.400> no<00:08:09.599> way<00:08:09.759> to<00:08:09.919> communicate 00:08:10.469 --> 00:08:10.479 align:start position:0% because there was no way to communicate 00:08:10.479 --> 00:08:12.950 align:start position:0% because there was no way to communicate because<00:08:10.680> a<00:08:10.840> browser<00:08:11.400> between<00:08:12.199> a<00:08:12.360> browser<00:08:12.840> and 00:08:12.950 --> 00:08:12.960 align:start position:0% because a browser between a browser and 00:08:12.960 --> 00:08:16.670 align:start position:0% because a browser between a browser and a<00:08:13.120> USB<00:08:13.560> device<00:08:14.199> so<00:08:15.199> it<00:08:15.599> was<00:08:15.759> used<00:08:16.000> as<00:08:16.120> a<00:08:16.240> tunnel 00:08:16.670 --> 00:08:16.680 align:start position:0% a USB device so it was used as a tunnel 00:08:16.680 --> 00:08:17.990 align:start position:0% a USB device so it was used as a tunnel at<00:08:16.840> that 00:08:17.990 --> 00:08:18.000 align:start position:0% at that 00:08:18.000 --> 00:08:21.189 align:start position:0% at that time<00:08:19.000> short<00:08:19.319> break<00:08:19.759> maybe<00:08:20.360> why<00:08:20.720> secure 00:08:21.189 --> 00:08:21.199 align:start position:0% time short break maybe why secure 00:08:21.199 --> 00:08:23.469 align:start position:0% time short break maybe why secure Hardware<00:08:21.560> is<00:08:21.720> important<00:08:22.680> secure<00:08:23.039> Hardware<00:08:23.319> is 00:08:23.469 --> 00:08:23.479 align:start position:0% Hardware is important secure Hardware is 00:08:23.479 --> 00:08:25.790 align:start position:0% Hardware is important secure Hardware is important<00:08:24.120> because<00:08:24.560> it<00:08:24.680> will<00:08:25.000> protect<00:08:25.599> the 00:08:25.790 --> 00:08:25.800 align:start position:0% important because it will protect the 00:08:25.800 --> 00:08:28.149 align:start position:0% important because it will protect the key<00:08:26.080> against<00:08:26.360> malware<00:08:27.240> any<00:08:27.479> hardware<00:08:27.879> does 00:08:28.149 --> 00:08:28.159 align:start position:0% key against malware any hardware does 00:08:28.159 --> 00:08:30.029 align:start position:0% key against malware any hardware does that<00:08:28.479> but<00:08:28.639> secure<00:08:29.000> Hardware<00:08:29.280> is<00:08:29.560> supposed<00:08:29.879> to 00:08:30.029 --> 00:08:30.039 align:start position:0% that but secure Hardware is supposed to 00:08:30.039 --> 00:08:31.110 align:start position:0% that but secure Hardware is supposed to do<00:08:30.159> it 00:08:31.110 --> 00:08:31.120 align:start position:0% do it 00:08:31.120 --> 00:08:33.230 align:start position:0% do it better<00:08:32.120> then<00:08:32.279> it<00:08:32.399> will<00:08:32.599> protect<00:08:32.880> the<00:08:33.039> key 00:08:33.230 --> 00:08:33.240 align:start position:0% better then it will protect the key 00:08:33.240 --> 00:08:35.350 align:start position:0% better then it will protect the key against<00:08:33.519> physical<00:08:33.919> attacks<00:08:34.919> physical 00:08:35.350 --> 00:08:35.360 align:start position:0% against physical attacks physical 00:08:35.360 --> 00:08:38.190 align:start position:0% against physical attacks physical attacks<00:08:35.760> are<00:08:35.959> the<00:08:36.120> last<00:08:36.360> line<00:08:36.640> of<00:08:37.039> of<00:08:37.200> Defense 00:08:38.190 --> 00:08:38.200 align:start position:0% attacks are the last line of of Defense 00:08:38.200 --> 00:08:40.389 align:start position:0% attacks are the last line of of Defense when<00:08:38.479> an<00:08:38.680> attacker<00:08:39.080> has<00:08:39.320> access<00:08:39.560> to<00:08:39.719> a<00:08:39.919> device 00:08:40.389 --> 00:08:40.399 align:start position:0% when an attacker has access to a device 00:08:40.399 --> 00:08:42.949 align:start position:0% when an attacker has access to a device you<00:08:40.719> always<00:08:41.200> think<00:08:41.560> that<00:08:41.719> your<00:08:41.959> key<00:08:42.159> is<00:08:42.279> lost 00:08:42.949 --> 00:08:42.959 align:start position:0% you always think that your key is lost 00:08:42.959 --> 00:08:45.070 align:start position:0% you always think that your key is lost SEC<00:08:43.599> is<00:08:43.680> supposed<00:08:44.000> to<00:08:44.120> protect<00:08:44.399> you<00:08:44.600> against 00:08:45.070 --> 00:08:45.080 align:start position:0% SEC is supposed to protect you against 00:08:45.080 --> 00:08:48.389 align:start position:0% SEC is supposed to protect you against this<00:08:46.080> but<00:08:46.399> even<00:08:46.680> more<00:08:46.959> importantly<00:08:47.959> secure 00:08:48.389 --> 00:08:48.399 align:start position:0% this but even more importantly secure 00:08:48.399 --> 00:08:50.190 align:start position:0% this but even more importantly secure Hardware<00:08:48.800> will<00:08:49.000> protect<00:08:49.360> you<00:08:49.720> against 00:08:50.190 --> 00:08:50.200 align:start position:0% Hardware will protect you against 00:08:50.200 --> 00:08:52.829 align:start position:0% Hardware will protect you against passive<00:08:50.560> attacks<00:08:51.080> passive<00:08:51.440> attacks<00:08:51.880> meaning 00:08:52.829 --> 00:08:52.839 align:start position:0% passive attacks passive attacks meaning 00:08:52.839 --> 00:08:55.230 align:start position:0% passive attacks passive attacks meaning trying<00:08:53.240> to<00:08:53.560> obtain<00:08:53.920> the<00:08:54.080> key<00:08:54.440> by<00:08:54.640> listening<00:08:55.040> to 00:08:55.230 --> 00:08:55.240 align:start position:0% trying to obtain the key by listening to 00:08:55.240 --> 00:08:56.949 align:start position:0% trying to obtain the key by listening to what<00:08:55.360> the<00:08:55.480> ship<00:08:55.720> is<00:08:55.880> doing<00:08:56.279> by<00:08:56.440> listening<00:08:56.760> to 00:08:56.949 --> 00:08:56.959 align:start position:0% what the ship is doing by listening to 00:08:56.959 --> 00:08:59.630 align:start position:0% what the ship is doing by listening to electromagnetic<00:08:58.120> radiation<00:08:59.120> power 00:08:59.630 --> 00:08:59.640 align:start position:0% electromagnetic radiation power 00:08:59.640 --> 00:09:02.550 align:start position:0% electromagnetic radiation power differences<00:09:00.279> that<00:09:00.440> kind<00:09:00.600> of<00:09:01.160> thing<00:09:02.160> and<00:09:02.360> the 00:09:02.550 --> 00:09:02.560 align:start position:0% differences that kind of thing and the 00:09:02.560 --> 00:09:04.630 align:start position:0% differences that kind of thing and the only<00:09:02.880> way<00:09:03.079> to<00:09:03.360> really<00:09:03.640> protect<00:09:04.000> against<00:09:04.320> this 00:09:04.630 --> 00:09:04.640 align:start position:0% only way to really protect against this 00:09:04.640 --> 00:09:06.710 align:start position:0% only way to really protect against this is<00:09:04.800> by<00:09:04.959> using<00:09:05.279> dedicated<00:09:05.800> Hardware<00:09:06.360> because 00:09:06.710 --> 00:09:06.720 align:start position:0% is by using dedicated Hardware because 00:09:06.720 --> 00:09:08.430 align:start position:0% is by using dedicated Hardware because even<00:09:06.959> if<00:09:07.079> you<00:09:07.200> use<00:09:07.560> the<00:09:07.680> best<00:09:07.920> open<00:09:08.160> source 00:09:08.430 --> 00:09:08.440 align:start position:0% even if you use the best open source 00:09:08.440 --> 00:09:11.230 align:start position:0% even if you use the best open source Library<00:09:09.440> like<00:09:09.680> lipc<00:09:10.240> P 00:09:11.230 --> 00:09:11.240 align:start position:0% Library like lipc P 00:09:11.240 --> 00:09:15.150 align:start position:0% Library like lipc P 2666<00:09:12.240> K1<00:09:12.920> here<00:09:13.720> um<00:09:14.160> it<00:09:14.519> needs<00:09:14.839> to<00:09:14.959> be 00:09:15.150 --> 00:09:15.160 align:start position:0% 2666 K1 here um it needs to be 00:09:15.160 --> 00:09:17.230 align:start position:0% 2666 K1 here um it needs to be customized<00:09:15.760> to<00:09:15.880> your<00:09:16.079> chip<00:09:16.360> to<00:09:16.519> avoid<00:09:16.800> leaking 00:09:17.230 --> 00:09:17.240 align:start position:0% customized to your chip to avoid leaking 00:09:17.240 --> 00:09:19.190 align:start position:0% customized to your chip to avoid leaking information<00:09:17.920> so<00:09:18.079> if<00:09:18.200> you're<00:09:18.440> not<00:09:18.839> working 00:09:19.190 --> 00:09:19.200 align:start position:0% information so if you're not working 00:09:19.200 --> 00:09:20.590 align:start position:0% information so if you're not working with<00:09:19.360> secure<00:09:19.720> Hardware<00:09:20.079> you're<00:09:20.279> going<00:09:20.440> to 00:09:20.590 --> 00:09:20.600 align:start position:0% with secure Hardware you're going to 00:09:20.600 --> 00:09:22.990 align:start position:0% with secure Hardware you're going to have<00:09:20.839> problems<00:09:21.640> that's<00:09:21.959> basically<00:09:22.640> you<00:09:22.760> are 00:09:22.990 --> 00:09:23.000 align:start position:0% have problems that's basically you are 00:09:23.000 --> 00:09:26.150 align:start position:0% have problems that's basically you are just<00:09:23.240> one<00:09:23.720> speculation<00:09:24.760> speculative<00:09:25.760> leak 00:09:26.150 --> 00:09:26.160 align:start position:0% just one speculation speculative leak 00:09:26.160 --> 00:09:30.230 align:start position:0% just one speculation speculative leak away<00:09:27.000> from<00:09:27.200> losing<00:09:27.519> the<00:09:27.680> key<00:09:27.920> for<00:09:28.079> example 00:09:30.230 --> 00:09:30.240 align:start position:0% away from losing the key for example 00:09:30.240 --> 00:09:33.069 align:start position:0% away from losing the key for example so<00:09:30.720> what<00:09:30.920> is<00:09:31.320> phyo<00:09:31.800> security<00:09:32.279> model<00:09:32.600> for<00:09:32.800> non 00:09:33.069 --> 00:09:33.079 align:start position:0% so what is phyo security model for non 00:09:33.079 --> 00:09:33.990 align:start position:0% so what is phyo security model for non seekable 00:09:33.990 --> 00:09:34.000 align:start position:0% seekable 00:09:34.000 --> 00:09:37.190 align:start position:0% seekable credentials<00:09:35.000> they<00:09:35.160> cannot<00:09:35.560> be<00:09:36.560> extracted<00:09:37.040> by 00:09:37.190 --> 00:09:37.200 align:start position:0% credentials they cannot be extracted by 00:09:37.200 --> 00:09:39.350 align:start position:0% credentials they cannot be extracted by malware<00:09:37.800> this<00:09:37.920> is<00:09:38.079> very<00:09:38.320> important<00:09:39.200> the 00:09:39.350 --> 00:09:39.360 align:start position:0% malware this is very important the 00:09:39.360 --> 00:09:41.069 align:start position:0% malware this is very important the authentication<00:09:40.040> is<00:09:40.279> always<00:09:40.600> done<00:09:40.839> at<00:09:40.959> The 00:09:41.069 --> 00:09:41.079 align:start position:0% authentication is always done at The 00:09:41.079 --> 00:09:43.470 align:start position:0% authentication is always done at The Enclave<00:09:41.560> level<00:09:41.880> The<00:09:41.959> Enclave<00:09:42.480> is<00:09:42.720> basically 00:09:43.470 --> 00:09:43.480 align:start position:0% Enclave level The Enclave is basically 00:09:43.480 --> 00:09:45.630 align:start position:0% Enclave level The Enclave is basically in<00:09:43.720> charge<00:09:44.160> it's<00:09:44.320> holding<00:09:44.640> the<00:09:44.839> key<00:09:45.399> it's 00:09:45.630 --> 00:09:45.640 align:start position:0% in charge it's holding the key it's 00:09:45.640 --> 00:09:49.150 align:start position:0% in charge it's holding the key it's doing<00:09:45.959> the<00:09:46.440> authentication<00:09:47.440> if<00:09:47.600> you<00:09:47.800> want<00:09:48.560> to 00:09:49.150 --> 00:09:49.160 align:start position:0% doing the authentication if you want to 00:09:49.160 --> 00:09:50.670 align:start position:0% doing the authentication if you want to do<00:09:49.399> something<00:09:49.720> with<00:09:49.880> the<00:09:50.000> Enclave<00:09:50.480> you<00:09:50.560> have 00:09:50.670 --> 00:09:50.680 align:start position:0% do something with the Enclave you have 00:09:50.680 --> 00:09:52.949 align:start position:0% do something with the Enclave you have to<00:09:50.800> authenticate<00:09:51.399> this<00:09:51.560> cannot<00:09:51.800> be<00:09:51.959> bypassed 00:09:52.949 --> 00:09:52.959 align:start position:0% to authenticate this cannot be bypassed 00:09:52.959 --> 00:09:55.750 align:start position:0% to authenticate this cannot be bypassed so<00:09:53.160> the<00:09:53.360> malware<00:09:53.760> cannot<00:09:54.600> a<00:09:54.800> very<00:09:55.560> strong 00:09:55.750 --> 00:09:55.760 align:start position:0% so the malware cannot a very strong 00:09:55.760 --> 00:09:58.030 align:start position:0% so the malware cannot a very strong malware<00:09:56.279> that<00:09:56.440> manage<00:09:56.800> to<00:09:57.120> modify<00:09:57.560> the<00:09:57.720> canel 00:09:58.030 --> 00:09:58.040 align:start position:0% malware that manage to modify the canel 00:09:58.040 --> 00:10:00.110 align:start position:0% malware that manage to modify the canel of<00:09:58.160> the<00:09:58.360> device<00:09:58.720> can<00:09:58.880> fully<00:09:59.440> into<00:09:59.640> signing 00:10:00.110 --> 00:10:00.120 align:start position:0% of the device can fully into signing 00:10:00.120 --> 00:10:02.350 align:start position:0% of the device can fully into signing something<00:10:01.120> but<00:10:01.240> it<00:10:01.360> would<00:10:01.560> have<00:10:01.680> to<00:10:01.880> do<00:10:02.040> it 00:10:02.350 --> 00:10:02.360 align:start position:0% something but it would have to do it 00:10:02.360 --> 00:10:04.910 align:start position:0% something but it would have to do it every<00:10:02.640> time<00:10:02.920> and<00:10:03.079> it<00:10:03.200> can't<00:10:03.440> do<00:10:03.600> anything 00:10:04.910 --> 00:10:04.920 align:start position:0% every time and it can't do anything 00:10:04.920 --> 00:10:07.509 align:start position:0% every time and it can't do anything else<00:10:05.920> now<00:10:06.120> let's<00:10:06.360> think<00:10:06.640> about<00:10:07.360> some 00:10:07.509 --> 00:10:07.519 align:start position:0% else now let's think about some 00:10:07.519 --> 00:10:09.790 align:start position:0% else now let's think about some hypothesis<00:10:08.079> for<00:10:08.240> the<00:10:08.600> synchronization<00:10:09.600> the 00:10:09.790 --> 00:10:09.800 align:start position:0% hypothesis for the synchronization the 00:10:09.800 --> 00:10:11.990 align:start position:0% hypothesis for the synchronization the first<00:10:10.079> one<00:10:10.320> would<00:10:10.519> be<00:10:10.720> the<00:10:10.880> good<00:10:11.120> hypothesis 00:10:11.990 --> 00:10:12.000 align:start position:0% first one would be the good hypothesis 00:10:12.000 --> 00:10:14.550 align:start position:0% first one would be the good hypothesis in<00:10:12.200> that<00:10:12.480> case<00:10:12.800> we<00:10:12.920> think<00:10:13.800> we<00:10:13.959> imagine<00:10:14.399> that 00:10:14.550 --> 00:10:14.560 align:start position:0% in that case we think we imagine that 00:10:14.560 --> 00:10:16.110 align:start position:0% in that case we think we imagine that there<00:10:14.680> is<00:10:14.800> a<00:10:14.959> Hardware<00:10:15.360> security<00:10:15.760> module 00:10:16.110 --> 00:10:16.120 align:start position:0% there is a Hardware security module 00:10:16.120 --> 00:10:18.230 align:start position:0% there is a Hardware security module sitting<00:10:16.480> at<00:10:16.680> Google<00:10:16.959> and<00:10:17.120> apple<00:10:17.880> and<00:10:18.040> this 00:10:18.230 --> 00:10:18.240 align:start position:0% sitting at Google and apple and this 00:10:18.240 --> 00:10:20.310 align:start position:0% sitting at Google and apple and this Hardware<00:10:18.640> security<00:10:19.040> module<00:10:19.399> is<00:10:19.560> doing<00:10:20.160> a 00:10:20.310 --> 00:10:20.320 align:start position:0% Hardware security module is doing a 00:10:20.320 --> 00:10:22.030 align:start position:0% Hardware security module is doing a synchronization<00:10:21.120> protocol<00:10:21.600> between<00:10:21.880> two 00:10:22.030 --> 00:10:22.040 align:start position:0% synchronization protocol between two 00:10:22.040 --> 00:10:24.949 align:start position:0% synchronization protocol between two enclaves<00:10:22.959> in<00:10:23.120> that<00:10:23.440> case<00:10:23.760> the<00:10:24.079> security<00:10:24.600> model 00:10:24.949 --> 00:10:24.959 align:start position:0% enclaves in that case the security model 00:10:24.959 --> 00:10:26.990 align:start position:0% enclaves in that case the security model doesn't<00:10:25.279> change<00:10:25.880> the<00:10:26.079> credential<00:10:26.600> is<00:10:26.720> never 00:10:26.990 --> 00:10:27.000 align:start position:0% doesn't change the credential is never 00:10:27.000 --> 00:10:29.069 align:start position:0% doesn't change the credential is never exposed<00:10:27.560> everything<00:10:27.920> is<00:10:28.120> good<00:10:28.720> at<00:10:28.839> least<00:10:28.959> it 00:10:29.069 --> 00:10:29.079 align:start position:0% exposed everything is good at least it 00:10:29.079 --> 00:10:31.990 align:start position:0% exposed everything is good at least it doesn't<00:10:29.600> change<00:10:30.600> uh<00:10:30.800> now<00:10:31.000> the<00:10:31.240> bad 00:10:31.990 --> 00:10:32.000 align:start position:0% doesn't change uh now the bad 00:10:32.000 --> 00:10:34.670 align:start position:0% doesn't change uh now the bad synchronization<00:10:32.800> hypothesis<00:10:33.600> in<00:10:33.800> that<00:10:34.040> case 00:10:34.670 --> 00:10:34.680 align:start position:0% synchronization hypothesis in that case 00:10:34.680 --> 00:10:36.829 align:start position:0% synchronization hypothesis in that case the<00:10:34.920> key<00:10:35.120> is<00:10:35.320> still<00:10:35.600> owned<00:10:35.959> by<00:10:36.079> The<00:10:36.200> Enclave 00:10:36.829 --> 00:10:36.839 align:start position:0% the key is still owned by The Enclave 00:10:36.839 --> 00:10:38.509 align:start position:0% the key is still owned by The Enclave but<00:10:36.959> you<00:10:37.079> have<00:10:37.200> a<00:10:37.360> way<00:10:37.560> to<00:10:37.760> put<00:10:37.920> it<00:10:38.079> into<00:10:38.360> the 00:10:38.509 --> 00:10:38.519 align:start position:0% but you have a way to put it into the 00:10:38.519 --> 00:10:40.310 align:start position:0% but you have a way to put it into the application<00:10:39.040> processor<00:10:39.560> to<00:10:39.720> start<00:10:40.040> the 00:10:40.310 --> 00:10:40.320 align:start position:0% application processor to start the 00:10:40.320 --> 00:10:43.110 align:start position:0% application processor to start the synchronization<00:10:41.200> mechanism<00:10:42.200> in<00:10:42.399> that<00:10:42.680> case<00:10:43.000> a 00:10:43.110 --> 00:10:43.120 align:start position:0% synchronization mechanism in that case a 00:10:43.120 --> 00:10:45.310 align:start position:0% synchronization mechanism in that case a malware<00:10:43.680> could<00:10:43.880> be<00:10:44.000> able<00:10:44.279> to<00:10:44.480> extract<00:10:44.839> the<00:10:45.000> key 00:10:45.310 --> 00:10:45.320 align:start position:0% malware could be able to extract the key 00:10:45.320 --> 00:10:47.870 align:start position:0% malware could be able to extract the key but<00:10:45.680> after<00:10:46.360> prompting<00:10:46.880> The<00:10:47.000> Enclave<00:10:47.480> to<00:10:47.639> start 00:10:47.870 --> 00:10:47.880 align:start position:0% but after prompting The Enclave to start 00:10:47.880 --> 00:10:49.990 align:start position:0% but after prompting The Enclave to start the<00:10:48.000> synchronization 00:10:49.990 --> 00:10:50.000 align:start position:0% the synchronization 00:10:50.000 --> 00:10:53.470 align:start position:0% the synchronization protocol<00:10:51.000> and<00:10:51.279> finally<00:10:52.200> uh<00:10:52.399> the<00:10:52.680> ugly 00:10:53.470 --> 00:10:53.480 align:start position:0% protocol and finally uh the ugly 00:10:53.480 --> 00:10:55.750 align:start position:0% protocol and finally uh the ugly synchronization<00:10:54.440> hypothesis<00:10:55.440> where<00:10:55.639> The 00:10:55.750 --> 00:10:55.760 align:start position:0% synchronization hypothesis where The 00:10:55.760 --> 00:10:58.430 align:start position:0% synchronization hypothesis where The Enclave<00:10:56.519> might<00:10:56.800> not<00:10:57.000> even<00:10:57.240> be<00:10:57.360> used<00:10:57.680> anymore 00:10:58.430 --> 00:10:58.440 align:start position:0% Enclave might not even be used anymore 00:10:58.440 --> 00:11:00.470 align:start position:0% Enclave might not even be used anymore the<00:10:58.600> keys<00:10:58.880> in<00:10:59.000> the<00:10:59.279> application<00:10:59.760> processor 00:11:00.470 --> 00:11:00.480 align:start position:0% the keys in the application processor 00:11:00.480 --> 00:11:02.910 align:start position:0% the keys in the application processor everything<00:11:01.480> is<00:11:01.600> in<00:11:01.760> the<00:11:01.959> clear<00:11:02.480> and<00:11:02.639> then<00:11:02.800> a 00:11:02.910 --> 00:11:02.920 align:start position:0% everything is in the clear and then a 00:11:02.920 --> 00:11:05.069 align:start position:0% everything is in the clear and then a malware<00:11:03.440> could<00:11:03.600> be<00:11:03.720> able<00:11:03.959> to<00:11:04.120> extract<00:11:04.480> the<00:11:04.639> key 00:11:05.069 --> 00:11:05.079 align:start position:0% malware could be able to extract the key 00:11:05.079 --> 00:11:06.670 align:start position:0% malware could be able to extract the key and<00:11:05.200> the<00:11:05.320> malware<00:11:05.800> doesn't<00:11:06.079> need<00:11:06.240> to<00:11:06.360> be<00:11:06.519> as 00:11:06.670 --> 00:11:06.680 align:start position:0% and the malware doesn't need to be as 00:11:06.680 --> 00:11:09.670 align:start position:0% and the malware doesn't need to be as sophisticated<00:11:07.480> as<00:11:07.600> in<00:11:07.720> the<00:11:07.880> previous<00:11:08.680> cases 00:11:09.670 --> 00:11:09.680 align:start position:0% sophisticated as in the previous cases 00:11:09.680 --> 00:11:12.350 align:start position:0% sophisticated as in the previous cases and<00:11:09.839> unfortunately<00:11:10.639> the<00:11:10.800> only<00:11:11.120> way<00:11:11.320> to<00:11:11.519> know 00:11:12.350 --> 00:11:12.360 align:start position:0% and unfortunately the only way to know 00:11:12.360 --> 00:11:14.430 align:start position:0% and unfortunately the only way to know uh<00:11:12.680> what<00:11:12.839> the<00:11:13.040> implementation<00:11:13.880> is<00:11:14.120> is<00:11:14.240> to 00:11:14.430 --> 00:11:14.440 align:start position:0% uh what the implementation is is to 00:11:14.440 --> 00:11:17.550 align:start position:0% uh what the implementation is is to reverse<00:11:14.880> it<00:11:15.480> so<00:11:15.680> we<00:11:15.760> are<00:11:15.920> going<00:11:16.079> to<00:11:16.240> do<00:11:16.519> this<00:11:17.360> uh 00:11:17.550 --> 00:11:17.560 align:start position:0% reverse it so we are going to do this uh 00:11:17.560 --> 00:11:20.949 align:start position:0% reverse it so we are going to do this uh first<00:11:17.839> on<00:11:18.320> iOS<00:11:19.320> so<00:11:19.639> iOS<00:11:20.120> to<00:11:20.279> do<00:11:20.480> this<00:11:20.680> we<00:11:20.800> need 00:11:20.949 --> 00:11:20.959 align:start position:0% first on iOS so iOS to do this we need 00:11:20.959 --> 00:11:23.629 align:start position:0% first on iOS so iOS to do this we need to<00:11:21.160> act<00:11:21.360> as<00:11:21.440> a<00:11:21.560> malware<00:11:22.519> iOS<00:11:22.920> is<00:11:23.040> a<00:11:23.160> bit 00:11:23.629 --> 00:11:23.639 align:start position:0% to act as a malware iOS is a bit 00:11:23.639 --> 00:11:25.470 align:start position:0% to act as a malware iOS is a bit difficult<00:11:23.760> to<00:11:23.920> jailbreak<00:11:24.680> as<00:11:24.800> you<00:11:24.920> know<00:11:25.160> so<00:11:25.360> I 00:11:25.470 --> 00:11:25.480 align:start position:0% difficult to jailbreak as you know so I 00:11:25.480 --> 00:11:27.310 align:start position:0% difficult to jailbreak as you know so I made<00:11:25.600> a<00:11:25.760> reference<00:11:26.160> to<00:11:26.360> a<00:11:26.480> recent<00:11:26.800> jailbreak 00:11:27.310 --> 00:11:27.320 align:start position:0% made a reference to a recent jailbreak 00:11:27.320 --> 00:11:29.750 align:start position:0% made a reference to a recent jailbreak to<00:11:27.560> show<00:11:27.800> you<00:11:28.079> how<00:11:28.320> complex<00:11:28.760> this<00:11:28.920> is 00:11:29.750 --> 00:11:29.760 align:start position:0% to show you how complex this is 00:11:29.760 --> 00:11:31.870 align:start position:0% to show you how complex this is uh<00:11:29.920> but<00:11:30.079> since<00:11:30.320> we<00:11:30.440> can<00:11:30.639> synchronize<00:11:31.600> uh<00:11:31.760> we 00:11:31.870 --> 00:11:31.880 align:start position:0% uh but since we can synchronize uh we 00:11:31.880 --> 00:11:34.190 align:start position:0% uh but since we can synchronize uh we can<00:11:32.200> jailbreak<00:11:32.720> an<00:11:32.880> older<00:11:33.279> iOS<00:11:33.720> device<00:11:34.040> and 00:11:34.190 --> 00:11:34.200 align:start position:0% can jailbreak an older iOS device and 00:11:34.200 --> 00:11:36.710 align:start position:0% can jailbreak an older iOS device and see<00:11:34.440> what<00:11:34.920> happens<00:11:35.920> so<00:11:36.120> for<00:11:36.360> that<00:11:36.519> we<00:11:36.600> are 00:11:36.710 --> 00:11:36.720 align:start position:0% see what happens so for that we are 00:11:36.720 --> 00:11:39.069 align:start position:0% see what happens so for that we are going<00:11:36.920> to<00:11:37.040> use<00:11:37.320> the<00:11:37.480> Checkmate<00:11:38.079> bug<00:11:38.760> uh<00:11:38.920> which 00:11:39.069 --> 00:11:39.079 align:start position:0% going to use the Checkmate bug uh which 00:11:39.079 --> 00:11:41.750 align:start position:0% going to use the Checkmate bug uh which is<00:11:39.440> quite<00:11:39.760> powerful<00:11:40.279> and<00:11:40.440> allow<00:11:40.800> us<00:11:40.959> to<00:11:41.120> break 00:11:41.750 --> 00:11:41.760 align:start position:0% is quite powerful and allow us to break 00:11:41.760 --> 00:11:44.310 align:start position:0% is quite powerful and allow us to break to<00:11:41.959> jailbreak<00:11:42.480> a<00:11:42.600> lot<00:11:42.760> of<00:11:42.880> older<00:11:43.320> iPhones<00:11:44.240> I 00:11:44.310 --> 00:11:44.320 align:start position:0% to jailbreak a lot of older iPhones I 00:11:44.320 --> 00:11:46.629 align:start position:0% to jailbreak a lot of older iPhones I use<00:11:44.600> P<00:11:44.839> Rin<00:11:45.079> for<00:11:45.320> that<00:11:45.560> but<00:11:45.680> you<00:11:45.880> might<00:11:46.320> want<00:11:46.480> to 00:11:46.629 --> 00:11:46.639 align:start position:0% use P Rin for that but you might want to 00:11:46.639 --> 00:11:48.949 align:start position:0% use P Rin for that but you might want to use<00:11:46.880> another<00:11:47.240> exploit<00:11:48.200> it's<00:11:48.320> a<00:11:48.440> bit<00:11:48.639> hard<00:11:48.800> to 00:11:48.949 --> 00:11:48.959 align:start position:0% use another exploit it's a bit hard to 00:11:48.959 --> 00:11:51.230 align:start position:0% use another exploit it's a bit hard to run<00:11:49.360> but<00:11:50.000> well<00:11:50.240> you<00:11:50.320> will<00:11:50.519> manage<00:11:50.760> to<00:11:50.920> run<00:11:51.079> it 00:11:51.230 --> 00:11:51.240 align:start position:0% run but well you will manage to run it 00:11:51.240 --> 00:11:52.629 align:start position:0% run but well you will manage to run it if<00:11:51.360> you 00:11:52.629 --> 00:11:52.639 align:start position:0% if you 00:11:52.639 --> 00:11:55.509 align:start position:0% if you want<00:11:53.639> then<00:11:53.760> we<00:11:53.920> can<00:11:54.120> D<00:11:54.320> the<00:11:54.440> keychain<00:11:55.200> we<00:11:55.320> have 00:11:55.509 --> 00:11:55.519 align:start position:0% want then we can D the keychain we have 00:11:55.519 --> 00:11:57.230 align:start position:0% want then we can D the keychain we have some<00:11:55.800> information<00:11:56.279> about<00:11:56.480> the<00:11:56.600> keychain<00:11:57.040> at 00:11:57.230 --> 00:11:57.240 align:start position:0% some information about the keychain at 00:11:57.240 --> 00:11:59.590 align:start position:0% some information about the keychain at Apple<00:11:58.200> uh<00:11:58.440> but<00:11:58.760> here<00:11:58.959> the<00:11:59.040> first<00:11:59.279> first<00:11:59.440> thing 00:11:59.590 --> 00:11:59.600 align:start position:0% Apple uh but here the first first thing 00:11:59.600 --> 00:12:01.110 align:start position:0% Apple uh but here the first first thing that<00:11:59.760> we<00:11:59.880> notice<00:12:00.279> is<00:12:00.440> that<00:12:00.600> there<00:12:00.720> is<00:12:00.880> no 00:12:01.110 --> 00:12:01.120 align:start position:0% that we notice is that there is no 00:12:01.120 --> 00:12:02.790 align:start position:0% that we notice is that there is no security<00:12:01.600> property<00:12:02.079> that<00:12:02.240> says<00:12:02.519> that<00:12:02.639> the 00:12:02.790 --> 00:12:02.800 align:start position:0% security property that says that the 00:12:02.800 --> 00:12:04.949 align:start position:0% security property that says that the credential<00:12:03.440> needs<00:12:03.720> to<00:12:03.880> be<00:12:04.040> authenticated 00:12:04.949 --> 00:12:04.959 align:start position:0% credential needs to be authenticated 00:12:04.959 --> 00:12:07.190 align:start position:0% credential needs to be authenticated every<00:12:05.200> time<00:12:05.839> it's<00:12:06.079> basically<00:12:06.440> authenticated 00:12:07.190 --> 00:12:07.200 align:start position:0% every time it's basically authenticated 00:12:07.200 --> 00:12:09.350 align:start position:0% every time it's basically authenticated at<00:12:07.519> unlock<00:12:07.959> when<00:12:08.079> the<00:12:08.240> device<00:12:08.519> is<00:12:08.639> unlocked 00:12:09.350 --> 00:12:09.360 align:start position:0% at unlock when the device is unlocked 00:12:09.360 --> 00:12:11.030 align:start position:0% at unlock when the device is unlocked and<00:12:09.519> then<00:12:09.680> it's<00:12:09.880> not<00:12:10.120> going<00:12:10.320> to<00:12:10.480> be<00:12:10.639> locked 00:12:11.030 --> 00:12:11.040 align:start position:0% and then it's not going to be locked 00:12:11.040 --> 00:12:15.310 align:start position:0% and then it's not going to be locked again<00:12:11.800> so<00:12:11.959> we<00:12:12.079> see<00:12:12.240> a<00:12:12.399> first<00:12:12.680> problem 00:12:15.310 --> 00:12:15.320 align:start position:0% 00:12:15.320 --> 00:12:18.230 align:start position:0% here<00:12:16.320> then<00:12:16.720> digging<00:12:17.120> into<00:12:17.440> it<00:12:17.680> dumping<00:12:18.079> the 00:12:18.230 --> 00:12:18.240 align:start position:0% here then digging into it dumping the 00:12:18.240 --> 00:12:21.269 align:start position:0% here then digging into it dumping the kitchen<00:12:18.680> itself<00:12:19.279> we<00:12:19.440> get<00:12:19.639> more<00:12:20.279> information 00:12:21.269 --> 00:12:21.279 align:start position:0% kitchen itself we get more information 00:12:21.279 --> 00:12:23.949 align:start position:0% kitchen itself we get more information uh<00:12:21.399> we<00:12:21.560> got<00:12:21.839> a<00:12:22.079> first<00:12:22.959> uh<00:12:23.199> attempt<00:12:23.639> that<00:12:23.800> was 00:12:23.949 --> 00:12:23.959 align:start position:0% uh we got a first uh attempt that was 00:12:23.959 --> 00:12:26.189 align:start position:0% uh we got a first uh attempt that was done<00:12:24.120> on<00:12:24.279> an<00:12:24.440> older<00:12:24.880> version<00:12:25.160> of<00:12:25.360> iOS<00:12:26.000> a 00:12:26.189 --> 00:12:26.199 align:start position:0% done on an older version of iOS a 00:12:26.199 --> 00:12:27.710 align:start position:0% done on an older version of iOS a description<00:12:26.639> of<00:12:26.800> what<00:12:26.959> the<00:12:27.079> kitchen<00:12:27.399> looks 00:12:27.710 --> 00:12:27.720 align:start position:0% description of what the kitchen looks 00:12:27.720 --> 00:12:30.030 align:start position:0% description of what the kitchen looks like<00:12:28.440> uh<00:12:28.600> we<00:12:28.760> basically<00:12:29.320> we<00:12:29.399> have<00:12:29.600> items<00:12:29.920> in 00:12:30.030 --> 00:12:30.040 align:start position:0% like uh we basically we have items in 00:12:30.040 --> 00:12:32.629 align:start position:0% like uh we basically we have items in the<00:12:30.199> kitchen<00:12:30.800> which<00:12:30.920> are<00:12:31.720> um<00:12:31.959> defined<00:12:32.360> by<00:12:32.480> a 00:12:32.629 --> 00:12:32.639 align:start position:0% the kitchen which are um defined by a 00:12:32.639 --> 00:12:35.189 align:start position:0% the kitchen which are um defined by a metadata<00:12:33.399> and<00:12:33.680> the<00:12:33.800> secret<00:12:34.240> itself<00:12:35.040> the 00:12:35.189 --> 00:12:35.199 align:start position:0% metadata and the secret itself the 00:12:35.199 --> 00:12:37.670 align:start position:0% metadata and the secret itself the metadata<00:12:35.680> and<00:12:35.839> secret<00:12:36.199> are<00:12:36.360> W<00:12:36.680> by<00:12:36.800> a<00:12:36.959> key<00:12:37.519> which 00:12:37.670 --> 00:12:37.680 align:start position:0% metadata and secret are W by a key which 00:12:37.680 --> 00:12:39.829 align:start position:0% metadata and secret are W by a key which is<00:12:38.040> handled<00:12:38.480> by<00:12:38.600> the<00:12:38.760> platform<00:12:39.279> so<00:12:39.480> you<00:12:39.600> need 00:12:39.829 --> 00:12:39.839 align:start position:0% is handled by the platform so you need 00:12:39.839 --> 00:12:42.550 align:start position:0% is handled by the platform so you need to<00:12:40.079> have<00:12:40.279> the<00:12:40.480> device<00:12:40.880> in<00:12:41.000> order<00:12:41.240> to<00:12:41.399> deip<00:12:41.880> this 00:12:42.550 --> 00:12:42.560 align:start position:0% to have the device in order to deip this 00:12:42.560 --> 00:12:43.910 align:start position:0% to have the device in order to deip this and<00:12:42.720> you<00:12:42.839> have<00:12:43.000> an<00:12:43.199> in<00:12:43.560> you<00:12:43.680> have<00:12:43.800> an 00:12:43.910 --> 00:12:43.920 align:start position:0% and you have an in you have an 00:12:43.920 --> 00:12:45.550 align:start position:0% and you have an in you have an additional<00:12:44.360> IND<00:12:44.600> Direction<00:12:44.959> level<00:12:45.360> for 00:12:45.550 --> 00:12:45.560 align:start position:0% additional IND Direction level for 00:12:45.560 --> 00:12:47.990 align:start position:0% additional IND Direction level for metadata<00:12:46.199> so<00:12:46.360> you<00:12:46.480> have<00:12:46.600> an<00:12:46.720> extra<00:12:47.120> key<00:12:47.839> uh 00:12:47.990 --> 00:12:48.000 align:start position:0% metadata so you have an extra key uh 00:12:48.000 --> 00:12:50.150 align:start position:0% metadata so you have an extra key uh which<00:12:48.160> will<00:12:48.360> be<00:12:48.600> deied<00:12:49.160> by<00:12:49.279> the<00:12:49.440> platform<00:12:49.839> as 00:12:50.150 --> 00:12:50.160 align:start position:0% which will be deied by the platform as 00:12:50.160 --> 00:12:52.670 align:start position:0% which will be deied by the platform as well<00:12:51.160> but<00:12:51.320> the<00:12:51.440> scheme<00:12:51.760> is<00:12:52.120> the<00:12:52.240> scheme<00:12:52.519> is 00:12:52.670 --> 00:12:52.680 align:start position:0% well but the scheme is the scheme is 00:12:52.680 --> 00:12:55.189 align:start position:0% well but the scheme is the scheme is always<00:12:53.360> metadata<00:12:53.880> in<00:12:54.079> secret<00:12:54.519> protected<00:12:54.920> by<00:12:55.040> a 00:12:55.189 --> 00:12:55.199 align:start position:0% always metadata in secret protected by a 00:12:55.199 --> 00:12:56.230 align:start position:0% always metadata in secret protected by a key 00:12:56.230 --> 00:12:56.240 align:start position:0% key 00:12:56.240 --> 00:12:58.670 align:start position:0% key basically<00:12:57.240> so<00:12:57.480> there<00:12:57.600> is<00:12:57.720> a<00:12:57.880> small<00:12:58.199> difference 00:12:58.670 --> 00:12:58.680 align:start position:0% basically so there is a small difference 00:12:58.680 --> 00:13:02.110 align:start position:0% basically so there is a small difference between<00:12:59.440> two<00:12:59.760> item<00:13:00.079> version<00:13:00.839> and<00:13:01.120> basically 00:13:02.110 --> 00:13:02.120 align:start position:0% between two item version and basically 00:13:02.120 --> 00:13:04.470 align:start position:0% between two item version and basically uh<00:13:02.320> knowing<00:13:02.800> this<00:13:03.000> you<00:13:03.120> can<00:13:03.360> fix<00:13:04.000> uh<00:13:04.160> what<00:13:04.320> is 00:13:04.470 --> 00:13:04.480 align:start position:0% uh knowing this you can fix uh what is 00:13:04.480 --> 00:13:06.230 align:start position:0% uh knowing this you can fix uh what is on<00:13:04.680> the<00:13:04.839> internet<00:13:05.240> today<00:13:05.600> and<00:13:05.720> you<00:13:05.839> can<00:13:06.079> make 00:13:06.230 --> 00:13:06.240 align:start position:0% on the internet today and you can make 00:13:06.240 --> 00:13:08.949 align:start position:0% on the internet today and you can make it<00:13:06.560> dump<00:13:07.320> um<00:13:07.600> the<00:13:07.720> recent<00:13:08.079> items<00:13:08.639> because 00:13:08.949 --> 00:13:08.959 align:start position:0% it dump um the recent items because 00:13:08.959 --> 00:13:11.110 align:start position:0% it dump um the recent items because protocol<00:13:09.360> buffers<00:13:09.800> is<00:13:10.000> very<00:13:10.199> easy<00:13:10.480> to 00:13:11.110 --> 00:13:11.120 align:start position:0% protocol buffers is very easy to 00:13:11.120 --> 00:13:12.750 align:start position:0% protocol buffers is very easy to describe<00:13:11.519> I<00:13:11.600> mean<00:13:11.720> it's<00:13:11.839> self<00:13:12.120> describing<00:13:12.639> so 00:13:12.750 --> 00:13:12.760 align:start position:0% describe I mean it's self describing so 00:13:12.760 --> 00:13:15.590 align:start position:0% describe I mean it's self describing so you<00:13:12.880> can<00:13:13.040> modify<00:13:13.839> this<00:13:14.839> when<00:13:15.000> you<00:13:15.199> look<00:13:15.360> at<00:13:15.440> the 00:13:15.590 --> 00:13:15.600 align:start position:0% you can modify this when you look at the 00:13:15.600 --> 00:13:18.750 align:start position:0% you can modify this when you look at the decrypted<00:13:16.440> item<00:13:17.079> you'll<00:13:17.320> see<00:13:17.560> that<00:13:17.720> the<00:13:17.880> value 00:13:18.750 --> 00:13:18.760 align:start position:0% decrypted item you'll see that the value 00:13:18.760 --> 00:13:21.110 align:start position:0% decrypted item you'll see that the value the<00:13:18.920> length<00:13:19.199> of<00:13:19.320> the<00:13:19.480> value<00:13:19.720> is<00:13:19.880> 65<00:13:20.440> bytes<00:13:20.880> plus 00:13:21.110 --> 00:13:21.120 align:start position:0% the length of the value is 65 bytes plus 00:13:21.120 --> 00:13:23.949 align:start position:0% the length of the value is 65 bytes plus 32<00:13:21.720> starting<00:13:22.079> with<00:13:22.360> 04<00:13:23.360> if<00:13:23.440> you<00:13:23.560> have<00:13:23.680> played 00:13:23.949 --> 00:13:23.959 align:start position:0% 32 starting with 04 if you have played 00:13:23.959 --> 00:13:25.829 align:start position:0% 32 starting with 04 if you have played with<00:13:24.160> key<00:13:24.440> you<00:13:24.600> think<00:13:24.880> that<00:13:25.199> okay<00:13:25.440> this<00:13:25.639> might 00:13:25.829 --> 00:13:25.839 align:start position:0% with key you think that okay this might 00:13:25.839 --> 00:13:27.710 align:start position:0% with key you think that okay this might just<00:13:26.040> be<00:13:26.160> the<00:13:26.360> public<00:13:26.720> key<00:13:27.120> and<00:13:27.240> the<00:13:27.399> private 00:13:27.710 --> 00:13:27.720 align:start position:0% just be the public key and the private 00:13:27.720 --> 00:13:30.710 align:start position:0% just be the public key and the private key<00:13:28.120> concatenated<00:13:29.199> um<00:13:29.440> you<00:13:29.560> can<00:13:29.839> verify<00:13:30.279> it<00:13:30.519> by 00:13:30.710 --> 00:13:30.720 align:start position:0% key concatenated um you can verify it by 00:13:30.720 --> 00:13:32.670 align:start position:0% key concatenated um you can verify it by dumping<00:13:31.079> the<00:13:31.279> key<00:13:31.839> verifying<00:13:32.360> that<00:13:32.519> the 00:13:32.670 --> 00:13:32.680 align:start position:0% dumping the key verifying that the 00:13:32.680 --> 00:13:34.430 align:start position:0% dumping the key verifying that the public<00:13:33.000> key<00:13:33.240> Associated<00:13:33.680> to<00:13:33.800> the<00:13:33.959> private<00:13:34.279> key 00:13:34.430 --> 00:13:34.440 align:start position:0% public key Associated to the private key 00:13:34.440 --> 00:13:36.710 align:start position:0% public key Associated to the private key is<00:13:34.519> the<00:13:34.680> right<00:13:34.880> one<00:13:35.120> and<00:13:35.279> it<00:13:35.399> is<00:13:35.519> the<00:13:35.720> right<00:13:35.920> one 00:13:36.710 --> 00:13:36.720 align:start position:0% is the right one and it is the right one 00:13:36.720 --> 00:13:39.430 align:start position:0% is the right one and it is the right one so<00:13:36.920> this<00:13:37.160> means<00:13:37.760> we<00:13:37.880> have<00:13:38.000> a<00:13:38.120> way<00:13:38.240> to<00:13:38.399> decrypt<00:13:39.320> a 00:13:39.430 --> 00:13:39.440 align:start position:0% so this means we have a way to decrypt a 00:13:39.440 --> 00:13:41.350 align:start position:0% so this means we have a way to decrypt a malware<00:13:39.880> has<00:13:40.000> a<00:13:40.120> way<00:13:40.240> to<00:13:40.360> decrypt<00:13:40.760> the<00:13:40.880> kit<00:13:41.160> can 00:13:41.350 --> 00:13:41.360 align:start position:0% malware has a way to decrypt the kit can 00:13:41.360 --> 00:13:43.710 align:start position:0% malware has a way to decrypt the kit can steal<00:13:41.680> it<00:13:41.920> and<00:13:42.040> it's<00:13:42.240> fully<00:13:42.519> unol<00:13:43.000> by<00:13:43.440> by<00:13:43.560> the 00:13:43.710 --> 00:13:43.720 align:start position:0% steal it and it's fully unol by by the 00:13:43.720 --> 00:13:45.310 align:start position:0% steal it and it's fully unol by by the application<00:13:44.240> processor<00:13:44.600> on 00:13:45.310 --> 00:13:45.320 align:start position:0% application processor on 00:13:45.320 --> 00:13:47.790 align:start position:0% application processor on iOS<00:13:46.320> um<00:13:46.440> on<00:13:46.600> Android<00:13:47.040> we<00:13:47.120> can<00:13:47.240> do<00:13:47.399> the<00:13:47.560> same 00:13:47.790 --> 00:13:47.800 align:start position:0% iOS um on Android we can do the same 00:13:47.800 --> 00:13:50.509 align:start position:0% iOS um on Android we can do the same thing<00:13:48.519> uh<00:13:48.680> it's<00:13:49.160> much<00:13:49.519> easier<00:13:49.880> to<00:13:50.040> jailbreak 00:13:50.509 --> 00:13:50.519 align:start position:0% thing uh it's much easier to jailbreak 00:13:50.519 --> 00:13:52.710 align:start position:0% thing uh it's much easier to jailbreak an<00:13:50.680> Android<00:13:51.040> phone<00:13:51.440> because<00:13:51.720> you<00:13:51.839> can<00:13:52.160> just 00:13:52.710 --> 00:13:52.720 align:start position:0% an Android phone because you can just 00:13:52.720 --> 00:13:54.670 align:start position:0% an Android phone because you can just unlock<00:13:53.120> the<00:13:53.240> bootloader<00:13:53.759> install<00:13:54.120> magic<00:13:54.519> and 00:13:54.670 --> 00:13:54.680 align:start position:0% unlock the bootloader install magic and 00:13:54.680 --> 00:13:59.670 align:start position:0% unlock the bootloader install magic and you're<00:13:55.240> magist<00:13:56.639> ma<00:13:57.639> Magis<00:13:58.279> and<00:13:58.440> you're<00:13:58.639> done 00:13:59.670 --> 00:13:59.680 align:start position:0% you're magist ma Magis and you're done 00:13:59.680 --> 00:14:02.110 align:start position:0% you're magist ma Magis and you're done and<00:13:59.959> to<00:14:00.360> look<00:14:00.560> at<00:14:00.720> the<00:14:00.880> application<00:14:01.519> we'll<00:14:01.759> use 00:14:02.110 --> 00:14:02.120 align:start position:0% and to look at the application we'll use 00:14:02.120 --> 00:14:04.350 align:start position:0% and to look at the application we'll use a<00:14:02.240> framework<00:14:02.720> called<00:14:02.920> Freda<00:14:03.800> uh<00:14:03.920> which<00:14:04.079> will 00:14:04.350 --> 00:14:04.360 align:start position:0% a framework called Freda uh which will 00:14:04.360 --> 00:14:06.550 align:start position:0% a framework called Freda uh which will let<00:14:04.600> us<00:14:04.959> introspect<00:14:05.680> the<00:14:05.839> application<00:14:06.320> and 00:14:06.550 --> 00:14:06.560 align:start position:0% let us introspect the application and 00:14:06.560 --> 00:14:09.110 align:start position:0% let us introspect the application and inject<00:14:07.079> code<00:14:07.399> to<00:14:07.880> understand<00:14:08.199> what<00:14:08.759> um<00:14:08.959> the 00:14:09.110 --> 00:14:09.120 align:start position:0% inject code to understand what um the 00:14:09.120 --> 00:14:10.230 align:start position:0% inject code to understand what um the program<00:14:09.440> is 00:14:10.230 --> 00:14:10.240 align:start position:0% program is 00:14:10.240 --> 00:14:13.030 align:start position:0% program is doing<00:14:11.240> first<00:14:11.600> question<00:14:12.120> it's<00:14:12.360> very<00:14:12.600> s<00:14:12.880> it's 00:14:13.030 --> 00:14:13.040 align:start position:0% doing first question it's very s it's 00:14:13.040 --> 00:14:15.430 align:start position:0% doing first question it's very s it's very<00:14:13.240> clear<00:14:13.440> on<00:14:13.600> iOS<00:14:14.360> where<00:14:14.560> the<00:14:14.720> kitchen<00:14:15.160> is 00:14:15.430 --> 00:14:15.440 align:start position:0% very clear on iOS where the kitchen is 00:14:15.440 --> 00:14:17.949 align:start position:0% very clear on iOS where the kitchen is on<00:14:15.680> Android<00:14:16.160> not<00:14:16.399> that<00:14:16.600> much<00:14:17.360> so<00:14:17.560> we<00:14:17.680> want<00:14:17.839> to 00:14:17.949 --> 00:14:17.959 align:start position:0% on Android not that much so we want to 00:14:17.959 --> 00:14:19.990 align:start position:0% on Android not that much so we want to know<00:14:18.160> where<00:14:18.360> we<00:14:18.480> are<00:14:19.079> and<00:14:19.240> for<00:14:19.519> that<00:14:19.720> we<00:14:19.839> are 00:14:19.990 --> 00:14:20.000 align:start position:0% know where we are and for that we are 00:14:20.000 --> 00:14:22.350 align:start position:0% know where we are and for that we are going<00:14:20.240> to<00:14:20.440> look<00:14:20.600> at<00:14:20.720> the<00:14:20.839> logs<00:14:21.480> we<00:14:21.600> see<00:14:21.959> that<00:14:22.240> we 00:14:22.350 --> 00:14:22.360 align:start position:0% going to look at the logs we see that we 00:14:22.360 --> 00:14:24.590 align:start position:0% going to look at the logs we see that we see<00:14:22.519> a<00:14:22.639> lot<00:14:22.800> of<00:14:22.920> logs<00:14:23.320> referring<00:14:23.880> GMS<00:14:24.399> for 00:14:24.590 --> 00:14:24.600 align:start position:0% see a lot of logs referring GMS for 00:14:24.600 --> 00:14:26.829 align:start position:0% see a lot of logs referring GMS for Google<00:14:24.880> mobile<00:14:25.279> services<00:14:26.120> looks<00:14:26.360> like<00:14:26.480> a<00:14:26.639> good 00:14:26.829 --> 00:14:26.839 align:start position:0% Google mobile services looks like a good 00:14:26.839 --> 00:14:29.350 align:start position:0% Google mobile services looks like a good place<00:14:27.079> to<00:14:27.560> place<00:14:27.759> to<00:14:27.959> start<00:14:28.240> so<00:14:28.440> we<00:14:28.680> instrument 00:14:29.350 --> 00:14:29.360 align:start position:0% place to place to start so we instrument 00:14:29.360 --> 00:14:32.550 align:start position:0% place to place to start so we instrument it<00:14:30.160> to<00:14:30.320> instrument<00:14:30.880> it<00:14:31.120> we'll<00:14:31.560> just<00:14:32.120> use<00:14:32.399> the 00:14:32.550 --> 00:14:32.560 align:start position:0% it to instrument it we'll just use the 00:14:32.560 --> 00:14:35.030 align:start position:0% it to instrument it we'll just use the signature<00:14:33.079> API<00:14:33.519> in<00:14:33.759> Java<00:14:34.240> and<00:14:34.360> we<00:14:34.480> will<00:14:34.800> ask 00:14:35.030 --> 00:14:35.040 align:start position:0% signature API in Java and we will ask 00:14:35.040 --> 00:14:36.949 align:start position:0% signature API in Java and we will ask for<00:14:35.240> the<00:14:35.440> class<00:14:35.800> that<00:14:35.920> is<00:14:36.079> being<00:14:36.320> used<00:14:36.720> because 00:14:36.949 --> 00:14:36.959 align:start position:0% for the class that is being used because 00:14:36.959 --> 00:14:39.710 align:start position:0% for the class that is being used because that<00:14:37.160> way<00:14:37.320> we<00:14:37.440> can<00:14:37.560> dig<00:14:37.839> further<00:14:38.639> and<00:14:38.800> we<00:14:38.959> can 00:14:39.710 --> 00:14:39.720 align:start position:0% that way we can dig further and we can 00:14:39.720 --> 00:14:42.949 align:start position:0% that way we can dig further and we can try<00:14:40.000> to<00:14:40.199> know<00:14:40.720> exactly<00:14:41.199> what<00:14:41.320> is<00:14:41.720> happening<00:14:42.720> so 00:14:42.949 --> 00:14:42.959 align:start position:0% try to know exactly what is happening so 00:14:42.959 --> 00:14:45.509 align:start position:0% try to know exactly what is happening so we<00:14:43.120> do<00:14:43.320> that<00:14:43.560> with<00:14:43.759> GMS<00:14:44.399> we<00:14:44.560> see<00:14:44.880> finally<00:14:45.360> the 00:14:45.509 --> 00:14:45.519 align:start position:0% we do that with GMS we see finally the 00:14:45.519 --> 00:14:48.310 align:start position:0% we do that with GMS we see finally the name<00:14:45.680> of<00:14:45.839> the<00:14:46.120> class<00:14:47.120> and<00:14:47.440> we<00:14:47.560> can<00:14:47.839> find<00:14:48.079> some 00:14:48.310 --> 00:14:48.320 align:start position:0% name of the class and we can find some 00:14:48.320 --> 00:14:49.829 align:start position:0% name of the class and we can find some information<00:14:48.839> about<00:14:49.079> that<00:14:49.279> class<00:14:49.519> on<00:14:49.680> the 00:14:49.829 --> 00:14:49.839 align:start position:0% information about that class on the 00:14:49.839 --> 00:14:52.030 align:start position:0% information about that class on the internet<00:14:50.839> uh<00:14:50.959> we<00:14:51.040> see<00:14:51.279> that<00:14:51.399> it's<00:14:51.519> a<00:14:51.680> wrapper 00:14:52.030 --> 00:14:52.040 align:start position:0% internet uh we see that it's a wrapper 00:14:52.040 --> 00:14:54.509 align:start position:0% internet uh we see that it's a wrapper to<00:14:52.199> another<00:14:52.560> class<00:14:52.839> so<00:14:53.079> we<00:14:53.240> still<00:14:53.480> don't<00:14:53.759> know 00:14:54.509 --> 00:14:54.519 align:start position:0% to another class so we still don't know 00:14:54.519 --> 00:14:56.110 align:start position:0% to another class so we still don't know if<00:14:54.680> the<00:14:54.839> credential<00:14:55.399> is<00:14:55.560> handled<00:14:55.920> by<00:14:56.000> the 00:14:56.110 --> 00:14:56.120 align:start position:0% if the credential is handled by the 00:14:56.120 --> 00:14:58.069 align:start position:0% if the credential is handled by the secure<00:14:56.399> onclave<00:14:56.920> or<00:14:57.079> on<00:14:57.199> the<00:14:57.399> device<00:14:57.759> but<00:14:57.920> at 00:14:58.069 --> 00:14:58.079 align:start position:0% secure onclave or on the device but at 00:14:58.079 --> 00:15:00.310 align:start position:0% secure onclave or on the device but at least<00:14:58.279> we<00:14:58.399> can<00:14:58.519> dig<00:14:58.720> further 00:15:00.310 --> 00:15:00.320 align:start position:0% least we can dig further 00:15:00.320 --> 00:15:02.990 align:start position:0% least we can dig further so<00:15:00.600> we<00:15:00.839> start<00:15:01.199> instrumenting<00:15:01.920> again<00:15:02.480> and<00:15:02.800> this 00:15:02.990 --> 00:15:03.000 align:start position:0% so we start instrumenting again and this 00:15:03.000 --> 00:15:05.189 align:start position:0% so we start instrumenting again and this time<00:15:03.199> we<00:15:03.320> will<00:15:03.480> dump<00:15:03.759> the<00:15:03.880> key<00:15:04.519> so<00:15:04.800> we<00:15:04.920> will 00:15:05.189 --> 00:15:05.199 align:start position:0% time we will dump the key so we will 00:15:05.199 --> 00:15:06.790 align:start position:0% time we will dump the key so we will assume<00:15:05.600> that<00:15:05.759> if<00:15:05.880> we<00:15:06.000> have<00:15:06.120> the<00:15:06.279> right<00:15:06.480> class 00:15:06.790 --> 00:15:06.800 align:start position:0% assume that if we have the right class 00:15:06.800 --> 00:15:09.110 align:start position:0% assume that if we have the right class we<00:15:06.920> can<00:15:07.199> cast<00:15:07.519> it<00:15:08.000> and<00:15:08.120> we<00:15:08.240> can<00:15:08.399> ask<00:15:08.600> it<00:15:08.720> to<00:15:08.880> Dum 00:15:09.110 --> 00:15:09.120 align:start position:0% we can cast it and we can ask it to Dum 00:15:09.120 --> 00:15:11.790 align:start position:0% we can cast it and we can ask it to Dum the<00:15:09.279> key<00:15:09.959> and<00:15:10.160> it<00:15:10.360> works<00:15:10.880> so<00:15:11.079> we<00:15:11.199> can<00:15:11.360> Dum<00:15:11.680> the 00:15:11.790 --> 00:15:11.800 align:start position:0% the key and it works so we can Dum the 00:15:11.800 --> 00:15:13.749 align:start position:0% the key and it works so we can Dum the key<00:15:12.199> we<00:15:12.360> can<00:15:12.519> Dum<00:15:12.759> the<00:15:12.920> key<00:15:13.079> we<00:15:13.199> can<00:15:13.360> verify 00:15:13.749 --> 00:15:13.759 align:start position:0% key we can Dum the key we can verify 00:15:13.759 --> 00:15:15.550 align:start position:0% key we can Dum the key we can verify it's<00:15:13.920> the<00:15:14.040> right<00:15:14.240> private<00:15:14.600> key<00:15:15.079> it<00:15:15.199> matches 00:15:15.550 --> 00:15:15.560 align:start position:0% it's the right private key it matches 00:15:15.560 --> 00:15:17.350 align:start position:0% it's the right private key it matches the<00:15:15.720> public<00:15:16.040> key<00:15:16.560> which<00:15:16.720> means<00:15:17.000> that<00:15:17.160> on 00:15:17.350 --> 00:15:17.360 align:start position:0% the public key which means that on 00:15:17.360 --> 00:15:19.629 align:start position:0% the public key which means that on Android<00:15:17.880> and<00:15:18.199> iOS<00:15:18.720> we<00:15:18.839> have<00:15:19.040> verified<00:15:19.519> that 00:15:19.629 --> 00:15:19.639 align:start position:0% Android and iOS we have verified that 00:15:19.639 --> 00:15:22.350 align:start position:0% Android and iOS we have verified that the<00:15:19.839> key<00:15:20.000> is<00:15:20.160> unol<00:15:20.600> by<00:15:20.720> the<00:15:20.839> application 00:15:22.350 --> 00:15:22.360 align:start position:0% the key is unol by the application 00:15:22.360 --> 00:15:25.269 align:start position:0% the key is unol by the application processor<00:15:23.360> as<00:15:23.519> a<00:15:23.680> bonus<00:15:24.120> on<00:15:24.360> Android<00:15:24.880> so<00:15:25.079> it's 00:15:25.269 --> 00:15:25.279 align:start position:0% processor as a bonus on Android so it's 00:15:25.279 --> 00:15:28.230 align:start position:0% processor as a bonus on Android so it's yet<00:15:25.519> another<00:15:26.079> yet<00:15:26.279> another<00:15:26.680> big<00:15:26.920> wat<00:15:27.360> here<00:15:28.079> uh 00:15:28.230 --> 00:15:28.240 align:start position:0% yet another yet another big wat here uh 00:15:28.240 --> 00:15:30.069 align:start position:0% yet another yet another big wat here uh we<00:15:28.399> get<00:15:28.560> the<00:15:28.720> key<00:15:29.079> before<00:15:29.399> the<00:15:29.560> user 00:15:30.069 --> 00:15:30.079 align:start position:0% we get the key before the user 00:15:30.079 --> 00:15:31.829 align:start position:0% we get the key before the user authentication<00:15:31.079> which<00:15:31.240> means<00:15:31.480> that<00:15:31.639> there<00:15:31.759> is 00:15:31.829 --> 00:15:31.839 align:start position:0% authentication which means that there is 00:15:31.839 --> 00:15:33.670 align:start position:0% authentication which means that there is a<00:15:32.000> catch<00:15:32.360> mechanism<00:15:32.920> that<00:15:33.040> is<00:15:33.160> loading<00:15:33.519> the 00:15:33.670 --> 00:15:33.680 align:start position:0% a catch mechanism that is loading the 00:15:33.680 --> 00:15:35.590 align:start position:0% a catch mechanism that is loading the key<00:15:33.959> and<00:15:34.120> user<00:15:34.399> authentication<00:15:35.040> is<00:15:35.240> just 00:15:35.590 --> 00:15:35.600 align:start position:0% key and user authentication is just 00:15:35.600 --> 00:15:38.309 align:start position:0% key and user authentication is just there<00:15:36.480> basically<00:15:37.319> to<00:15:37.560> make<00:15:37.720> you<00:15:37.920> think<00:15:38.199> that 00:15:38.309 --> 00:15:38.319 align:start position:0% there basically to make you think that 00:15:38.319 --> 00:15:40.230 align:start position:0% there basically to make you think that it's<00:15:38.519> secure<00:15:38.880> but<00:15:39.040> it's<00:15:39.160> not<00:15:39.360> really<00:15:39.920> it's<00:15:40.079> not 00:15:40.230 --> 00:15:40.240 align:start position:0% it's secure but it's not really it's not 00:15:40.240 --> 00:15:42.949 align:start position:0% it's secure but it's not really it's not really<00:15:40.639> secure<00:15:41.639> uh<00:15:41.959> finally<00:15:42.360> looking<00:15:42.639> at<00:15:42.800> an 00:15:42.949 --> 00:15:42.959 align:start position:0% really secure uh finally looking at an 00:15:42.959 --> 00:15:44.870 align:start position:0% really secure uh finally looking at an external<00:15:43.440> password<00:15:43.839> manager<00:15:44.399> here<00:15:44.560> we<00:15:44.680> have 00:15:44.870 --> 00:15:44.880 align:start position:0% external password manager here we have 00:15:44.880 --> 00:15:47.150 align:start position:0% external password manager here we have absolutely<00:15:45.360> no<00:15:45.600> expectation<00:15:46.600> um<00:15:46.720> so<00:15:46.920> it's 00:15:47.150 --> 00:15:47.160 align:start position:0% absolutely no expectation um so it's 00:15:47.160 --> 00:15:49.910 align:start position:0% absolutely no expectation um so it's good<00:15:48.040> um<00:15:48.720> I<00:15:48.839> did<00:15:49.000> the<00:15:49.160> example<00:15:49.480> with<00:15:49.639> bit 00:15:49.910 --> 00:15:49.920 align:start position:0% good um I did the example with bit 00:15:49.920 --> 00:15:51.990 align:start position:0% good um I did the example with bit Warden<00:15:50.560> you<00:15:50.680> can<00:15:50.839> see<00:15:51.079> when<00:15:51.199> you<00:15:51.360> dump<00:15:51.680> it<00:15:51.839> that 00:15:51.990 --> 00:15:52.000 align:start position:0% Warden you can see when you dump it that 00:15:52.000 --> 00:15:54.509 align:start position:0% Warden you can see when you dump it that the<00:15:52.079> credential<00:15:52.680> is<00:15:52.839> listed<00:15:53.240> as<00:15:53.360> a<00:15:53.519> public<00:15:53.839> key 00:15:54.509 --> 00:15:54.519 align:start position:0% the credential is listed as a public key 00:15:54.519 --> 00:15:56.269 align:start position:0% the credential is listed as a public key uh<00:15:54.680> bad<00:15:54.920> news<00:15:55.160> it's<00:15:55.319> not<00:15:55.480> a<00:15:55.639> public<00:15:55.920> key<00:15:56.160> of 00:15:56.269 --> 00:15:56.279 align:start position:0% uh bad news it's not a public key of 00:15:56.279 --> 00:15:57.870 align:start position:0% uh bad news it's not a public key of course<00:15:56.440> it's<00:15:56.560> a<00:15:56.720> private<00:15:57.079> key<00:15:57.279> so<00:15:57.440> we<00:15:57.560> can<00:15:57.720> just 00:15:57.870 --> 00:15:57.880 align:start position:0% course it's a private key so we can just 00:15:57.880 --> 00:16:00.069 align:start position:0% course it's a private key so we can just dump<00:15:58.160> it<00:15:58.360> look<00:15:58.560> at<00:15:58.720> it<00:15:59.279> look<00:15:59.480> at<00:15:59.600> the<00:15:59.759> private 00:16:00.069 --> 00:16:00.079 align:start position:0% dump it look at it look at the private 00:16:00.079 --> 00:16:01.749 align:start position:0% dump it look at it look at the private key<00:16:00.319> verify<00:16:00.759> that<00:16:00.880> it<00:16:01.000> matches<00:16:01.319> the<00:16:01.440> public 00:16:01.749 --> 00:16:01.759 align:start position:0% key verify that it matches the public 00:16:01.759 --> 00:16:04.269 align:start position:0% key verify that it matches the public key<00:16:02.040> exactly<00:16:02.360> the<00:16:02.480> same<00:16:02.759> thing<00:16:03.399> so<00:16:03.959> if<00:16:04.079> you 00:16:04.269 --> 00:16:04.279 align:start position:0% key exactly the same thing so if you 00:16:04.279 --> 00:16:06.150 align:start position:0% key exactly the same thing so if you expected<00:16:04.720> some<00:16:05.040> security<00:16:05.560> by<00:16:05.720> saving<00:16:06.000> your 00:16:06.150 --> 00:16:06.160 align:start position:0% expected some security by saving your 00:16:06.160 --> 00:16:07.710 align:start position:0% expected some security by saving your pass<00:16:06.399> key<00:16:06.519> to<00:16:06.639> a<00:16:06.720> passform<00:16:07.079> manager<00:16:07.440> you<00:16:07.600> have 00:16:07.710 --> 00:16:07.720 align:start position:0% pass key to a passform manager you have 00:16:07.720 --> 00:16:11.590 align:start position:0% pass key to a passform manager you have known<00:16:08.720> which<00:16:08.839> is<00:16:09.240> completely<00:16:09.639> the<00:16:09.839> expected 00:16:11.590 --> 00:16:11.600 align:start position:0% known which is completely the expected 00:16:11.600 --> 00:16:14.550 align:start position:0% known which is completely the expected result<00:16:12.600> so<00:16:13.040> to<00:16:13.240> summarize<00:16:13.800> this<00:16:13.959> is<00:16:14.240> where<00:16:14.440> we 00:16:14.550 --> 00:16:14.560 align:start position:0% result so to summarize this is where we 00:16:14.560 --> 00:16:16.910 align:start position:0% result so to summarize this is where we are<00:16:14.759> today<00:16:15.120> on<00:16:15.440> smartphones<00:16:16.440> we<00:16:16.600> have<00:16:16.720> to 00:16:16.910 --> 00:16:16.920 align:start position:0% are today on smartphones we have to 00:16:16.920 --> 00:16:19.910 align:start position:0% are today on smartphones we have to choose<00:16:17.240> between<00:16:17.600> secure<00:16:17.959> credentials<00:16:18.920> or 00:16:19.910 --> 00:16:19.920 align:start position:0% choose between secure credentials or 00:16:19.920 --> 00:16:22.189 align:start position:0% choose between secure credentials or back<00:16:20.199> synchron<00:16:20.759> or<00:16:20.959> backup<00:16:21.519> credentials 00:16:22.189 --> 00:16:22.199 align:start position:0% back synchron or backup credentials 00:16:22.199 --> 00:16:24.590 align:start position:0% back synchron or backup credentials which<00:16:22.480> might<00:16:22.720> not<00:16:22.959> be<00:16:23.360> a<00:16:23.639> right<00:16:24.000> a<00:16:24.160> good<00:16:24.360> thing 00:16:24.590 --> 00:16:24.600 align:start position:0% which might not be a right a good thing 00:16:24.600 --> 00:16:27.389 align:start position:0% which might not be a right a good thing because<00:16:24.800> you<00:16:24.880> want<00:16:25.240> both<00:16:26.240> so<00:16:26.800> the<00:16:26.959> pass<00:16:27.199> keys 00:16:27.389 --> 00:16:27.399 align:start position:0% because you want both so the pass keys 00:16:27.399 --> 00:16:29.829 align:start position:0% because you want both so the pass keys are<00:16:27.519> under<00:16:28.040> by<00:16:28.199> the<00:16:28.319> application<00:16:28.920> processor 00:16:29.829 --> 00:16:29.839 align:start position:0% are under by the application processor 00:16:29.839 --> 00:16:32.430 align:start position:0% are under by the application processor it's<00:16:30.120> there<00:16:30.519> easy<00:16:30.759> to<00:16:30.959> extract<00:16:31.360> by<00:16:31.560> a<00:16:31.680> malware 00:16:32.430 --> 00:16:32.440 align:start position:0% it's there easy to extract by a malware 00:16:32.440 --> 00:16:34.150 align:start position:0% it's there easy to extract by a malware when<00:16:32.600> the<00:16:32.759> device<00:16:33.040> is<00:16:33.199> unlocked<00:16:33.839> and<00:16:34.040> there 00:16:34.150 --> 00:16:34.160 align:start position:0% when the device is unlocked and there 00:16:34.160 --> 00:16:36.670 align:start position:0% when the device is unlocked and there are<00:16:34.360> physical<00:16:34.800> attacks<00:16:35.560> applicable<00:16:36.399> which<00:16:36.519> is 00:16:36.670 --> 00:16:36.680 align:start position:0% are physical attacks applicable which is 00:16:36.680 --> 00:16:39.189 align:start position:0% are physical attacks applicable which is probably<00:16:37.079> the<00:16:37.199> worst<00:16:37.519> part<00:16:38.199> because 00:16:39.189 --> 00:16:39.199 align:start position:0% probably the worst part because 00:16:39.199 --> 00:16:40.949 align:start position:0% probably the worst part because something<00:16:39.759> might<00:16:39.959> be<00:16:40.120> able<00:16:40.319> to<00:16:40.480> dump<00:16:40.759> those 00:16:40.949 --> 00:16:40.959 align:start position:0% something might be able to dump those 00:16:40.959 --> 00:16:43.509 align:start position:0% something might be able to dump those keys<00:16:41.279> at<00:16:41.399> a<00:16:41.519> later<00:16:41.880> stage<00:16:42.600> so<00:16:42.800> user<00:16:43.120> pres 00:16:43.509 --> 00:16:43.519 align:start position:0% keys at a later stage so user pres 00:16:43.519 --> 00:16:45.629 align:start position:0% keys at a later stage so user pres enforcement<00:16:44.240> is<00:16:44.399> not<00:16:44.560> really<00:16:44.920> linked<00:16:45.319> to 00:16:45.629 --> 00:16:45.639 align:start position:0% enforcement is not really linked to 00:16:45.639 --> 00:16:49.829 align:start position:0% enforcement is not really linked to usage<00:16:46.120> of<00:16:46.279> the<00:16:46.480> key<00:16:47.319> and<00:16:47.720> ninka<00:16:48.480> pass<00:16:48.839> Keys 00:16:49.829 --> 00:16:49.839 align:start position:0% usage of the key and ninka pass Keys 00:16:49.839 --> 00:16:51.550 align:start position:0% usage of the key and ninka pass Keys things<00:16:50.120> doesn't<00:16:50.399> change<00:16:50.839> there<00:16:51.319> they<00:16:51.399> are 00:16:51.550 --> 00:16:51.560 align:start position:0% things doesn't change there they are 00:16:51.560 --> 00:16:52.710 align:start position:0% things doesn't change there they are still<00:16:51.800> very 00:16:52.710 --> 00:16:52.720 align:start position:0% still very 00:16:52.720 --> 00:16:55.550 align:start position:0% still very secure<00:16:53.720> so<00:16:54.079> we<00:16:54.199> can<00:16:54.440> wonder<00:16:54.800> who<00:16:55.000> did<00:16:55.160> we<00:16:55.319> get 00:16:55.550 --> 00:16:55.560 align:start position:0% secure so we can wonder who did we get 00:16:55.560 --> 00:16:59.309 align:start position:0% secure so we can wonder who did we get there<00:16:56.440> um<00:16:56.880> one<00:16:57.720> one<00:16:58.000> way<00:16:58.160> to<00:16:58.319> say<00:16:58.560> that<00:16:59.079> that 00:16:59.309 --> 00:16:59.319 align:start position:0% there um one one way to say that that 00:16:59.319 --> 00:17:01.030 align:start position:0% there um one one way to say that that well<00:16:59.519> we<00:16:59.680> have<00:16:59.920> conflicting<00:17:00.399> rules<00:17:00.800> between 00:17:01.030 --> 00:17:01.040 align:start position:0% well we have conflicting rules between 00:17:01.040 --> 00:17:04.150 align:start position:0% well we have conflicting rules between the<00:17:01.160> vendors<00:17:02.160> so<00:17:02.440> Google<00:17:03.199> says<00:17:03.639> that<00:17:03.800> you<00:17:03.959> can 00:17:04.150 --> 00:17:04.160 align:start position:0% the vendors so Google says that you can 00:17:04.160 --> 00:17:06.270 align:start position:0% the vendors so Google says that you can inject<00:17:04.480> a<00:17:04.640> key<00:17:04.839> into<00:17:05.079> the<00:17:05.199> enclave<00:17:05.799> and<00:17:05.959> apple 00:17:06.270 --> 00:17:06.280 align:start position:0% inject a key into the enclave and apple 00:17:06.280 --> 00:17:08.429 align:start position:0% inject a key into the enclave and apple says<00:17:06.600> that<00:17:06.880> this<00:17:07.000> is<00:17:07.199> absolutely<00:17:07.640> forbidden 00:17:08.429 --> 00:17:08.439 align:start position:0% says that this is absolutely forbidden 00:17:08.439 --> 00:17:10.510 align:start position:0% says that this is absolutely forbidden you<00:17:08.600> cannot<00:17:08.919> inject<00:17:09.199> a<00:17:09.360> key<00:17:09.520> Into<00:17:09.679> The<00:17:09.799> Enclave 00:17:10.510 --> 00:17:10.520 align:start position:0% you cannot inject a key Into The Enclave 00:17:10.520 --> 00:17:12.110 align:start position:0% you cannot inject a key Into The Enclave so<00:17:10.679> this<00:17:10.880> might<00:17:11.039> be<00:17:11.280> the<00:17:11.480> reason<00:17:11.839> why<00:17:11.959> the 00:17:12.110 --> 00:17:12.120 align:start position:0% so this might be the reason why the 00:17:12.120 --> 00:17:13.909 align:start position:0% so this might be the reason why the Enclave<00:17:12.559> were<00:17:12.760> not<00:17:12.919> modified<00:17:13.400> and<00:17:13.520> not<00:17:13.679> used 00:17:13.909 --> 00:17:13.919 align:start position:0% Enclave were not modified and not used 00:17:13.919 --> 00:17:16.549 align:start position:0% Enclave were not modified and not used in<00:17:14.079> that<00:17:14.280> case<00:17:15.240> and<00:17:15.520> all<00:17:15.760> agree<00:17:16.079> that<00:17:16.240> the<00:17:16.360> key 00:17:16.549 --> 00:17:16.559 align:start position:0% in that case and all agree that the key 00:17:16.559 --> 00:17:18.270 align:start position:0% in that case and all agree that the key cannot<00:17:16.839> be<00:17:16.959> exported<00:17:17.400> from<00:17:17.520> The<00:17:17.640> Enclave<00:17:18.120> so 00:17:18.270 --> 00:17:18.280 align:start position:0% cannot be exported from The Enclave so 00:17:18.280 --> 00:17:19.829 align:start position:0% cannot be exported from The Enclave so that's<00:17:18.480> another<00:17:18.760> good<00:17:18.959> reason<00:17:19.319> why<00:17:19.480> it's<00:17:19.640> not 00:17:19.829 --> 00:17:19.839 align:start position:0% that's another good reason why it's not 00:17:19.839 --> 00:17:24.669 align:start position:0% that's another good reason why it's not implemented<00:17:20.400> that<00:17:20.799> way<00:17:21.799> uh<00:17:22.280> so<00:17:22.720> Pho<00:17:23.280> says<00:17:23.919> Pho 00:17:24.669 --> 00:17:24.679 align:start position:0% implemented that way uh so Pho says Pho 00:17:24.679 --> 00:17:27.710 align:start position:0% implemented that way uh so Pho says Pho introduced<00:17:25.679> um<00:17:25.880> some<00:17:26.679> Enterprise<00:17:27.480> some 00:17:27.710 --> 00:17:27.720 align:start position:0% introduced um some Enterprise some 00:17:27.720 --> 00:17:29.270 align:start position:0% introduced um some Enterprise some difference<00:17:28.160> between<00:17:28.400> Enterprise<00:17:29.080> and 00:17:29.270 --> 00:17:29.280 align:start position:0% difference between Enterprise and 00:17:29.280 --> 00:17:31.669 align:start position:0% difference between Enterprise and customer<00:17:29.679> pass<00:17:29.919> keys<00:17:30.360> so<00:17:30.600> this<00:17:30.799> can<00:17:31.000> be 00:17:31.669 --> 00:17:31.679 align:start position:0% customer pass keys so this can be 00:17:31.679 --> 00:17:33.510 align:start position:0% customer pass keys so this can be another<00:17:32.080> sign<00:17:32.440> that<00:17:32.600> things<00:17:32.840> are<00:17:33.000> not<00:17:33.200> get 00:17:33.510 --> 00:17:33.520 align:start position:0% another sign that things are not get 00:17:33.520 --> 00:17:36.350 align:start position:0% another sign that things are not get very<00:17:33.799> very<00:17:34.039> well<00:17:34.840> uh<00:17:35.000> if<00:17:35.120> we<00:17:35.320> wonder<00:17:36.000> what<00:17:36.160> will 00:17:36.350 --> 00:17:36.360 align:start position:0% very very well uh if we wonder what will 00:17:36.360 --> 00:17:38.470 align:start position:0% very very well uh if we wonder what will happen<00:17:36.600> in<00:17:36.720> the<00:17:36.919> future<00:17:37.720> it's<00:17:37.919> not<00:17:38.120> going<00:17:38.320> to 00:17:38.470 --> 00:17:38.480 align:start position:0% happen in the future it's not going to 00:17:38.480 --> 00:17:41.789 align:start position:0% happen in the future it's not going to change<00:17:38.840> much<00:17:39.559> because<00:17:40.000> here<00:17:40.640> we<00:17:40.799> have<00:17:41.080> a<00:17:41.280> draft 00:17:41.789 --> 00:17:41.799 align:start position:0% change much because here we have a draft 00:17:41.799 --> 00:17:43.750 align:start position:0% change much because here we have a draft regarding<00:17:42.240> the<00:17:42.400> synchronization<00:17:43.120> protocol 00:17:43.750 --> 00:17:43.760 align:start position:0% regarding the synchronization protocol 00:17:43.760 --> 00:17:46.110 align:start position:0% regarding the synchronization protocol which<00:17:43.960> is<00:17:44.679> which<00:17:44.960> does<00:17:45.160> not<00:17:45.360> describe<00:17:45.799> how<00:17:46.000> the 00:17:46.110 --> 00:17:46.120 align:start position:0% which is which does not describe how the 00:17:46.120 --> 00:17:48.470 align:start position:0% which is which does not describe how the key<00:17:46.320> is<00:17:46.440> used<00:17:47.200> uh<00:17:47.360> if<00:17:47.440> we<00:17:47.600> want<00:17:47.799> to<00:17:47.960> add<00:17:48.120> a<00:17:48.240> trust 00:17:48.470 --> 00:17:48.480 align:start position:0% key is used uh if we want to add a trust 00:17:48.480 --> 00:17:50.510 align:start position:0% key is used uh if we want to add a trust on<00:17:48.679> core<00:17:48.919> to<00:17:49.039> the<00:17:49.200> key<00:17:49.440> so<00:17:49.640> if<00:17:49.760> you<00:17:49.960> want<00:17:50.280> if<00:17:50.360> we 00:17:50.510 --> 00:17:50.520 align:start position:0% on core to the key so if you want if we 00:17:50.520 --> 00:17:52.669 align:start position:0% on core to the key so if you want if we want<00:17:50.679> to<00:17:50.880> link<00:17:51.240> a<00:17:51.440> device<00:17:51.840> Bond<00:17:52.200> Pass<00:17:52.400> key<00:17:52.559> to 00:17:52.669 --> 00:17:52.679 align:start position:0% want to link a device Bond Pass key to 00:17:52.679 --> 00:17:54.830 align:start position:0% want to link a device Bond Pass key to the<00:17:52.880> key<00:17:53.440> there<00:17:53.559> were<00:17:53.720> a<00:17:53.840> few<00:17:54.039> extension<00:17:54.520> to<00:17:54.679> do 00:17:54.830 --> 00:17:54.840 align:start position:0% the key there were a few extension to do 00:17:54.840 --> 00:17:56.990 align:start position:0% the key there were a few extension to do that<00:17:55.039> and<00:17:55.159> they<00:17:55.280> were<00:17:55.480> finally<00:17:55.840> dropped<00:17:56.840> and 00:17:56.990 --> 00:17:57.000 align:start position:0% that and they were finally dropped and 00:17:57.000 --> 00:17:59.590 align:start position:0% that and they were finally dropped and in<00:17:57.159> the<00:17:57.320> end<00:17:57.880> well<00:17:58.159> if<00:17:58.280> we<00:17:58.400> want<00:17:58.559> a<00:17:58.840> better<00:17:59.159> ux 00:17:59.590 --> 00:17:59.600 align:start position:0% in the end well if we want a better ux 00:17:59.600 --> 00:18:03.149 align:start position:0% in the end well if we want a better ux for<00:17:59.880> pasis<00:18:00.880> um<00:18:01.159> this<00:18:01.320> is<00:18:01.679> also<00:18:02.600> going<00:18:02.840> to<00:18:03.000> be 00:18:03.149 --> 00:18:03.159 align:start position:0% for pasis um this is also going to be 00:18:03.159 --> 00:18:05.270 align:start position:0% for pasis um this is also going to be dropped<00:18:03.840> so<00:18:04.120> we<00:18:04.280> had<00:18:04.480> three<00:18:04.840> possible 00:18:05.270 --> 00:18:05.280 align:start position:0% dropped so we had three possible 00:18:05.280 --> 00:18:08.029 align:start position:0% dropped so we had three possible Improvement<00:18:06.240> protocols<00:18:06.880> that<00:18:07.120> were<00:18:07.400> dropped 00:18:08.029 --> 00:18:08.039 align:start position:0% Improvement protocols that were dropped 00:18:08.039 --> 00:18:09.710 align:start position:0% Improvement protocols that were dropped so<00:18:08.240> we<00:18:08.400> can't<00:18:08.679> think<00:18:08.880> we<00:18:08.960> can<00:18:09.159> think<00:18:09.440> that<00:18:09.559> this 00:18:09.710 --> 00:18:09.720 align:start position:0% so we can't think we can think that this 00:18:09.720 --> 00:18:12.070 align:start position:0% so we can't think we can think that this is<00:18:09.840> not<00:18:10.000> going<00:18:10.159> to<00:18:10.320> change<00:18:10.640> much<00:18:11.640> uh<00:18:11.880> if<00:18:12.000> you 00:18:12.070 --> 00:18:12.080 align:start position:0% is not going to change much uh if you 00:18:12.080 --> 00:18:13.470 align:start position:0% is not going to change much uh if you are<00:18:12.280> disappointed<00:18:12.880> by<00:18:13.080> platform 00:18:13.470 --> 00:18:13.480 align:start position:0% are disappointed by platform 00:18:13.480 --> 00:18:16.070 align:start position:0% are disappointed by platform authenticator<00:18:14.480> you<00:18:14.640> can<00:18:14.880> always<00:18:15.159> rely<00:18:15.640> on 00:18:16.070 --> 00:18:16.080 align:start position:0% authenticator you can always rely on 00:18:16.080 --> 00:18:18.789 align:start position:0% authenticator you can always rely on external<00:18:17.080> pasy<00:18:17.520> implementations<00:18:18.480> so<00:18:18.640> I 00:18:18.789 --> 00:18:18.799 align:start position:0% external pasy implementations so I 00:18:18.799 --> 00:18:20.669 align:start position:0% external pasy implementations so I listed<00:18:19.120> a<00:18:19.240> few<00:18:19.440> Open<00:18:19.679> Source<00:18:19.919> One<00:18:20.240> the<00:18:20.440> good 00:18:20.669 --> 00:18:20.679 align:start position:0% listed a few Open Source One the good 00:18:20.679 --> 00:18:22.350 align:start position:0% listed a few Open Source One the good news<00:18:20.960> is<00:18:21.120> that<00:18:21.280> you<00:18:21.400> can<00:18:21.600> use<00:18:21.799> your<00:18:21.960> favorite 00:18:22.350 --> 00:18:22.360 align:start position:0% news is that you can use your favorite 00:18:22.360 --> 00:18:24.549 align:start position:0% news is that you can use your favorite hardw<00:18:22.799> wallet<00:18:23.120> if<00:18:23.240> you<00:18:23.360> want<00:18:24.240> um<00:18:24.440> the 00:18:24.549 --> 00:18:24.559 align:start position:0% hardw wallet if you want um the 00:18:24.559 --> 00:18:26.630 align:start position:0% hardw wallet if you want um the application<00:18:25.000> is<00:18:25.159> open<00:18:25.480> source<00:18:25.960> and<00:18:26.200> you<00:18:26.360> get<00:18:26.480> a 00:18:26.630 --> 00:18:26.640 align:start position:0% application is open source and you get a 00:18:26.640 --> 00:18:30.190 align:start position:0% application is open source and you get a backup<00:18:27.520> Pass<00:18:27.840> key<00:18:28.400> so<00:18:28.559> it<00:18:28.799> can<00:18:28.919> be<00:18:29.039> another 00:18:30.190 --> 00:18:30.200 align:start position:0% backup Pass key so it can be another 00:18:30.200 --> 00:18:33.430 align:start position:0% backup Pass key so it can be another option<00:18:31.200> what<00:18:31.360> happens<00:18:31.640> on<00:18:31.880> chain<00:18:32.880> well<00:18:33.159> I<00:18:33.280> have 00:18:33.430 --> 00:18:33.440 align:start position:0% option what happens on chain well I have 00:18:33.440 --> 00:18:35.470 align:start position:0% option what happens on chain well I have one<00:18:33.640> minute<00:18:33.919> so<00:18:34.159> maybe<00:18:34.559> I<00:18:34.640> will<00:18:35.000> I<00:18:35.080> will<00:18:35.280> go 00:18:35.470 --> 00:18:35.480 align:start position:0% one minute so maybe I will I will go 00:18:35.480 --> 00:18:38.510 align:start position:0% one minute so maybe I will I will go over<00:18:35.720> there<00:18:35.960> very<00:18:36.440> fast<00:18:37.440> cartridge<00:18:38.000> initiated 00:18:38.510 --> 00:18:38.520 align:start position:0% over there very fast cartridge initiated 00:18:38.520 --> 00:18:41.750 align:start position:0% over there very fast cartridge initiated the<00:18:38.679> move<00:18:39.080> on<00:18:39.440> stocket<00:18:40.440> so<00:18:40.919> paskis<00:18:41.360> are<00:18:41.520> now 00:18:41.750 --> 00:18:41.760 align:start position:0% the move on stocket so paskis are now 00:18:41.760 --> 00:18:43.190 align:start position:0% the move on stocket so paskis are now very<00:18:42.039> popular<00:18:42.559> because<00:18:42.799> we<00:18:42.919> have<00:18:43.080> been 00:18:43.190 --> 00:18:43.200 align:start position:0% very popular because we have been 00:18:43.200 --> 00:18:45.510 align:start position:0% very popular because we have been running<00:18:43.559> several<00:18:44.080> optimizations<00:18:45.080> in<00:18:45.200> order 00:18:45.510 --> 00:18:45.520 align:start position:0% running several optimizations in order 00:18:45.520 --> 00:18:47.669 align:start position:0% running several optimizations in order to<00:18:45.679> be<00:18:45.840> able<00:18:46.080> to<00:18:46.240> verify<00:18:46.720> pasis<00:18:47.120> and<00:18:47.280> chain 00:18:47.669 --> 00:18:47.679 align:start position:0% to be able to verify pasis and chain 00:18:47.679 --> 00:18:50.630 align:start position:0% to be able to verify pasis and chain very<00:18:48.120> efficiently<00:18:49.120> uh<00:18:49.480> I<00:18:49.600> have<00:18:49.720> a<00:18:49.840> few<00:18:50.080> canel<00:18:50.559> I 00:18:50.630 --> 00:18:50.640 align:start position:0% very efficiently uh I have a few canel I 00:18:50.640 --> 00:18:53.390 align:start position:0% very efficiently uh I have a few canel I have<00:18:50.799> listed<00:18:51.120> a<00:18:51.280> few<00:18:51.520> canels<00:18:52.480> that<00:18:52.600> you<00:18:52.799> can 00:18:53.390 --> 00:18:53.400 align:start position:0% have listed a few canels that you can 00:18:53.400 --> 00:18:56.630 align:start position:0% have listed a few canels that you can use<00:18:53.880> to<00:18:54.880> check<00:18:55.280> to<00:18:55.480> to<00:18:55.600> use<00:18:55.840> with<00:18:56.080> Pass<00:18:56.280> key<00:18:56.480> so 00:18:56.630 --> 00:18:56.640 align:start position:0% use to check to to use with Pass key so 00:18:56.640 --> 00:18:59.190 align:start position:0% use to check to to use with Pass key so zero<00:18:57.000> da<00:18:57.520> safe<00:18:57.880> core<00:18:58.200> or<00:18:58.360> coinbase<00:18:58.799> smart 00:18:59.190 --> 00:18:59.200 align:start position:0% zero da safe core or coinbase smart 00:18:59.200 --> 00:19:01.830 align:start position:0% zero da safe core or coinbase smart wallet<00:19:00.200> uh<00:19:00.440> here's<00:19:00.679> the<00:19:00.840> main<00:19:01.159> difference<00:19:01.760> I 00:19:01.830 --> 00:19:01.840 align:start position:0% wallet uh here's the main difference I 00:19:01.840 --> 00:19:03.950 align:start position:0% wallet uh here's the main difference I will<00:19:02.080> just<00:19:02.280> look<00:19:02.440> at<00:19:02.640> who<00:19:02.880> they<00:19:03.080> using<00:19:03.360> Pas<00:19:03.679> key 00:19:03.950 --> 00:19:03.960 align:start position:0% will just look at who they using Pas key 00:19:03.960 --> 00:19:06.070 align:start position:0% will just look at who they using Pas key you<00:19:04.120> make<00:19:04.360> no<00:19:04.600> difference<00:19:05.080> with<00:19:05.200> a<00:19:05.760> common 00:19:06.070 --> 00:19:06.080 align:start position:0% you make no difference with a common 00:19:06.080 --> 00:19:08.950 align:start position:0% you make no difference with a common credential<00:19:06.559> on<00:19:06.760> zero<00:19:07.080> Dev<00:19:07.760> on<00:19:08.000> safe<00:19:08.320> core<00:19:08.640> Pass 00:19:08.950 --> 00:19:08.960 align:start position:0% credential on zero Dev on safe core Pass 00:19:08.960 --> 00:19:12.270 align:start position:0% credential on zero Dev on safe core Pass Key<00:19:09.400> are<00:19:10.000> are<00:19:10.240> supported<00:19:10.960> but<00:19:11.240> but<00:19:11.440> discourage 00:19:12.270 --> 00:19:12.280 align:start position:0% Key are are supported but but discourage 00:19:12.280 --> 00:19:13.990 align:start position:0% Key are are supported but but discourage if<00:19:12.360> you<00:19:12.480> look<00:19:12.600> at<00:19:12.720> the<00:19:12.919> specification<00:19:13.679> safe 00:19:13.990 --> 00:19:14.000 align:start position:0% if you look at the specification safe 00:19:14.000 --> 00:19:15.430 align:start position:0% if you look at the specification safe core<00:19:14.240> will<00:19:14.400> tell<00:19:14.559> you<00:19:14.840> it's<00:19:15.000> better<00:19:15.240> to 00:19:15.430 --> 00:19:15.440 align:start position:0% core will tell you it's better to 00:19:15.440 --> 00:19:17.190 align:start position:0% core will tell you it's better to associate<00:19:15.799> the<00:19:15.960> pace<00:19:16.240> key<00:19:16.400> with<00:19:16.520> a<00:19:16.799> the<00:19:16.960> pass 00:19:17.190 --> 00:19:17.200 align:start position:0% associate the pace key with a the pass 00:19:17.200 --> 00:19:19.669 align:start position:0% associate the pace key with a the pass key<00:19:17.360> with<00:19:17.440> a<00:19:17.600> regular<00:19:18.280> credential<00:19:19.280> and<00:19:19.440> if<00:19:19.559> you 00:19:19.669 --> 00:19:19.679 align:start position:0% key with a regular credential and if you 00:19:19.679 --> 00:19:21.789 align:start position:0% key with a regular credential and if you want<00:19:19.840> to<00:19:19.960> run<00:19:20.159> it<00:19:20.280> on<00:19:20.440> coinbase<00:19:20.840> Smart<00:19:21.120> wallet 00:19:21.789 --> 00:19:21.799 align:start position:0% want to run it on coinbase Smart wallet 00:19:21.799 --> 00:19:24.230 align:start position:0% want to run it on coinbase Smart wallet they<00:19:22.000> support<00:19:22.400> Pass<00:19:22.640> Key<00:19:22.960> they<00:19:23.159> also<00:19:23.440> support 00:19:24.230 --> 00:19:24.240 align:start position:0% they support Pass Key they also support 00:19:24.240 --> 00:19:26.870 align:start position:0% they support Pass Key they also support regular<00:19:24.720> signatures<00:19:25.679> and<00:19:25.880> they<00:19:26.039> will<00:19:26.440> pumpt 00:19:26.870 --> 00:19:26.880 align:start position:0% regular signatures and they will pumpt 00:19:26.880 --> 00:19:29.230 align:start position:0% regular signatures and they will pumpt you<00:19:27.400> and<00:19:27.600> tell<00:19:27.840> you<00:19:28.159> yeah<00:19:28.360> you<00:19:28.480> might<00:19:28.760> might 00:19:29.230 --> 00:19:29.240 align:start position:0% you and tell you yeah you might might 00:19:29.240 --> 00:19:32.830 align:start position:0% you and tell you yeah you might might want<00:19:29.600> to<00:19:29.799> use<00:19:29.960> a<00:19:30.159> recovery<00:19:31.039> key<00:19:32.039> so<00:19:32.320> the<00:19:32.520> answer 00:19:32.830 --> 00:19:32.840 align:start position:0% want to use a recovery key so the answer 00:19:32.840 --> 00:19:35.669 align:start position:0% want to use a recovery key so the answer to<00:19:33.039> the<00:19:34.039> maybe<00:19:34.320> burning<00:19:34.799> question<00:19:35.200> should<00:19:35.480> we 00:19:35.669 --> 00:19:35.679 align:start position:0% to the maybe burning question should we 00:19:35.679 --> 00:19:38.710 align:start position:0% to the maybe burning question should we should<00:19:35.880> we<00:19:36.080> drop<00:19:36.440> P<00:19:36.720> keys<00:19:37.120> in<00:19:37.280> my<00:19:37.480> opinion<00:19:38.120> no 00:19:38.710 --> 00:19:38.720 align:start position:0% should we drop P keys in my opinion no 00:19:38.720 --> 00:19:40.470 align:start position:0% should we drop P keys in my opinion no because<00:19:39.000> they<00:19:39.159> still<00:19:39.360> offer<00:19:39.720> the<00:19:39.919> best<00:19:40.159> way<00:19:40.320> to 00:19:40.470 --> 00:19:40.480 align:start position:0% because they still offer the best way to 00:19:40.480 --> 00:19:42.549 align:start position:0% because they still offer the best way to onboard<00:19:41.000> people<00:19:41.799> but<00:19:41.960> we<00:19:42.080> have<00:19:42.200> to<00:19:42.360> think 00:19:42.549 --> 00:19:42.559 align:start position:0% onboard people but we have to think 00:19:42.559 --> 00:19:44.070 align:start position:0% onboard people but we have to think about<00:19:42.760> the<00:19:42.880> threat<00:19:43.200> model<00:19:43.559> and<00:19:43.679> we<00:19:43.799> have<00:19:43.919> to 00:19:44.070 --> 00:19:44.080 align:start position:0% about the threat model and we have to 00:19:44.080 --> 00:19:46.630 align:start position:0% about the threat model and we have to code<00:19:44.520> accordingly<00:19:45.520> and<00:19:45.679> one<00:19:45.880> thing<00:19:46.120> we<00:19:46.240> can<00:19:46.400> do 00:19:46.630 --> 00:19:46.640 align:start position:0% code accordingly and one thing we can do 00:19:46.640 --> 00:19:49.470 align:start position:0% code accordingly and one thing we can do since<00:19:46.880> we<00:19:47.000> have<00:19:47.200> Smart<00:19:47.520> contracts<00:19:48.520> uh<00:19:48.679> we<00:19:48.880> can 00:19:49.470 --> 00:19:49.480 align:start position:0% since we have Smart contracts uh we can 00:19:49.480 --> 00:19:52.110 align:start position:0% since we have Smart contracts uh we can associate<00:19:50.120> less<00:19:50.480> privilege<00:19:51.000> to<00:19:51.480> pass<00:19:51.720> keys 00:19:52.110 --> 00:19:52.120 align:start position:0% associate less privilege to pass keys 00:19:52.120 --> 00:19:55.029 align:start position:0% associate less privilege to pass keys that<00:19:52.280> are<00:19:52.480> not<00:19:53.400> U<00:19:53.559> that<00:19:53.679> are<00:19:53.840> syncable<00:19:54.720> because 00:19:55.029 --> 00:19:55.039 align:start position:0% that are not U that are syncable because 00:19:55.039 --> 00:19:57.510 align:start position:0% that are not U that are syncable because since<00:19:55.320> we<00:19:55.480> know<00:19:55.919> that<00:19:56.120> syncable<00:19:56.679> P<00:19:56.919> keys<00:19:57.200> are 00:19:57.510 --> 00:19:57.520 align:start position:0% since we know that syncable P keys are 00:19:57.520 --> 00:19:59.990 align:start position:0% since we know that syncable P keys are way<00:19:57.799> less<00:19:58.039> secure<00:19:58.840> than<00:19:59.240> pass<00:19:59.520> keys<00:19:59.760> that<00:19:59.880> are 00:19:59.990 --> 00:20:00.000 align:start position:0% way less secure than pass keys that are 00:20:00.000 --> 00:20:02.230 align:start position:0% way less secure than pass keys that are handled<00:20:00.360> by<00:20:00.480> the<00:20:00.640> device<00:20:01.280> we<00:20:01.400> can<00:20:01.600> use<00:20:01.919> them 00:20:02.230 --> 00:20:02.240 align:start position:0% handled by the device we can use them 00:20:02.240 --> 00:20:04.470 align:start position:0% handled by the device we can use them with<00:20:02.480> kotas<00:20:03.039> we<00:20:03.159> can<00:20:03.320> use<00:20:03.559> them<00:20:03.799> for<00:20:04.000> example 00:20:04.470 --> 00:20:04.480 align:start position:0% with kotas we can use them for example 00:20:04.480 --> 00:20:08.669 align:start position:0% with kotas we can use them for example for<00:20:05.200> Less<00:20:05.840> M<00:20:06.120> for<00:20:06.400> less<00:20:06.840> amount<00:20:07.520> of<00:20:07.760> assets<00:20:08.400> and 00:20:08.669 --> 00:20:08.679 align:start position:0% for Less M for less amount of assets and 00:20:08.679 --> 00:20:10.630 align:start position:0% for Less M for less amount of assets and then<00:20:08.960> we<00:20:09.120> have<00:20:09.280> something<00:20:09.720> that<00:20:09.840> is 00:20:10.630 --> 00:20:10.640 align:start position:0% then we have something that is 00:20:10.640 --> 00:20:12.750 align:start position:0% then we have something that is acceptable<00:20:11.640> but<00:20:11.840> the<00:20:12.000> most<00:20:12.200> important<00:20:12.600> thing 00:20:12.750 --> 00:20:12.760 align:start position:0% acceptable but the most important thing 00:20:12.760 --> 00:20:15.710 align:start position:0% acceptable but the most important thing is<00:20:12.880> to<00:20:13.039> know<00:20:13.240> the<00:20:13.360> threet<00:20:13.960> and<00:20:14.600> act 00:20:15.710 --> 00:20:15.720 align:start position:0% is to know the threet and act 00:20:15.720 --> 00:20:18.029 align:start position:0% is to know the threet and act accordingly<00:20:16.720> we<00:20:16.840> are<00:20:17.000> finished<00:20:17.440> so<00:20:17.640> I<00:20:17.720> will 00:20:18.029 --> 00:20:18.039 align:start position:0% accordingly we are finished so I will 00:20:18.039 --> 00:20:20.230 align:start position:0% accordingly we are finished so I will just<00:20:18.240> let<00:20:18.559> you<00:20:18.799> with<00:20:19.120> one<00:20:19.440> last<00:20:19.679> meme<00:20:19.960> for<00:20:20.120> the 00:20:20.230 --> 00:20:20.240 align:start position:0% just let you with one last meme for the 00:20:20.240 --> 00:20:22.390 align:start position:0% just let you with one last meme for the road<00:20:21.000> um<00:20:21.200> this<00:20:21.320> is<00:20:21.480> the<00:20:21.679> difference<00:20:22.080> between 00:20:22.390 --> 00:20:22.400 align:start position:0% road um this is the difference between 00:20:22.400 --> 00:20:23.950 align:start position:0% road um this is the difference between 2014<00:20:23.159> and 00:20:23.950 --> 00:20:23.960 align:start position:0% 2014 and 00:20:23.960 --> 00:20:26.590 align:start position:0% 2014 and 2024<00:20:24.960> we<00:20:25.120> get<00:20:25.280> rid<00:20:25.480> of<00:20:25.640> password<00:20:26.080> by<00:20:26.200> storing 00:20:26.590 --> 00:20:26.600 align:start position:0% 2024 we get rid of password by storing 00:20:26.600 --> 00:20:28.789 align:start position:0% 2024 we get rid of password by storing in<00:20:26.840> password<00:20:27.159> managers<00:20:28.120> might<00:20:28.280> not<00:20:28.440> be<00:20:28.720> the 00:20:28.789 --> 00:20:28.799 align:start position:0% in password managers might not be the 00:20:28.799 --> 00:20:30.549 align:start position:0% in password managers might not be the best<00:20:29.000> ID<00:20:29.400> I<00:20:29.480> will<00:20:29.679> let<00:20:29.799> you 00:20:30.549 --> 00:20:30.559 align:start position:0% best ID I will let you 00:20:30.559 --> 00:20:33.310 align:start position:0% best ID I will let you decide<00:20:31.559> you<00:20:31.679> can<00:20:31.880> reach<00:20:32.120> me<00:20:32.280> on<00:20:32.480> Twitter<00:20:33.159> and 00:20:33.310 --> 00:20:33.320 align:start position:0% decide you can reach me on Twitter and 00:20:33.320 --> 00:20:35.149 align:start position:0% decide you can reach me on Twitter and there<00:20:33.440> will<00:20:33.559> be<00:20:33.720> code<00:20:33.960> on<00:20:34.159> GitHub<00:20:34.600> to<00:20:34.760> describe 00:20:35.149 --> 00:20:35.159 align:start position:0% there will be code on GitHub to describe 00:20:35.159 --> 00:20:36.870 align:start position:0% there will be code on GitHub to describe all<00:20:35.440> this<00:20:35.679> so<00:20:35.880> that<00:20:36.000> you<00:20:36.080> can<00:20:36.240> run<00:20:36.480> it<00:20:36.640> on<00:20:36.760> your 00:20:36.870 --> 00:20:36.880 align:start position:0% all this so that you can run it on your 00:20:36.880 --> 00:20:38.789 align:start position:0% all this so that you can run it on your own<00:20:37.159> device<00:20:37.480> and<00:20:37.640> you<00:20:37.760> can<00:20:37.960> know<00:20:38.280> if<00:20:38.440> at<00:20:38.600> some 00:20:38.789 --> 00:20:38.799 align:start position:0% own device and you can know if at some 00:20:38.799 --> 00:20:41.789 align:start position:0% own device and you can know if at some point<00:20:39.080> the<00:20:39.200> implementation<00:20:39.919> gets<00:20:40.200> better<00:20:41.120> and 00:20:41.789 --> 00:20:41.799 align:start position:0% point the implementation gets better and 00:20:41.799 --> 00:20:43.669 align:start position:0% point the implementation gets better and well<00:20:42.000> the<00:20:42.200> less<00:20:42.480> ugly<00:20:42.840> solution<00:20:43.320> for<00:20:43.520> the 00:20:43.669 --> 00:20:43.679 align:start position:0% well the less ugly solution for the 00:20:43.679 --> 00:20:47.870 align:start position:0% well the less ugly solution for the synchronization<00:20:44.320> is<00:20:44.480> being<00:20:44.760> picked<00:20:45.280> thank 00:20:47.870 --> 00:20:47.880 align:start position:0% 00:20:47.880 --> 00:20:50.390 align:start position:0% you<00:20:48.880> all<00:20:49.120> right<00:20:49.400> thank<00:20:49.559> you<00:20:49.640> so<00:20:49.760> much<00:20:49.919> Nicholas 00:20:50.390 --> 00:20:50.400 align:start position:0% you all right thank you so much Nicholas 00:20:50.400 --> 00:20:52.470 align:start position:0% you all right thank you so much Nicholas that<00:20:50.480> was<00:20:50.600> a<00:20:50.799> very<00:20:51.640> entertaining<00:20:52.120> as<00:20:52.240> well<00:20:52.400> to 00:20:52.470 --> 00:20:52.480 align:start position:0% that was a very entertaining as well to 00:20:52.480 --> 00:20:54.669 align:start position:0% that was a very entertaining as well to see<00:20:52.679> some<00:20:52.840> memes<00:20:53.200> on<00:20:53.400> the<00:20:53.640> slide<00:20:54.000> so<00:20:54.159> I<00:20:54.360> really 00:20:54.669 --> 00:20:54.679 align:start position:0% see some memes on the slide so I really 00:20:54.679 --> 00:20:56.669 align:start position:0% see some memes on the slide so I really enjoy<00:20:55.120> that<00:20:55.760> um<00:20:55.880> we<00:20:55.960> do<00:20:56.080> have<00:20:56.200> a<00:20:56.320> couple<00:20:56.520> of 00:20:56.669 --> 00:20:56.679 align:start position:0% enjoy that um we do have a couple of 00:20:56.679 --> 00:20:59.549 align:start position:0% enjoy that um we do have a couple of questions<00:20:56.960> for<00:20:57.159> you<00:20:57.400> I<00:20:57.480> hope<00:20:57.600> you<00:20:57.679> don't<00:20:57.880> mind 00:20:59.549 --> 00:20:59.559 align:start position:0% questions for you I hope you don't mind 00:20:59.559 --> 00:21:01.310 align:start position:0% questions for you I hope you don't mind so<00:20:59.720> the<00:20:59.880> first<00:21:00.120> question<00:21:00.400> is<00:21:00.640> is<00:21:00.799> bit<00:21:01.000> Warden 00:21:01.310 --> 00:21:01.320 align:start position:0% so the first question is is bit Warden 00:21:01.320 --> 00:21:03.190 align:start position:0% so the first question is is bit Warden not<00:21:01.480> safe<00:21:01.760> generally<00:21:02.200> or<00:21:02.400> just<00:21:02.559> for<00:21:02.760> managing 00:21:03.190 --> 00:21:03.200 align:start position:0% not safe generally or just for managing 00:21:03.200 --> 00:21:06.230 align:start position:0% not safe generally or just for managing pass<00:21:03.480> Keys<00:21:04.240> uh<00:21:04.360> so<00:21:04.600> bit<00:21:04.880> Warden<00:21:05.280> is<00:21:05.520> is<00:21:05.640> he<00:21:05.960> safe 00:21:06.230 --> 00:21:06.240 align:start position:0% pass Keys uh so bit Warden is is he safe 00:21:06.240 --> 00:21:07.950 align:start position:0% pass Keys uh so bit Warden is is he safe for<00:21:06.559> password<00:21:06.880> manager<00:21:07.360> but<00:21:07.480> you<00:21:07.640> don't 00:21:07.950 --> 00:21:07.960 align:start position:0% for password manager but you don't 00:21:07.960 --> 00:21:09.669 align:start position:0% for password manager but you don't expect<00:21:08.240> the<00:21:08.400> same<00:21:08.679> security<00:21:09.120> to<00:21:09.320> handle 00:21:09.669 --> 00:21:09.679 align:start position:0% expect the same security to handle 00:21:09.679 --> 00:21:11.510 align:start position:0% expect the same security to handle password<00:21:10.039> and<00:21:10.120> to<00:21:10.240> handle<00:21:10.600> keys<00:21:11.039> so<00:21:11.240> that's 00:21:11.510 --> 00:21:11.520 align:start position:0% password and to handle keys so that's 00:21:11.520 --> 00:21:13.630 align:start position:0% password and to handle keys so that's why<00:21:11.960> I<00:21:12.039> think<00:21:12.240> it's<00:21:12.440> important<00:21:12.799> to<00:21:12.960> store<00:21:13.279> keys 00:21:13.630 --> 00:21:13.640 align:start position:0% why I think it's important to store keys 00:21:13.640 --> 00:21:16.029 align:start position:0% why I think it's important to store keys in<00:21:13.880> Hardware<00:21:14.400> because<00:21:15.159> if<00:21:15.279> you<00:21:15.480> consider<00:21:15.880> that 00:21:16.029 --> 00:21:16.039 align:start position:0% in Hardware because if you consider that 00:21:16.039 --> 00:21:18.269 align:start position:0% in Hardware because if you consider that a<00:21:16.200> key<00:21:16.360> is<00:21:16.440> a<00:21:16.640> password<00:21:17.480> you<00:21:17.600> lose<00:21:17.840> a<00:21:17.960> lot<00:21:18.080> of 00:21:18.269 --> 00:21:18.279 align:start position:0% a key is a password you lose a lot of 00:21:18.279 --> 00:21:20.710 align:start position:0% a key is a password you lose a lot of security<00:21:18.880> so<00:21:19.080> bit<00:21:19.320> Wen<00:21:19.679> is<00:21:19.919> reasonably<00:21:20.480> safe 00:21:20.710 --> 00:21:20.720 align:start position:0% security so bit Wen is reasonably safe 00:21:20.720 --> 00:21:22.310 align:start position:0% security so bit Wen is reasonably safe for<00:21:20.880> a<00:21:21.000> password<00:21:21.320> manager<00:21:21.760> but<00:21:21.880> of<00:21:22.039> course<00:21:22.200> you 00:21:22.310 --> 00:21:22.320 align:start position:0% for a password manager but of course you 00:21:22.320 --> 00:21:24.110 align:start position:0% for a password manager but of course you can<00:21:22.559> extract<00:21:23.039> anything<00:21:23.400> you<00:21:23.480> want<00:21:23.720> from<00:21:23.880> it 00:21:24.110 --> 00:21:24.120 align:start position:0% can extract anything you want from it 00:21:24.120 --> 00:21:26.789 align:start position:0% can extract anything you want from it because<00:21:24.400> this<00:21:24.520> is<00:21:24.640> the<00:21:24.760> way<00:21:24.919> they<00:21:25.600> work<00:21:26.600> all 00:21:26.789 --> 00:21:26.799 align:start position:0% because this is the way they work all 00:21:26.799 --> 00:21:28.590 align:start position:0% because this is the way they work all right<00:21:27.200> there's<00:21:27.520> one<00:21:27.720> that's<00:21:27.919> not<00:21:28.039> a<00:21:28.200> question 00:21:28.590 --> 00:21:28.600 align:start position:0% right there's one that's not a question 00:21:28.600 --> 00:21:30.950 align:start position:0% right there's one that's not a question but<00:21:28.760> thank<00:21:28.880> you<00:21:28.960> for<00:21:29.159> making<00:21:29.919> that<00:21:30.120> Big<00:21:30.320> W<00:21:30.600> pun 00:21:30.950 --> 00:21:30.960 align:start position:0% but thank you for making that Big W pun 00:21:30.960 --> 00:21:33.110 align:start position:0% but thank you for making that Big W pun it<00:21:31.039> was<00:21:31.279> brilliant<00:21:32.000> yeah<00:21:32.279> thank 00:21:33.110 --> 00:21:33.120 align:start position:0% it was brilliant yeah thank 00:21:33.120 --> 00:21:34.990 align:start position:0% it was brilliant yeah thank you<00:21:34.120> thank 00:21:34.990 --> 00:21:35.000 align:start position:0% you thank 00:21:35.000 --> 00:21:37.870 align:start position:0% you thank you<00:21:36.000> next<00:21:36.200> is<00:21:36.360> do<00:21:36.480> you<00:21:36.640> think<00:21:36.919> intentional 00:21:37.870 --> 00:21:37.880 align:start position:0% you next is do you think intentional 00:21:37.880 --> 00:21:39.750 align:start position:0% you next is do you think intentional intentional<00:21:38.480> security<00:21:38.919> lowering<00:21:39.480> of<00:21:39.600> the 00:21:39.750 --> 00:21:39.760 align:start position:0% intentional security lowering of the 00:21:39.760 --> 00:21:43.590 align:start position:0% intentional security lowering of the standard<00:21:40.159> could<00:21:40.320> be<00:21:40.520> a<00:21:41.200> dual<00:21:42.200> I<00:21:42.279> don't<00:21:42.919> like<00:21:43.480> oh 00:21:43.590 --> 00:21:43.600 align:start position:0% standard could be a dual I don't like oh 00:21:43.600 --> 00:21:45.230 align:start position:0% standard could be a dual I don't like oh yeah<00:21:43.840> yeah<00:21:43.960> yeah<00:21:44.080> I<00:21:44.159> see<00:21:44.360> I<00:21:44.440> see<00:21:44.679> the<00:21:44.799> reference 00:21:45.230 --> 00:21:45.240 align:start position:0% yeah yeah yeah I see I see the reference 00:21:45.240 --> 00:21:48.310 align:start position:0% yeah yeah yeah I see I see the reference so<00:21:45.440> thanks<00:21:45.640> for<00:21:45.840> making<00:21:46.200> it<00:21:46.919> no<00:21:47.279> I<00:21:47.400> think<00:21:47.640> it 00:21:48.310 --> 00:21:48.320 align:start position:0% so thanks for making it no I think it 00:21:48.320 --> 00:21:52.990 align:start position:0% so thanks for making it no I think it is<00:21:49.679> sorry<00:21:50.679> I<00:21:50.799> got<00:21:50.960> the<00:21:51.120> direction<00:21:51.559> wrong<00:21:52.000> sorry 00:21:52.990 --> 00:21:53.000 align:start position:0% is sorry I got the direction wrong sorry 00:21:53.000 --> 00:21:54.870 align:start position:0% is sorry I got the direction wrong sorry so<00:21:53.240> no<00:21:53.400> no<00:21:53.600> I<00:21:53.720> don't<00:21:53.919> think<00:21:54.240> I<00:21:54.320> don't<00:21:54.559> think<00:21:54.720> it 00:21:54.870 --> 00:21:54.880 align:start position:0% so no no I don't think I don't think it 00:21:54.880 --> 00:21:57.470 align:start position:0% so no no I don't think I don't think it is<00:21:55.159> I<00:21:55.279> don't<00:21:55.480> think<00:21:55.679> it<00:21:55.919> was<00:21:56.600> uh<00:21:57.039> I<00:21:57.159> don't<00:21:57.320> think 00:21:57.470 --> 00:21:57.480 align:start position:0% is I don't think it was uh I don't think 00:21:57.480 --> 00:21:59.230 align:start position:0% is I don't think it was uh I don't think it<00:21:57.600> was<00:21:57.880> pushed<00:21:58.159> by<00:21:58.279> the<00:21:58.600> government<00:21:59.000> I<00:21:59.120> think 00:21:59.230 --> 00:21:59.240 align:start position:0% it was pushed by the government I think 00:21:59.240 --> 00:22:02.310 align:start position:0% it was pushed by the government I think it<00:21:59.360> was<00:21:59.600> really<00:22:00.000> Choice<00:22:00.559> uh<00:22:00.679> to<00:22:00.919> make<00:22:01.279> the<00:22:01.600> ux 00:22:02.310 --> 00:22:02.320 align:start position:0% it was really Choice uh to make the ux 00:22:02.320 --> 00:22:05.909 align:start position:0% it was really Choice uh to make the ux easier<00:22:03.200> and<00:22:03.520> to<00:22:03.760> make<00:22:04.000> it<00:22:04.440> well<00:22:05.080> easier<00:22:05.640> again 00:22:05.909 --> 00:22:05.919 align:start position:0% easier and to make it well easier again 00:22:05.919 --> 00:22:09.710 align:start position:0% easier and to make it well easier again to<00:22:06.120> not<00:22:06.320> lose<00:22:06.720> private<00:22:07.080> Keys<00:22:07.799> um<00:22:08.000> so<00:22:08.679> the<00:22:08.880> defin 00:22:09.710 --> 00:22:09.720 align:start position:0% to not lose private Keys um so the defin 00:22:09.720 --> 00:22:11.669 align:start position:0% to not lose private Keys um so the defin definitely<00:22:10.240> is<00:22:10.400> a<00:22:10.559> fuse<00:22:10.880> was<00:22:11.039> a<00:22:11.159> driver<00:22:11.440> for 00:22:11.669 --> 00:22:11.679 align:start position:0% definitely is a fuse was a driver for 00:22:11.679 --> 00:22:13.110 align:start position:0% definitely is a fuse was a driver for that<00:22:11.840> in<00:22:12.000> my 00:22:13.110 --> 00:22:13.120 align:start position:0% that in my 00:22:13.120 --> 00:22:15.789 align:start position:0% that in my opinion<00:22:14.120> all<00:22:14.360> right<00:22:14.840> and<00:22:15.080> next<00:22:15.360> question<00:22:15.640> is 00:22:15.789 --> 00:22:15.799 align:start position:0% opinion all right and next question is 00:22:15.799 --> 00:22:17.070 align:start position:0% opinion all right and next question is what<00:22:15.880> do<00:22:16.000> you<00:22:16.120> think<00:22:16.240> of<00:22:16.360> spending<00:22:16.720> limits 00:22:17.070 --> 00:22:17.080 align:start position:0% what do you think of spending limits 00:22:17.080 --> 00:22:19.310 align:start position:0% what do you think of spending limits permission<00:22:17.559> management<00:22:18.520> what<00:22:18.640> should<00:22:18.799> I<00:22:19.000> use 00:22:19.310 --> 00:22:19.320 align:start position:0% permission management what should I use 00:22:19.320 --> 00:22:20.990 align:start position:0% permission management what should I use as<00:22:19.720> yeah<00:22:19.840> so<00:22:19.960> I<00:22:20.039> think<00:22:20.320> I<00:22:20.440> think<00:22:20.640> spending 00:22:20.990 --> 00:22:21.000 align:start position:0% as yeah so I think I think spending 00:22:21.000 --> 00:22:22.630 align:start position:0% as yeah so I think I think spending limits<00:22:21.320> and<00:22:21.520> permission<00:22:21.919> management<00:22:22.360> are 00:22:22.630 --> 00:22:22.640 align:start position:0% limits and permission management are 00:22:22.640 --> 00:22:24.950 align:start position:0% limits and permission management are definitely<00:22:23.039> a<00:22:23.200> good<00:22:23.400> way<00:22:23.559> to<00:22:23.679> deal<00:22:23.960> with<00:22:24.200> that 00:22:24.950 --> 00:22:24.960 align:start position:0% definitely a good way to deal with that 00:22:24.960 --> 00:22:27.190 align:start position:0% definitely a good way to deal with that and<00:22:25.320> what<00:22:25.440> should<00:22:25.600> I<00:22:25.760> use<00:22:25.960> as<00:22:26.080> a<00:22:26.240> wallet<00:22:26.720> so<00:22:27.120> I 00:22:27.190 --> 00:22:27.200 align:start position:0% and what should I use as a wallet so I 00:22:27.200 --> 00:22:30.110 align:start position:0% and what should I use as a wallet so I will<00:22:27.559> just<00:22:27.799> speak<00:22:28.120> about<00:22:28.720> wallet<00:22:29.360> Frameworks 00:22:30.110 --> 00:22:30.120 align:start position:0% will just speak about wallet Frameworks 00:22:30.120 --> 00:22:32.350 align:start position:0% will just speak about wallet Frameworks so<00:22:30.400> not<00:22:30.799> necessarily<00:22:31.520> not<00:22:31.760> necessarily 00:22:32.350 --> 00:22:32.360 align:start position:0% so not necessarily not necessarily 00:22:32.360 --> 00:22:34.950 align:start position:0% so not necessarily not necessarily wallets<00:22:32.720> but<00:22:32.840> for<00:22:33.039> wallet<00:22:33.320> Frameworks<00:22:34.200> any<00:22:34.760> we 00:22:34.950 --> 00:22:34.960 align:start position:0% wallets but for wallet Frameworks any we 00:22:34.960 --> 00:22:37.310 align:start position:0% wallets but for wallet Frameworks any we framework<00:22:35.400> that<00:22:35.559> will<00:22:35.760> support<00:22:36.159> this<00:22:36.559> is<00:22:36.799> good 00:22:37.310 --> 00:22:37.320 align:start position:0% framework that will support this is good 00:22:37.320 --> 00:22:39.390 align:start position:0% framework that will support this is good so<00:22:37.559> you<00:22:37.720> can<00:22:38.080> there<00:22:38.200> are<00:22:38.320> a<00:22:38.400> lot<00:22:38.600> of<00:22:38.760> them<00:22:39.039> I<00:22:39.279> I 00:22:39.390 --> 00:22:39.400 align:start position:0% so you can there are a lot of them I I 00:22:39.400 --> 00:22:40.990 align:start position:0% so you can there are a lot of them I I Nam<00:22:39.720> three<00:22:39.960> of<00:22:40.120> them<00:22:40.279> and<00:22:40.400> I<00:22:40.480> think<00:22:40.640> the<00:22:40.799> three 00:22:40.990 --> 00:22:41.000 align:start position:0% Nam three of them and I think the three 00:22:41.000 --> 00:22:43.190 align:start position:0% Nam three of them and I think the three of<00:22:41.120> them<00:22:41.279> are<00:22:41.480> good<00:22:41.679> to<00:22:42.240> manage<00:22:42.640> pass<00:22:42.880> keys<00:22:43.080> and 00:22:43.190 --> 00:22:43.200 align:start position:0% of them are good to manage pass keys and 00:22:43.200 --> 00:22:44.950 align:start position:0% of them are good to manage pass keys and to<00:22:43.320> manage<00:22:43.640> additional<00:22:44.120> permissions<00:22:44.600> on<00:22:44.799> top 00:22:44.950 --> 00:22:44.960 align:start position:0% to manage additional permissions on top 00:22:44.960 --> 00:22:45.710 align:start position:0% to manage additional permissions on top of 00:22:45.710 --> 00:22:45.720 align:start position:0% of 00:22:45.720 --> 00:22:48.350 align:start position:0% of them<00:22:46.720> all<00:22:46.919> right<00:22:47.120> so<00:22:47.679> there's<00:22:47.880> four<00:22:48.120> people 00:22:48.350 --> 00:22:48.360 align:start position:0% them all right so there's four people 00:22:48.360 --> 00:22:50.390 align:start position:0% them all right so there's four people who<00:22:48.480> voted<00:22:48.880> this<00:22:49.279> well<00:22:49.559> that<00:22:49.679> was<00:22:49.840> depressing 00:22:50.390 --> 00:22:50.400 align:start position:0% who voted this well that was depressing 00:22:50.400 --> 00:22:53.390 align:start position:0% who voted this well that was depressing what<00:22:50.480> to<00:22:50.640> do<00:22:51.600> uh<00:22:51.799> what<00:22:51.960> to<00:22:52.120> do<00:22:52.480> not<00:22:52.720> panic<00:22:53.200> so 00:22:53.390 --> 00:22:53.400 align:start position:0% what to do uh what to do not panic so 00:22:53.400 --> 00:22:54.830 align:start position:0% what to do uh what to do not panic so that's<00:22:53.559> the<00:22:53.720> most<00:22:53.919> important<00:22:54.400> part<00:22:54.640> keep 00:22:54.830 --> 00:22:54.840 align:start position:0% that's the most important part keep 00:22:54.840 --> 00:22:56.950 align:start position:0% that's the most important part keep using<00:22:55.159> Pas<00:22:55.480> key<00:22:55.840> just<00:22:56.039> think<00:22:56.320> about<00:22:56.559> using 00:22:56.950 --> 00:22:56.960 align:start position:0% using Pas key just think about using 00:22:56.960 --> 00:23:00.669 align:start position:0% using Pas key just think about using them<00:22:57.520> well<00:22:57.799> using<00:22:58.120> them<00:22:58.559> is<00:22:58.720> knowing<00:22:59.120> this<00:22:59.679> and 00:23:00.669 --> 00:23:00.679 align:start position:0% them well using them is knowing this and 00:23:00.679 --> 00:23:02.590 align:start position:0% them well using them is knowing this and use<00:23:01.039> them<00:23:01.279> knowing<00:23:01.679> that<00:23:01.880> they<00:23:01.960> are<00:23:02.200> pretty 00:23:02.590 --> 00:23:02.600 align:start position:0% use them knowing that they are pretty 00:23:02.600 --> 00:23:04.870 align:start position:0% use them knowing that they are pretty easy<00:23:02.840> to<00:23:03.080> extract<00:23:03.600> by<00:23:03.760> mware<00:23:04.440> if<00:23:04.600> they<00:23:04.720> are 00:23:04.870 --> 00:23:04.880 align:start position:0% easy to extract by mware if they are 00:23:04.880 --> 00:23:07.070 align:start position:0% easy to extract by mware if they are synchronized<00:23:05.640> so<00:23:06.039> just<00:23:06.320> yeah<00:23:06.600> it's<00:23:06.760> not<00:23:06.960> the 00:23:07.070 --> 00:23:07.080 align:start position:0% synchronized so just yeah it's not the 00:23:07.080 --> 00:23:09.870 align:start position:0% synchronized so just yeah it's not the end<00:23:07.279> of<00:23:07.440> the<00:23:07.559> world<00:23:08.400> we<00:23:08.600> just<00:23:08.760> have<00:23:08.919> to<00:23:09.039> be<00:23:09.159> more 00:23:09.870 --> 00:23:09.880 align:start position:0% end of the world we just have to be more 00:23:09.880 --> 00:23:11.909 align:start position:0% end of the world we just have to be more careful<00:23:10.880> all<00:23:11.000> right<00:23:11.320> the<00:23:11.480> next<00:23:11.640> one<00:23:11.760> is 00:23:11.909 --> 00:23:11.919 align:start position:0% careful all right the next one is 00:23:11.919 --> 00:23:13.870 align:start position:0% careful all right the next one is Hardware<00:23:12.240> UB<00:23:12.600> Keys<00:23:13.000> would<00:23:13.159> be<00:23:13.440> relatively 00:23:13.870 --> 00:23:13.880 align:start position:0% Hardware UB Keys would be relatively 00:23:13.880 --> 00:23:15.789 align:start position:0% Hardware UB Keys would be relatively secure<00:23:14.400> yeah<00:23:14.520> they<00:23:14.600> are<00:23:14.760> absolutely<00:23:15.279> secure 00:23:15.789 --> 00:23:15.799 align:start position:0% secure yeah they are absolutely secure 00:23:15.799 --> 00:23:18.230 align:start position:0% secure yeah they are absolutely secure but<00:23:16.120> using<00:23:16.919> uh<00:23:17.039> using<00:23:17.360> your<00:23:17.559> smartphone<00:23:18.080> to 00:23:18.230 --> 00:23:18.240 align:start position:0% but using uh using your smartphone to 00:23:18.240 --> 00:23:20.590 align:start position:0% but using uh using your smartphone to store<00:23:18.720> a<00:23:18.919> key<00:23:19.240> that<00:23:19.400> will<00:23:19.559> not<00:23:19.760> be<00:23:19.919> syn<00:23:20.480> that 00:23:20.590 --> 00:23:20.600 align:start position:0% store a key that will not be syn that 00:23:20.600 --> 00:23:22.990 align:start position:0% store a key that will not be syn that will<00:23:20.840> not<00:23:21.000> be<00:23:21.159> thinkable<00:23:21.799> is<00:23:22.039> also<00:23:22.720> very 00:23:22.990 --> 00:23:23.000 align:start position:0% will not be thinkable is also very 00:23:23.000 --> 00:23:25.549 align:start position:0% will not be thinkable is also very secure<00:23:23.960> but<00:23:24.200> then<00:23:24.440> you<00:23:24.559> can't<00:23:24.760> back<00:23:24.960> up<00:23:25.159> it<00:23:25.360> so 00:23:25.549 --> 00:23:25.559 align:start position:0% secure but then you can't back up it so 00:23:25.559 --> 00:23:26.830 align:start position:0% secure but then you can't back up it so it's<00:23:25.720> always<00:23:25.960> a 00:23:26.830 --> 00:23:26.840 align:start position:0% it's always a 00:23:26.840 --> 00:23:29.750 align:start position:0% it's always a choice<00:23:27.840> all<00:23:28.039> right<00:23:28.600> and<00:23:28.880> next<00:23:29.200> question<00:23:29.520> is 00:23:29.750 --> 00:23:29.760 align:start position:0% choice all right and next question is 00:23:29.760 --> 00:23:31.990 align:start position:0% choice all right and next question is what<00:23:29.880> are<00:23:30.039> your<00:23:30.600> what<00:23:30.720> are<00:23:31.080> options<00:23:31.440> for<00:23:31.720> non-s 00:23:31.990 --> 00:23:32.000 align:start position:0% what are your what are options for non-s 00:23:32.000 --> 00:23:34.590 align:start position:0% what are your what are options for non-s syncable<00:23:32.480> Pass<00:23:32.799> Key<00:23:33.440> exactly<00:23:33.880> the<00:23:34.000> same<00:23:34.440> you 00:23:34.590 --> 00:23:34.600 align:start position:0% syncable Pass Key exactly the same you 00:23:34.600 --> 00:23:36.310 align:start position:0% syncable Pass Key exactly the same you have<00:23:34.760> to<00:23:34.960> pass<00:23:35.240> it<00:23:35.480> as<00:23:35.919> being 00:23:36.310 --> 00:23:36.320 align:start position:0% have to pass it as being 00:23:36.320 --> 00:23:38.350 align:start position:0% have to pass it as being non-discoverable<00:23:37.320> when<00:23:37.440> you<00:23:37.559> create<00:23:37.840> the<00:23:38.039> key 00:23:38.350 --> 00:23:38.360 align:start position:0% non-discoverable when you create the key 00:23:38.360 --> 00:23:39.990 align:start position:0% non-discoverable when you create the key but<00:23:38.480> you<00:23:38.600> can<00:23:38.760> use<00:23:39.000> the<00:23:39.200> smartphone<00:23:39.720> and<00:23:39.840> in 00:23:39.990 --> 00:23:40.000 align:start position:0% but you can use the smartphone and in 00:23:40.000 --> 00:23:42.950 align:start position:0% but you can use the smartphone and in that<00:23:40.240> case<00:23:40.880> uh<00:23:41.039> you<00:23:41.200> are<00:23:41.640> on<00:23:41.840> an<00:23:42.200> old<00:23:42.520> style<00:23:42.880> I 00:23:42.950 --> 00:23:42.960 align:start position:0% that case uh you are on an old style I 00:23:42.960 --> 00:23:44.950 align:start position:0% that case uh you are on an old style I would<00:23:43.159> say<00:23:43.600> phyto 00:23:44.950 --> 00:23:44.960 align:start position:0% would say phyto 00:23:44.960 --> 00:23:49.190 align:start position:0% would say phyto credential<00:23:45.960> all<00:23:46.240> right<00:23:46.919> and<00:23:47.159> let<00:23:47.279> me<00:23:47.480> just 00:23:49.190 --> 00:23:49.200 align:start position:0% credential all right and let me just 00:23:49.200 --> 00:23:52.990 align:start position:0% credential all right and let me just check<00:23:50.200> okay<00:23:50.480> so<00:23:51.039> next<00:23:51.880> top<00:23:52.159> voed<00:23:52.600> question<00:23:52.840> is 00:23:52.990 --> 00:23:53.000 align:start position:0% check okay so next top voed question is 00:23:53.000 --> 00:23:55.110 align:start position:0% check okay so next top voed question is do<00:23:53.080> you<00:23:53.200> think<00:23:53.360> pass<00:23:53.600> keys<00:23:53.799> are<00:23:54.000> easy<00:23:54.320> enough 00:23:55.110 --> 00:23:55.120 align:start position:0% do you think pass keys are easy enough 00:23:55.120 --> 00:23:57.390 align:start position:0% do you think pass keys are easy enough oh<00:23:55.240> it<00:23:55.320> keeps<00:23:55.559> moving<00:23:56.440> do<00:23:56.520> you<00:23:56.679> think<00:23:57.080> pass 00:23:57.390 --> 00:23:57.400 align:start position:0% oh it keeps moving do you think pass 00:23:57.400 --> 00:23:59.149 align:start position:0% oh it keeps moving do you think pass keys<00:23:57.640> are<00:23:57.799> easy<00:23:58.039> enough<00:23:58.200> to<00:23:58.440> to<00:23:58.559> use<00:23:58.960> for 00:23:59.149 --> 00:23:59.159 align:start position:0% keys are easy enough to to use for 00:23:59.159 --> 00:24:00.590 align:start position:0% keys are easy enough to to use for normal 00:24:00.590 --> 00:24:00.600 align:start position:0% normal 00:24:00.600 --> 00:24:03.269 align:start position:0% normal users<00:24:01.600> even<00:24:01.880> as<00:24:02.039> an<00:24:02.200> advanced<00:24:02.600> user<00:24:02.880> I<00:24:03.000> have 00:24:03.269 --> 00:24:03.279 align:start position:0% users even as an advanced user I have 00:24:03.279 --> 00:24:05.350 align:start position:0% users even as an advanced user I have sometimes<00:24:03.559> lost<00:24:04.039> access<00:24:04.279> to<00:24:04.440> pass<00:24:04.760> key<00:24:05.200> and 00:24:05.350 --> 00:24:05.360 align:start position:0% sometimes lost access to pass key and 00:24:05.360 --> 00:24:06.830 align:start position:0% sometimes lost access to pass key and had<00:24:05.480> to<00:24:05.559> jump<00:24:05.799> through<00:24:05.960> hoops<00:24:06.240> to<00:24:06.440> recover 00:24:06.830 --> 00:24:06.840 align:start position:0% had to jump through hoops to recover 00:24:06.840 --> 00:24:08.710 align:start position:0% had to jump through hoops to recover account<00:24:07.159> yes<00:24:07.400> I<00:24:07.520> think<00:24:07.720> I<00:24:07.799> think<00:24:08.000> they<00:24:08.159> will<00:24:08.360> be 00:24:08.710 --> 00:24:08.720 align:start position:0% account yes I think I think they will be 00:24:08.720 --> 00:24:11.630 align:start position:0% account yes I think I think they will be I<00:24:08.840> think<00:24:09.039> they<00:24:09.200> are<00:24:09.520> in<00:24:09.960> in<00:24:10.159> regular<00:24:10.640> cases<00:24:11.480> uh 00:24:11.630 --> 00:24:11.640 align:start position:0% I think they are in in regular cases uh 00:24:11.640 --> 00:24:13.510 align:start position:0% I think they are in in regular cases uh it<00:24:11.760> might<00:24:11.960> be<00:24:12.159> a<00:24:12.320> bit<00:24:12.679> a<00:24:12.760> bit<00:24:13.000> rough<00:24:13.240> on<00:24:13.360> the 00:24:13.510 --> 00:24:13.520 align:start position:0% it might be a bit a bit rough on the 00:24:13.520 --> 00:24:15.390 align:start position:0% it might be a bit a bit rough on the edges<00:24:13.880> at<00:24:14.039> the<00:24:14.159> moment<00:24:14.640> because<00:24:14.840> the<00:24:15.000> protocol 00:24:15.390 --> 00:24:15.400 align:start position:0% edges at the moment because the protocol 00:24:15.400 --> 00:24:16.870 align:start position:0% edges at the moment because the protocol is<00:24:15.520> still<00:24:15.760> very<00:24:15.960> new<00:24:16.279> I<00:24:16.360> mean<00:24:16.520> pasy 00:24:16.870 --> 00:24:16.880 align:start position:0% is still very new I mean pasy 00:24:16.880 --> 00:24:19.669 align:start position:0% is still very new I mean pasy synchronization<00:24:17.520> is<00:24:17.679> only<00:24:18.640> one<00:24:19.000> years<00:24:19.480> one 00:24:19.669 --> 00:24:19.679 align:start position:0% synchronization is only one years one 00:24:19.679 --> 00:24:21.870 align:start position:0% synchronization is only one years one years<00:24:19.919> old<00:24:20.200> one<00:24:20.440> two<00:24:20.679> years<00:24:20.880> old<00:24:21.520> uh<00:24:21.600> so<00:24:21.799> I 00:24:21.870 --> 00:24:21.880 align:start position:0% years old one two years old uh so I 00:24:21.880 --> 00:24:24.190 align:start position:0% years old one two years old uh so I think<00:24:22.000> it<00:24:22.120> will<00:24:22.279> get<00:24:22.520> better<00:24:22.960> and<00:24:23.200> ultimately 00:24:24.190 --> 00:24:24.200 align:start position:0% think it will get better and ultimately 00:24:24.200 --> 00:24:26.549 align:start position:0% think it will get better and ultimately uh<00:24:24.400> all<00:24:24.679> the<00:24:25.039> all<00:24:25.240> the<00:24:25.440> big<00:24:25.679> firms<00:24:26.159> want<00:24:26.360> to 00:24:26.549 --> 00:24:26.559 align:start position:0% uh all the all the big firms want to 00:24:26.559 --> 00:24:29.549 align:start position:0% uh all the all the big firms want to push<00:24:26.799> it<00:24:27.159> so<00:24:27.399> it<00:24:27.520> will<00:24:27.720> definitely<00:24:28.080> get<00:24:28.559> better 00:24:29.549 --> 00:24:29.559 align:start position:0% push it so it will definitely get better 00:24:29.559 --> 00:24:31.029 align:start position:0% push it so it will definitely get better all<00:24:29.679> right<00:24:29.799> we<00:24:29.919> have<00:24:30.039> a<00:24:30.120> few<00:24:30.320> more<00:24:30.520> seconds<00:24:30.799> to 00:24:31.029 --> 00:24:31.039 align:start position:0% all right we have a few more seconds to 00:24:31.039 --> 00:24:33.110 align:start position:0% all right we have a few more seconds to answer<00:24:31.360> this<00:24:31.600> last<00:24:31.880> question<00:24:32.520> if<00:24:32.640> you<00:24:32.760> turn 00:24:33.110 --> 00:24:33.120 align:start position:0% answer this last question if you turn 00:24:33.120 --> 00:24:35.990 align:start position:0% answer this last question if you turn off<00:24:33.880> uh<00:24:33.960> syncing<00:24:34.520> Pas<00:24:34.760> keys<00:24:34.960> on<00:24:35.200> iOS<00:24:35.640> are<00:24:35.840> they 00:24:35.990 --> 00:24:36.000 align:start position:0% off uh syncing Pas keys on iOS are they 00:24:36.000 --> 00:24:38.549 align:start position:0% off uh syncing Pas keys on iOS are they safe<00:24:36.240> again<00:24:36.880> they<00:24:37.039> are<00:24:37.200> still<00:24:37.440> on<00:24:37.600> your<00:24:37.840> device 00:24:38.549 --> 00:24:38.559 align:start position:0% safe again they are still on your device 00:24:38.559 --> 00:24:40.909 align:start position:0% safe again they are still on your device so<00:24:39.159> the<00:24:39.360> problem<00:24:39.799> here<00:24:40.000> is<00:24:40.200> that<00:24:40.440> if<00:24:40.559> you<00:24:40.799> if 00:24:40.909 --> 00:24:40.919 align:start position:0% so the problem here is that if you if 00:24:40.919 --> 00:24:43.630 align:start position:0% so the problem here is that if you if you<00:24:41.200> created<00:24:41.760> the<00:24:41.960> pass<00:24:42.240> key<00:24:42.520> as<00:24:42.720> syn<00:24:42.919> cable 00:24:43.630 --> 00:24:43.640 align:start position:0% you created the pass key as syn cable 00:24:43.640 --> 00:24:45.430 align:start position:0% you created the pass key as syn cable and<00:24:43.799> you<00:24:44.000> turn<00:24:44.279> off<00:24:44.640> synchron<00:24:45.120> Pass<00:24:45.320> Key 00:24:45.430 --> 00:24:45.440 align:start position:0% and you turn off synchron Pass Key 00:24:45.440 --> 00:24:47.510 align:start position:0% and you turn off synchron Pass Key synchronization<00:24:46.320> you<00:24:46.440> get<00:24:46.640> a<00:24:46.840> pass<00:24:47.159> key<00:24:47.399> that 00:24:47.510 --> 00:24:47.520 align:start position:0% synchronization you get a pass key that 00:24:47.520 --> 00:24:49.750 align:start position:0% synchronization you get a pass key that is<00:24:47.640> stored<00:24:48.240> in<00:24:48.440> the<00:24:48.600> application<00:24:49.159> processor 00:24:49.750 --> 00:24:49.760 align:start position:0% is stored in the application processor 00:24:49.760 --> 00:24:51.510 align:start position:0% is stored in the application processor and<00:24:50.000> which<00:24:50.120> is<00:24:50.279> not<00:24:50.480> synchronizable<00:24:51.320> so 00:24:51.510 --> 00:24:51.520 align:start position:0% and which is not synchronizable so 00:24:51.520 --> 00:24:54.269 align:start position:0% and which is not synchronizable so basically<00:24:51.919> you<00:24:52.039> get<00:24:52.240> the<00:24:52.760> worst<00:24:53.000> of<00:24:53.200> both 00:24:54.269 --> 00:24:54.279 align:start position:0% basically you get the worst of both 00:24:54.279 --> 00:24:57.470 align:start position:0% basically you get the worst of both world<00:24:55.720> sorry<00:24:56.720> well<00:24:56.840> actually<00:24:57.039> we<00:24:57.159> have<00:24:57.240> a<00:24:57.320> few 00:24:57.470 --> 00:24:57.480 align:start position:0% world sorry well actually we have a few 00:24:57.480 --> 00:24:58.710 align:start position:0% world sorry well actually we have a few more<00:24:57.679> seconds<00:24:57.960> maybe<00:24:58.120> you<00:24:58.200> want<00:24:58.399> want<00:24:58.520> to 00:24:58.710 --> 00:24:58.720 align:start position:0% more seconds maybe you want want to 00:24:58.720 --> 00:25:01.350 align:start position:0% more seconds maybe you want want to answer<00:24:59.440> also<00:25:00.440> uh<00:25:00.600> what's<00:25:00.799> the<00:25:00.919> future<00:25:01.200> of 00:25:01.350 --> 00:25:01.360 align:start position:0% answer also uh what's the future of 00:25:01.360 --> 00:25:03.669 align:start position:0% answer also uh what's the future of secure<00:25:01.799> chip<00:25:02.120> how<00:25:02.240> do<00:25:02.320> you<00:25:02.440> feel<00:25:03.000> Java<00:25:03.320> card<00:25:03.559> in 00:25:03.669 --> 00:25:03.679 align:start position:0% secure chip how do you feel Java card in 00:25:03.679 --> 00:25:05.269 align:start position:0% secure chip how do you feel Java card in general<00:25:04.039> oh<00:25:04.200> I<00:25:04.320> hope<00:25:04.520> there<00:25:04.679> will<00:25:04.799> be<00:25:04.960> secure 00:25:05.269 --> 00:25:05.279 align:start position:0% general oh I hope there will be secure 00:25:05.279 --> 00:25:07.590 align:start position:0% general oh I hope there will be secure chips<00:25:05.559> that<00:25:05.679> are<00:25:05.799> more<00:25:06.039> secure<00:25:06.840> more<00:25:07.080> sorry 00:25:07.590 --> 00:25:07.600 align:start position:0% chips that are more secure more sorry 00:25:07.600 --> 00:25:09.990 align:start position:0% chips that are more secure more sorry more<00:25:07.880> open<00:25:08.320> in<00:25:08.440> the<00:25:08.640> future<00:25:09.080> and<00:25:09.240> Flash<00:25:09.600> BS<00:25:09.880> is 00:25:09.990 --> 00:25:10.000 align:start position:0% more open in the future and Flash BS is 00:25:10.000 --> 00:25:12.110 align:start position:0% more open in the future and Flash BS is doing<00:25:10.240> a<00:25:10.360> lot<00:25:10.559> of<00:25:10.960> a<00:25:11.039> lot<00:25:11.200> of<00:25:11.320> research<00:25:11.720> in<00:25:11.919> that 00:25:12.110 --> 00:25:12.120 align:start position:0% doing a lot of a lot of research in that 00:25:12.120 --> 00:25:15.230 align:start position:0% doing a lot of a lot of research in that so<00:25:12.320> it's<00:25:12.520> good<00:25:13.240> uh<00:25:13.399> Java<00:25:13.760> card<00:25:14.000> is<00:25:14.200> outdated<00:25:15.120> uh 00:25:15.230 --> 00:25:15.240 align:start position:0% so it's good uh Java card is outdated uh 00:25:15.240 --> 00:25:16.909 align:start position:0% so it's good uh Java card is outdated uh that's<00:25:15.440> one<00:25:15.559> of<00:25:15.679> the<00:25:15.840> reason<00:25:16.240> why<00:25:16.440> I<00:25:16.600> decided 00:25:16.909 --> 00:25:16.919 align:start position:0% that's one of the reason why I decided 00:25:16.919 --> 00:25:19.389 align:start position:0% that's one of the reason why I decided to<00:25:17.080> start<00:25:17.320> Ledger<00:25:17.840> because<00:25:18.080> I<00:25:18.200> wanted<00:25:18.480> to<00:25:18.720> have 00:25:19.389 --> 00:25:19.399 align:start position:0% to start Ledger because I wanted to have 00:25:19.399 --> 00:25:21.630 align:start position:0% to start Ledger because I wanted to have U<00:25:19.559> native<00:25:19.919> code<00:25:20.200> running<00:25:20.440> on<00:25:20.559> a<00:25:20.679> smart<00:25:21.000> card<00:25:21.279> so 00:25:21.630 --> 00:25:21.640 align:start position:0% U native code running on a smart card so 00:25:21.640 --> 00:25:24.389 align:start position:0% U native code running on a smart card so that's<00:25:21.919> my<00:25:22.360> general<00:25:22.760> take<00:25:23.000> so<00:25:23.360> I<00:25:23.840> javac<00:25:24.159> card 00:25:24.389 --> 00:25:24.399 align:start position:0% that's my general take so I javac card 00:25:24.399 --> 00:25:26.870 align:start position:0% that's my general take so I javac card is<00:25:24.600> good<00:25:25.000> as<00:25:25.880> considering<00:25:26.440> that<00:25:26.679> the 00:25:26.870 --> 00:25:26.880 align:start position:0% is good as considering that the 00:25:26.880 --> 00:25:28.310 align:start position:0% is good as considering that the basically<00:25:27.320> the<00:25:27.440> only<00:25:27.720> thing<00:25:28.000> that<00:25:28.080> you<00:25:28.200> can 00:25:28.310 --> 00:25:28.320 align:start position:0% basically the only thing that you can 00:25:28.320 --> 00:25:30.720 align:start position:0% basically the only thing that you can can<00:25:28.559> back