WEBVTT Kind: captions Language: en 00:00:00.050 --> 00:00:03.649 align:start position:0% hi<00:00:01.050> everybody<00:00:01.319> so<00:00:02.220> maybe<00:00:02.730> you<00:00:03.090> are<00:00:03.120> not<00:00:03.419> coming 00:00:03.649 --> 00:00:03.659 align:start position:0% hi everybody so maybe you are not coming 00:00:03.659 --> 00:00:05.269 align:start position:0% hi everybody so maybe you are not coming for<00:00:03.929> this<00:00:04.080> talk<00:00:04.290> so<00:00:04.560> I<00:00:04.589> have<00:00:04.859> an<00:00:04.950> explanation 00:00:05.269 --> 00:00:05.279 align:start position:0% for this talk so I have an explanation 00:00:05.279 --> 00:00:10.879 align:start position:0% for this talk so I have an explanation for<00:00:05.670> that<00:00:07.130> which<00:00:08.130> is<00:00:08.370> right<00:00:08.550> there<00:00:08.960> so<00:00:09.960> where<00:00:10.860> I 00:00:10.879 --> 00:00:10.889 align:start position:0% for that which is right there so where I 00:00:10.889 --> 00:00:12.440 align:start position:0% for that which is right there so where I can<00:00:11.160> try<00:00:11.340> to<00:00:11.400> convince<00:00:11.849> that<00:00:11.940> this<00:00:12.179> is<00:00:12.300> the 00:00:12.440 --> 00:00:12.450 align:start position:0% can try to convince that this is the 00:00:12.450 --> 00:00:14.150 align:start position:0% can try to convince that this is the talk<00:00:12.630> you<00:00:12.750> were<00:00:12.870> coming<00:00:13.139> from<00:00:13.349> you<00:00:13.679> are<00:00:13.889> coming 00:00:14.150 --> 00:00:14.160 align:start position:0% talk you were coming from you are coming 00:00:14.160 --> 00:00:17.480 align:start position:0% talk you were coming from you are coming from<00:00:14.280> but<00:00:14.460> it<00:00:14.610> will<00:00:14.790> probably<00:00:15.089> not<00:00:15.719> work<00:00:16.100> so<00:00:17.100> my 00:00:17.480 --> 00:00:17.490 align:start position:0% from but it will probably not work so my 00:00:17.490 --> 00:00:19.550 align:start position:0% from but it will probably not work so my initial<00:00:17.699> talk<00:00:18.150> was<00:00:18.359> rejected<00:00:19.020> and<00:00:19.230> I<00:00:19.289> got<00:00:19.529> a 00:00:19.550 --> 00:00:19.560 align:start position:0% initial talk was rejected and I got a 00:00:19.560 --> 00:00:22.010 align:start position:0% initial talk was rejected and I got a notification<00:00:20.010> like<00:00:20.730> yesterday<00:00:21.480> at<00:00:21.570> midnight 00:00:22.010 --> 00:00:22.020 align:start position:0% notification like yesterday at midnight 00:00:22.020 --> 00:00:25.130 align:start position:0% notification like yesterday at midnight that<00:00:22.289> in<00:00:22.800> fact<00:00:23.010> it<00:00:23.130> was<00:00:23.369> not<00:00:23.580> rejected<00:00:24.109> so<00:00:25.109> I 00:00:25.130 --> 00:00:25.140 align:start position:0% that in fact it was not rejected so I 00:00:25.140 --> 00:00:27.230 align:start position:0% that in fact it was not rejected so I decided<00:00:25.560> to<00:00:25.650> recycle<00:00:26.220> some<00:00:26.400> slides<00:00:26.730> I<00:00:26.939> had<00:00:27.060> for 00:00:27.230 --> 00:00:27.240 align:start position:0% decided to recycle some slides I had for 00:00:27.240 --> 00:00:27.920 align:start position:0% decided to recycle some slides I had for hgx 00:00:27.920 --> 00:00:27.930 align:start position:0% hgx 00:00:27.930 --> 00:00:30.320 align:start position:0% hgx add<00:00:28.109> a<00:00:28.170> bit<00:00:28.439> more<00:00:28.590> content<00:00:28.980> and<00:00:29.340> that's<00:00:30.000> what 00:00:30.320 --> 00:00:30.330 align:start position:0% add a bit more content and that's what 00:00:30.330 --> 00:00:32.540 align:start position:0% add a bit more content and that's what the<00:00:30.510> talk<00:00:30.660> will<00:00:30.869> be<00:00:30.900> about<00:00:31.199> so<00:00:32.070> if<00:00:32.279> you<00:00:32.399> have<00:00:32.520> a 00:00:32.540 --> 00:00:32.550 align:start position:0% the talk will be about so if you have a 00:00:32.550 --> 00:00:34.760 align:start position:0% the talk will be about so if you have a medical<00:00:32.910> condition<00:00:32.969> and<00:00:33.930> you<00:00:34.260> can't<00:00:34.500> listen 00:00:34.760 --> 00:00:34.770 align:start position:0% medical condition and you can't listen 00:00:34.770 --> 00:00:37.400 align:start position:0% medical condition and you can't listen to<00:00:34.980> a<00:00:35.190> nice<00:00:35.340> Jake's<00:00:35.640> talk<00:00:35.940> you<00:00:36.210> might<00:00:36.510> leave<00:00:37.079> I 00:00:37.400 --> 00:00:37.410 align:start position:0% to a nice Jake's talk you might leave I 00:00:37.410 --> 00:00:40.340 align:start position:0% to a nice Jake's talk you might leave I won't<00:00:37.710> be<00:00:37.890> offended<00:00:38.390> otherwise<00:00:39.390> it<00:00:40.020> should<00:00:40.200> be 00:00:40.340 --> 00:00:40.350 align:start position:0% won't be offended otherwise it should be 00:00:40.350 --> 00:00:44.690 align:start position:0% won't be offended otherwise it should be interesting<00:00:40.829> so<00:00:41.570> with<00:00:42.570> that<00:00:43.280> we<00:00:44.280> are<00:00:44.309> going<00:00:44.579> to 00:00:44.690 --> 00:00:44.700 align:start position:0% interesting so with that we are going to 00:00:44.700 --> 00:00:46.220 align:start position:0% interesting so with that we are going to talk<00:00:44.910> so<00:00:45.090> a<00:00:45.120> little<00:00:45.239> bit<00:00:45.450> more<00:00:45.510> about<00:00:45.899> around 00:00:46.220 --> 00:00:46.230 align:start position:0% talk so a little bit more about around 00:00:46.230 --> 00:00:48.560 align:start position:0% talk so a little bit more about around clave<00:00:46.559> the<00:00:46.800> idea<00:00:47.219> is<00:00:47.280> to<00:00:47.550> keep<00:00:47.820> talking<00:00:48.180> about 00:00:48.560 --> 00:00:48.570 align:start position:0% clave the idea is to keep talking about 00:00:48.570 --> 00:00:50.930 align:start position:0% clave the idea is to keep talking about what<00:00:48.750> we<00:00:49.140> did<00:00:49.320> last<00:00:49.590> year<00:00:49.800> previously<00:00:50.700> which 00:00:50.930 --> 00:00:50.940 align:start position:0% what we did last year previously which 00:00:50.940 --> 00:00:52.729 align:start position:0% what we did last year previously which was<00:00:51.149> not<00:00:51.360> very<00:00:51.570> successful<00:00:52.079> we<00:00:52.260> will<00:00:52.379> discuss 00:00:52.729 --> 00:00:52.739 align:start position:0% was not very successful we will discuss 00:00:52.739 --> 00:00:54.650 align:start position:0% was not very successful we will discuss why<00:00:52.980> and<00:00:53.280> we<00:00:53.399> will<00:00:53.550> discuss<00:00:53.910> how<00:00:54.480> we<00:00:54.539> can 00:00:54.650 --> 00:00:54.660 align:start position:0% why and we will discuss how we can 00:00:54.660 --> 00:00:58.160 align:start position:0% why and we will discuss how we can improve<00:00:55.050> that<00:00:55.289> and<00:00:55.820> well<00:00:56.820> if<00:00:57.120> you<00:00:57.660> want<00:00:57.960> to 00:00:58.160 --> 00:00:58.170 align:start position:0% improve that and well if you want to 00:00:58.170 --> 00:00:59.900 align:start position:0% improve that and well if you want to follow<00:00:58.350> something<00:00:58.949> for<00:00:59.190> example<00:00:59.280> during<00:00:59.789> the 00:00:59.900 --> 00:00:59.910 align:start position:0% follow something for example during the 00:00:59.910 --> 00:01:01.729 align:start position:0% follow something for example during the talk<00:01:00.239> and<00:01:00.480> read<00:01:00.780> something<00:01:00.989> during<00:01:01.350> the<00:01:01.469> talks 00:01:01.729 --> 00:01:01.739 align:start position:0% talk and read something during the talks 00:01:01.739 --> 00:01:03.590 align:start position:0% talk and read something during the talks a<00:01:01.949> thread<00:01:02.250> model<00:01:02.609> we<00:01:02.789> have<00:01:02.940> in<00:01:03.059> the<00:01:03.180> readme<00:01:03.390> is 00:01:03.590 --> 00:01:03.600 align:start position:0% a thread model we have in the readme is 00:01:03.600 --> 00:01:05.810 align:start position:0% a thread model we have in the readme is interesting<00:01:04.229> to<00:01:04.350> read<00:01:04.530> and<00:01:04.860> it's<00:01:05.339> still<00:01:05.580> up<00:01:05.700> to 00:01:05.810 --> 00:01:05.820 align:start position:0% interesting to read and it's still up to 00:01:05.820 --> 00:01:10.100 align:start position:0% interesting to read and it's still up to date<00:01:05.970> even<00:01:06.240> if<00:01:06.450> the<00:01:06.600> code<00:01:06.840> is<00:01:07.049> not<00:01:08.689> so<00:01:09.689> first 00:01:10.100 --> 00:01:10.110 align:start position:0% date even if the code is not so first 00:01:10.110 --> 00:01:12.710 align:start position:0% date even if the code is not so first question<00:01:10.229> you<00:01:10.619> can<00:01:10.830> ask<00:01:10.979> why<00:01:11.729> are<00:01:12.030> we<00:01:12.240> making<00:01:12.450> a 00:01:12.710 --> 00:01:12.720 align:start position:0% question you can ask why are we making a 00:01:12.720 --> 00:01:14.539 align:start position:0% question you can ask why are we making a month<00:01:12.900> wave<00:01:13.170> as<00:01:13.350> a<00:01:13.409> hardware<00:01:14.189> wallet 00:01:14.539 --> 00:01:14.549 align:start position:0% month wave as a hardware wallet 00:01:14.549 --> 00:01:16.820 align:start position:0% month wave as a hardware wallet manufacturer<00:01:15.150> so<00:01:15.990> the<00:01:16.110> first<00:01:16.350> thing<00:01:16.530> is<00:01:16.680> that 00:01:16.820 --> 00:01:16.830 align:start position:0% manufacturer so the first thing is that 00:01:16.830 --> 00:01:19.100 align:start position:0% manufacturer so the first thing is that we<00:01:17.100> are<00:01:17.130> lecture<00:01:18.030> has<00:01:18.180> been<00:01:18.330> developing<00:01:18.810> into 00:01:19.100 --> 00:01:19.110 align:start position:0% we are lecture has been developing into 00:01:19.110 --> 00:01:20.990 align:start position:0% we are lecture has been developing into civil<00:01:19.470> industries<00:01:20.130> and<00:01:20.369> created<00:01:20.790> several 00:01:20.990 --> 00:01:21.000 align:start position:0% civil industries and created several 00:01:21.000 --> 00:01:23.120 align:start position:0% civil industries and created several business<00:01:21.630> units<00:01:21.930> today<00:01:22.140> so<00:01:22.619> we<00:01:22.830> are<00:01:22.920> not<00:01:23.070> only 00:01:23.120 --> 00:01:23.130 align:start position:0% business units today so we are not only 00:01:23.130 --> 00:01:25.969 align:start position:0% business units today so we are not only making<00:01:23.490> our<00:01:23.880> wallets<00:01:24.360> with<00:01:24.600> the<00:01:24.780> SE<00:01:25.590> on<00:01:25.799> which 00:01:25.969 --> 00:01:25.979 align:start position:0% making our wallets with the SE on which 00:01:25.979 --> 00:01:28.819 align:start position:0% making our wallets with the SE on which we<00:01:26.130> can<00:01:26.310> call<00:01:26.520> our<00:01:26.670> own<00:01:26.790> OS<00:01:27.290> we<00:01:28.290> are<00:01:28.409> exploring 00:01:28.819 --> 00:01:28.829 align:start position:0% we can call our own OS we are exploring 00:01:28.829 --> 00:01:31.039 align:start position:0% we can call our own OS we are exploring the<00:01:29.009> custodian<00:01:29.460> model<00:01:29.790> where<00:01:30.030> we<00:01:30.270> work<00:01:30.450> on<00:01:30.600> HSN 00:01:31.039 --> 00:01:31.049 align:start position:0% the custodian model where we work on HSN 00:01:31.049 --> 00:01:33.800 align:start position:0% the custodian model where we work on HSN that<00:01:31.259> are<00:01:31.409> not<00:01:31.590> built<00:01:32.400> by<00:01:32.640> us<00:01:32.850> so<00:01:33.240> in<00:01:33.360> that<00:01:33.509> case 00:01:33.800 --> 00:01:33.810 align:start position:0% that are not built by us so in that case 00:01:33.810 --> 00:01:35.210 align:start position:0% that are not built by us so in that case we<00:01:34.049> need<00:01:34.079> to<00:01:34.229> work<00:01:34.530> into<00:01:34.799> something<00:01:35.009> that 00:01:35.210 --> 00:01:35.220 align:start position:0% we need to work into something that 00:01:35.220 --> 00:01:37.160 align:start position:0% we need to work into something that looks<00:01:35.640> a<00:01:35.820> little<00:01:35.909> bit<00:01:36.210> like<00:01:36.450> an<00:01:36.600> enclave<00:01:36.750> and 00:01:37.160 --> 00:01:37.170 align:start position:0% looks a little bit like an enclave and 00:01:37.170 --> 00:01:39.679 align:start position:0% looks a little bit like an enclave and we<00:01:38.040> want<00:01:38.250> to<00:01:38.340> transition<00:01:38.640> from<00:01:38.880> a<00:01:39.240> company 00:01:39.679 --> 00:01:39.689 align:start position:0% we want to transition from a company 00:01:39.689 --> 00:01:41.510 align:start position:0% we want to transition from a company manufacturing<00:01:40.020> hardware<00:01:40.829> devices<00:01:41.130> to<00:01:41.430> a 00:01:41.510 --> 00:01:41.520 align:start position:0% manufacturing hardware devices to a 00:01:41.520 --> 00:01:43.940 align:start position:0% manufacturing hardware devices to a company<00:01:41.909> selling<00:01:42.899> operating<00:01:43.619> system 00:01:43.940 --> 00:01:43.950 align:start position:0% company selling operating system 00:01:43.950 --> 00:01:46.700 align:start position:0% company selling operating system licenses<00:01:44.460> and<00:01:44.670> for<00:01:45.540> that<00:01:45.689> enclaves<00:01:46.290> are<00:01:46.500> very 00:01:46.700 --> 00:01:46.710 align:start position:0% licenses and for that enclaves are very 00:01:46.710 --> 00:01:48.499 align:start position:0% licenses and for that enclaves are very good<00:01:46.860> target<00:01:47.250> because<00:01:47.610> he<00:01:47.729> already<00:01:47.850> exists 00:01:48.499 --> 00:01:48.509 align:start position:0% good target because he already exists 00:01:48.509 --> 00:01:50.690 align:start position:0% good target because he already exists there<00:01:48.689> already<00:01:48.930> in<00:01:49.110> the<00:01:49.229> market<00:01:49.590> and<00:01:49.799> the<00:01:50.490> main 00:01:50.690 --> 00:01:50.700 align:start position:0% there already in the market and the main 00:01:50.700 --> 00:01:52.670 align:start position:0% there already in the market and the main obstacle<00:01:51.270> today<00:01:51.570> for<00:01:51.810> people<00:01:51.960> to<00:01:52.470> use<00:01:52.649> a 00:01:52.670 --> 00:01:52.680 align:start position:0% obstacle today for people to use a 00:01:52.680 --> 00:01:54.649 align:start position:0% obstacle today for people to use a ledger<00:01:53.100> is<00:01:53.220> actually<00:01:53.549> to<00:01:53.670> buy<00:01:53.820> a<00:01:53.850> ledger<00:01:54.119> so<00:01:54.479> if 00:01:54.649 --> 00:01:54.659 align:start position:0% ledger is actually to buy a ledger so if 00:01:54.659 --> 00:01:57.289 align:start position:0% ledger is actually to buy a ledger so if we<00:01:54.840> could<00:01:55.049> find<00:01:55.380> a<00:01:55.530> way<00:01:55.560> to<00:01:55.770> download<00:01:56.100> a<00:01:56.610> ledger 00:01:57.289 --> 00:01:57.299 align:start position:0% we could find a way to download a ledger 00:01:57.299 --> 00:02:00.139 align:start position:0% we could find a way to download a ledger and<00:01:57.750> have<00:01:58.110> an<00:01:58.590> interesting<00:01:59.219> security<00:01:59.399> on<00:02:00.030> an 00:02:00.139 --> 00:02:00.149 align:start position:0% and have an interesting security on an 00:02:00.149 --> 00:02:02.179 align:start position:0% and have an interesting security on an existing<00:02:00.420> computer<00:02:01.049> it<00:02:01.680> would<00:02:01.829> be<00:02:01.979> quite 00:02:02.179 --> 00:02:02.189 align:start position:0% existing computer it would be quite 00:02:02.189 --> 00:02:03.950 align:start position:0% existing computer it would be quite interesting<00:02:02.640> for<00:02:02.820> us<00:02:02.969> and<00:02:03.180> so<00:02:03.329> that's<00:02:03.540> why<00:02:03.719> we 00:02:03.950 --> 00:02:03.960 align:start position:0% interesting for us and so that's why we 00:02:03.960 --> 00:02:06.050 align:start position:0% interesting for us and so that's why we are<00:02:03.990> digging<00:02:04.290> into<00:02:04.560> those<00:02:04.799> models<00:02:05.009> and<00:02:05.430> we<00:02:05.909> are 00:02:06.050 --> 00:02:06.060 align:start position:0% are digging into those models and we are 00:02:06.060 --> 00:02:08.540 align:start position:0% are digging into those models and we are rating<00:02:06.479> the<00:02:06.600> security<00:02:07.170> very<00:02:07.550> thoughtfully 00:02:08.540 --> 00:02:08.550 align:start position:0% rating the security very thoughtfully 00:02:08.550 --> 00:02:11.990 align:start position:0% rating the security very thoughtfully for<00:02:08.759> that<00:02:08.910> so<00:02:09.810> we<00:02:10.200> have<00:02:10.319> a<00:02:10.349> reusable<00:02:11.310> operating 00:02:11.990 --> 00:02:12.000 align:start position:0% for that so we have a reusable operating 00:02:12.000 --> 00:02:13.700 align:start position:0% for that so we have a reusable operating system<00:02:12.300> code<00:02:12.480> base<00:02:12.720> working<00:02:13.230> on 00:02:13.700 --> 00:02:13.710 align:start position:0% system code base working on 00:02:13.710 --> 00:02:16.310 align:start position:0% system code base working on Clavin<00:02:14.150> changing<00:02:15.150> from<00:02:15.480> a<00:02:15.510> secure<00:02:15.960> element<00:02:16.020> to 00:02:16.310 --> 00:02:16.320 align:start position:0% Clavin changing from a secure element to 00:02:16.320 --> 00:02:18.950 align:start position:0% Clavin changing from a secure element to an<00:02:16.410> enclave<00:02:16.740> first<00:02:17.070> is<00:02:17.370> quite<00:02:17.730> easy<00:02:18.030> so<00:02:18.360> using 00:02:18.950 --> 00:02:18.960 align:start position:0% an enclave first is quite easy so using 00:02:18.960 --> 00:02:23.240 align:start position:0% an enclave first is quite easy so using this<00:02:19.200> way<00:02:19.740> using<00:02:19.950> expenses<00:02:20.640> and<00:02:22.250> another 00:02:23.240 --> 00:02:23.250 align:start position:0% this way using expenses and another 00:02:23.250 --> 00:02:25.610 align:start position:0% this way using expenses and another important<00:02:23.730> thing<00:02:23.940> is<00:02:24.210> that<00:02:24.330> well<00:02:25.080> we<00:02:25.470> have<00:02:25.500> a 00:02:25.610 --> 00:02:25.620 align:start position:0% important thing is that well we have a 00:02:25.620 --> 00:02:28.640 align:start position:0% important thing is that well we have a strong<00:02:26.360> expertise<00:02:27.360> in<00:02:27.750> hardening 00:02:28.640 --> 00:02:28.650 align:start position:0% strong expertise in hardening 00:02:28.650 --> 00:02:30.620 align:start position:0% strong expertise in hardening cryptographic<00:02:28.980> code<00:02:29.460> and<00:02:29.820> this<00:02:30.330> is<00:02:30.450> some 00:02:30.620 --> 00:02:30.630 align:start position:0% cryptographic code and this is some 00:02:30.630 --> 00:02:32.510 align:start position:0% cryptographic code and this is some things<00:02:30.870> that's<00:02:31.140> difficult<00:02:31.680> to<00:02:32.010> do<00:02:32.190> I<00:02:32.220> mean 00:02:32.510 --> 00:02:32.520 align:start position:0% things that's difficult to do I mean 00:02:32.520 --> 00:02:33.920 align:start position:0% things that's difficult to do I mean that<00:02:32.550> some<00:02:32.850> things<00:02:33.090> that<00:02:33.270> you<00:02:33.390> don't<00:02:33.600> usually 00:02:33.920 --> 00:02:33.930 align:start position:0% that some things that you don't usually 00:02:33.930 --> 00:02:36.110 align:start position:0% that some things that you don't usually do<00:02:34.320> because<00:02:34.710> a<00:02:34.740> lot<00:02:34.950> of<00:02:34.980> people<00:02:35.310> using<00:02:35.700> secure 00:02:36.110 --> 00:02:36.120 align:start position:0% do because a lot of people using secure 00:02:36.120 --> 00:02:38.480 align:start position:0% do because a lot of people using secure elements<00:02:36.540> will<00:02:37.410> just<00:02:37.680> reuse<00:02:38.010> a<00:02:38.040> vendor 00:02:38.480 --> 00:02:38.490 align:start position:0% elements will just reuse a vendor 00:02:38.490 --> 00:02:40.550 align:start position:0% elements will just reuse a vendor cryptographic<00:02:38.820> library<00:02:39.420> we<00:02:40.020> build<00:02:40.230> them<00:02:40.350> from 00:02:40.550 --> 00:02:40.560 align:start position:0% cryptographic library we build them from 00:02:40.560 --> 00:02:43.400 align:start position:0% cryptographic library we build them from scratch<00:02:40.650> and<00:02:41.280> we<00:02:41.460> use<00:02:41.880> everything<00:02:42.840> that<00:02:43.080> we 00:02:43.400 --> 00:02:43.410 align:start position:0% scratch and we use everything that we 00:02:43.410 --> 00:02:46.100 align:start position:0% scratch and we use everything that we have<00:02:43.560> on<00:02:43.680> the<00:02:43.800> chip<00:02:44.040> to<00:02:44.220> make<00:02:44.250> them<00:02:44.850> harder<00:02:45.330> so 00:02:46.100 --> 00:02:46.110 align:start position:0% have on the chip to make them harder so 00:02:46.110 --> 00:02:48.530 align:start position:0% have on the chip to make them harder so we<00:02:46.140> did<00:02:46.530> a<00:02:46.560> popular<00:02:47.010> CTF<00:02:47.550> this<00:02:48.300> year 00:02:48.530 --> 00:02:48.540 align:start position:0% we did a popular CTF this year 00:02:48.540 --> 00:02:50.840 align:start position:0% we did a popular CTF this year honourable<00:02:49.530> device<00:02:49.830> that<00:02:50.100> was<00:02:50.250> worn<00:02:50.550> by<00:02:50.640> a 00:02:50.840 --> 00:02:50.850 align:start position:0% honourable device that was worn by a 00:02:50.850 --> 00:02:54.350 align:start position:0% honourable device that was worn by a company<00:02:51.300> called<00:02:51.420> ninja<00:02:51.780> labs<00:02:52.310> they<00:02:53.310> like<00:02:53.490> CTF 00:02:54.350 --> 00:02:54.360 align:start position:0% company called ninja labs they like CTF 00:02:54.360 --> 00:02:56.330 align:start position:0% company called ninja labs they like CTF didn't<00:02:54.840> describe<00:02:55.140> everything<00:02:55.440> yet<00:02:55.770> but<00:02:55.980> it<00:02:56.310> is 00:02:56.330 --> 00:02:56.340 align:start position:0% didn't describe everything yet but it is 00:02:56.340 --> 00:02:59.750 align:start position:0% didn't describe everything yet but it is related<00:02:57.270> to<00:02:57.410> side<00:02:58.410> channels<00:02:58.830> and<00:02:59.040> to<00:02:59.250> template 00:02:59.750 --> 00:02:59.760 align:start position:0% related to side channels and to template 00:02:59.760 --> 00:03:02.390 align:start position:0% related to side channels and to template profiling<00:03:00.300> on<00:03:00.450> side<00:03:00.630> channels<00:03:00.990> so<00:03:01.200> that's<00:03:01.410> the 00:03:02.390 --> 00:03:02.400 align:start position:0% profiling on side channels so that's the 00:03:02.400 --> 00:03:03.800 align:start position:0% profiling on side channels so that's the kind<00:03:02.610> of<00:03:02.700> things<00:03:02.970> we<00:03:03.150> want<00:03:03.330> to<00:03:03.390> do<00:03:03.540> an<00:03:03.660> edge 00:03:03.800 --> 00:03:03.810 align:start position:0% kind of things we want to do an edge 00:03:03.810 --> 00:03:06.770 align:start position:0% kind of things we want to do an edge takes<00:03:04.050> as<00:03:04.260> well<00:03:04.500> improve<00:03:05.310> it<00:03:05.460> and<00:03:05.670> provide<00:03:06.630> the 00:03:06.770 --> 00:03:06.780 align:start position:0% takes as well improve it and provide the 00:03:06.780 --> 00:03:10.550 align:start position:0% takes as well improve it and provide the result<00:03:07.110> you<00:03:07.230> everybody<00:03:07.590> so<00:03:08.750> if<00:03:09.750> you<00:03:10.110> want<00:03:10.320> to 00:03:10.550 --> 00:03:10.560 align:start position:0% result you everybody so if you want to 00:03:10.560 --> 00:03:14.600 align:start position:0% result you everybody so if you want to transition<00:03:10.950> from<00:03:11.250> a<00:03:12.000> hardware<00:03:12.450> wallet<00:03:12.780> to<00:03:13.610> via 00:03:14.600 --> 00:03:14.610 align:start position:0% transition from a hardware wallet to via 00:03:14.610 --> 00:03:17.090 align:start position:0% transition from a hardware wallet to via to<00:03:14.760> a<00:03:14.790> secure<00:03:15.270> device<00:03:15.570> so<00:03:15.810> 12<00:03:16.080> Enclave<00:03:16.440> you 00:03:17.090 --> 00:03:17.100 align:start position:0% to a secure device so 12 Enclave you 00:03:17.100 --> 00:03:19.490 align:start position:0% to a secure device so 12 Enclave you have<00:03:17.220> to<00:03:17.340> consider<00:03:17.580> a<00:03:17.730> few<00:03:17.910> things<00:03:18.260> first<00:03:19.260> you 00:03:19.490 --> 00:03:19.500 align:start position:0% have to consider a few things first you 00:03:19.500 --> 00:03:21.290 align:start position:0% have to consider a few things first you want<00:03:19.710> to<00:03:19.800> focus<00:03:20.190> on<00:03:20.340> the<00:03:20.460> key<00:03:20.610> protection<00:03:21.120> so 00:03:21.290 --> 00:03:21.300 align:start position:0% want to focus on the key protection so 00:03:21.300 --> 00:03:22.880 align:start position:0% want to focus on the key protection so keyboard<00:03:21.750> action<00:03:21.990> is<00:03:22.110> the<00:03:22.200> most<00:03:22.410> important 00:03:22.880 --> 00:03:22.890 align:start position:0% keyboard action is the most important 00:03:22.890 --> 00:03:24.530 align:start position:0% keyboard action is the most important part<00:03:23.100> of<00:03:23.220> a<00:03:23.340> hardware<00:03:23.610> wallet<00:03:23.940> it's<00:03:24.180> going<00:03:24.420> to 00:03:24.530 --> 00:03:24.540 align:start position:0% part of a hardware wallet it's going to 00:03:24.540 --> 00:03:26.270 align:start position:0% part of a hardware wallet it's going to be<00:03:24.660> very<00:03:24.870> important<00:03:25.320> for<00:03:25.470> an<00:03:25.560> enclave<00:03:25.890> as<00:03:26.070> well 00:03:26.270 --> 00:03:26.280 align:start position:0% be very important for an enclave as well 00:03:26.280 --> 00:03:28.700 align:start position:0% be very important for an enclave as well you<00:03:27.090> don't<00:03:27.270> want<00:03:27.540> an<00:03:27.690> attacker<00:03:27.960> to<00:03:28.230> be<00:03:28.380> able<00:03:28.470> to 00:03:28.700 --> 00:03:28.710 align:start position:0% you don't want an attacker to be able to 00:03:28.710 --> 00:03:31.310 align:start position:0% you don't want an attacker to be able to extract<00:03:29.040> keys<00:03:29.280> so<00:03:30.120> here<00:03:30.480> for<00:03:30.690> an<00:03:30.780> entree<00:03:31.110> we 00:03:31.310 --> 00:03:31.320 align:start position:0% extract keys so here for an entree we 00:03:31.320 --> 00:03:33.350 align:start position:0% extract keys so here for an entree we will<00:03:31.470> focus<00:03:31.650> on<00:03:32.010> software<00:03:32.220> threat<00:03:32.640> models<00:03:33.030> so 00:03:33.350 --> 00:03:33.360 align:start position:0% will focus on software threat models so 00:03:33.360 --> 00:03:35.210 align:start position:0% will focus on software threat models so we<00:03:33.570> will<00:03:33.780> not<00:03:34.050> consider<00:03:34.290> hardware<00:03:34.950> threat 00:03:35.210 --> 00:03:35.220 align:start position:0% we will not consider hardware threat 00:03:35.220 --> 00:03:37.310 align:start position:0% we will not consider hardware threat models<00:03:35.580> where<00:03:35.880> an<00:03:36.090> attacker<00:03:36.690> has<00:03:36.960> access<00:03:36.990> to 00:03:37.310 --> 00:03:37.320 align:start position:0% models where an attacker has access to 00:03:37.320 --> 00:03:39.020 align:start position:0% models where an attacker has access to the<00:03:37.560> Enclave<00:03:37.920> because<00:03:38.340> that's<00:03:38.550> pretty<00:03:38.850> much 00:03:39.020 --> 00:03:39.030 align:start position:0% the Enclave because that's pretty much 00:03:39.030 --> 00:03:41.090 align:start position:0% the Enclave because that's pretty much out<00:03:39.360> of<00:03:39.510> scope<00:03:39.780> I<00:03:39.960> mean<00:03:40.200> waves<00:03:40.680> are<00:03:40.860> quite 00:03:41.090 --> 00:03:41.100 align:start position:0% out of scope I mean waves are quite 00:03:41.100 --> 00:03:44.030 align:start position:0% out of scope I mean waves are quite complex<00:03:41.580> and<00:03:41.880> it's<00:03:42.150> difficult<00:03:42.570> to<00:03:43.230> focus<00:03:43.650> on 00:03:44.030 --> 00:03:44.040 align:start position:0% complex and it's difficult to focus on 00:03:44.040 --> 00:03:46.130 align:start position:0% complex and it's difficult to focus on securing<00:03:44.520> as<00:03:44.700> a<00:03:44.760> whole<00:03:45.330> thing<00:03:45.600> against<00:03:46.080> a 00:03:46.130 --> 00:03:46.140 align:start position:0% securing as a whole thing against a 00:03:46.140 --> 00:03:50.690 align:start position:0% securing as a whole thing against a physical<00:03:46.530> attacker<00:03:47.360> then<00:03:48.920> user<00:03:49.920> confirmation 00:03:50.690 --> 00:03:50.700 align:start position:0% physical attacker then user confirmation 00:03:50.700 --> 00:03:52.820 align:start position:0% physical attacker then user confirmation is<00:03:50.940> extremely<00:03:51.780> important<00:03:52.170> as<00:03:52.290> well<00:03:52.500> because 00:03:52.820 --> 00:03:52.830 align:start position:0% is extremely important as well because 00:03:52.830 --> 00:03:54.650 align:start position:0% is extremely important as well because if<00:03:52.980> you<00:03:53.070> want<00:03:53.220> crave<00:03:53.490> is<00:03:53.610> holding<00:03:53.970> keys<00:03:54.240> but 00:03:54.650 --> 00:03:54.660 align:start position:0% if you want crave is holding keys but 00:03:54.660 --> 00:03:57.230 align:start position:0% if you want crave is holding keys but users<00:03:55.080> can<00:03:55.560> an<00:03:55.860> attacker<00:03:56.160> or<00:03:56.580> malware<00:03:57.030> can 00:03:57.230 --> 00:03:57.240 align:start position:0% users can an attacker or malware can 00:03:57.240 --> 00:03:59.810 align:start position:0% users can an attacker or malware can sign<00:03:57.480> anything<00:03:57.960> it's<00:03:58.800> not<00:03:59.040> very<00:03:59.250> secure<00:03:59.430> so 00:03:59.810 --> 00:03:59.820 align:start position:0% sign anything it's not very secure so 00:03:59.820 --> 00:04:01.340 align:start position:0% sign anything it's not very secure so you<00:03:59.970> should<00:04:00.240> be<00:04:00.390> able<00:04:00.480> to<00:04:00.630> confirm<00:04:01.140> what<00:04:01.320> you 00:04:01.340 --> 00:04:01.350 align:start position:0% you should be able to confirm what you 00:04:01.350 --> 00:04:03.260 align:start position:0% you should be able to confirm what you are<00:04:01.530> doing<00:04:01.650> and<00:04:01.950> you<00:04:02.100> should<00:04:02.310> be<00:04:02.460> it<00:04:02.970> shouldn't 00:04:03.260 --> 00:04:03.270 align:start position:0% are doing and you should be it shouldn't 00:04:03.270 --> 00:04:05.150 align:start position:0% are doing and you should be it shouldn't be<00:04:03.450> possible<00:04:03.600> to<00:04:03.990> fake<00:04:04.230> this<00:04:04.410> confirmation<00:04:05.040> if 00:04:05.150 --> 00:04:05.160 align:start position:0% be possible to fake this confirmation if 00:04:05.160 --> 00:04:08.000 align:start position:0% be possible to fake this confirmation if your<00:04:05.310> malware<00:04:05.700> then<00:04:06.390> flexibility<00:04:07.140> you<00:04:07.800> should 00:04:08.000 --> 00:04:08.010 align:start position:0% your malware then flexibility you should 00:04:08.010 --> 00:04:09.650 align:start position:0% your malware then flexibility you should be<00:04:08.160> able<00:04:08.220> to<00:04:08.400> do<00:04:08.550> software<00:04:08.940> updates<00:04:09.360> on<00:04:09.600> your 00:04:09.650 --> 00:04:09.660 align:start position:0% be able to do software updates on your 00:04:09.660 --> 00:04:12.980 align:start position:0% be able to do software updates on your hard<00:04:10.200> wallet<00:04:10.620> Enclave<00:04:11.370> anytime<00:04:12.150> so<00:04:12.480> even<00:04:12.870> if 00:04:12.980 --> 00:04:12.990 align:start position:0% hard wallet Enclave anytime so even if 00:04:12.990 --> 00:04:14.900 align:start position:0% hard wallet Enclave anytime so even if your<00:04:13.170> computer<00:04:13.290> is<00:04:13.740> compromised<00:04:14.280> which<00:04:14.730> is 00:04:14.900 --> 00:04:14.910 align:start position:0% your computer is compromised which is 00:04:14.910 --> 00:04:18.410 align:start position:0% your computer is compromised which is quite<00:04:15.210> important<00:04:15.720> and<00:04:16.190> as<00:04:17.190> a<00:04:17.609> developer<00:04:18.239> you 00:04:18.410 --> 00:04:18.420 align:start position:0% quite important and as a developer you 00:04:18.420 --> 00:04:19.610 align:start position:0% quite important and as a developer you should<00:04:18.450> be<00:04:18.780> able<00:04:18.870> to<00:04:18.989> test<00:04:19.350> new 00:04:19.610 --> 00:04:19.620 align:start position:0% should be able to test new 00:04:19.620 --> 00:04:22.370 align:start position:0% should be able to test new functionalities<00:04:20.390> typically<00:04:21.390> for<00:04:21.570> atrium<00:04:21.989> if 00:04:22.370 --> 00:04:22.380 align:start position:0% functionalities typically for atrium if 00:04:22.380 --> 00:04:24.170 align:start position:0% functionalities typically for atrium if you<00:04:22.620> want<00:04:22.770> clave<00:04:23.040> is<00:04:23.250> signing<00:04:23.669> an<00:04:23.820> interim 00:04:24.170 --> 00:04:24.180 align:start position:0% you want clave is signing an interim 00:04:24.180 --> 00:04:25.940 align:start position:0% you want clave is signing an interim transaction<00:04:24.780> it<00:04:24.930> should<00:04:25.140> be<00:04:25.290> able<00:04:25.380> to<00:04:25.500> support 00:04:25.940 --> 00:04:25.950 align:start position:0% transaction it should be able to support 00:04:25.950 --> 00:04:27.500 align:start position:0% transaction it should be able to support smart<00:04:26.610> contracts<00:04:27.150> and 00:04:27.500 --> 00:04:27.510 align:start position:0% smart contracts and 00:04:27.510 --> 00:04:30.440 align:start position:0% smart contracts and should<00:04:27.720> be<00:04:27.870> able<00:04:27.960> if<00:04:28.490> possible<00:04:29.490> to<00:04:30.180> display 00:04:30.440 --> 00:04:30.450 align:start position:0% should be able if possible to display 00:04:30.450 --> 00:04:32.630 align:start position:0% should be able if possible to display specific<00:04:30.810> UX<00:04:31.410> for<00:04:31.860> specific<00:04:32.280> smartphone 00:04:32.630 --> 00:04:32.640 align:start position:0% specific UX for specific smartphone 00:04:32.640 --> 00:04:35.000 align:start position:0% specific UX for specific smartphone twice<00:04:32.850> in<00:04:33.510> order<00:04:33.750> to<00:04:33.900> provide<00:04:34.260> always<00:04:34.770> the 00:04:35.000 --> 00:04:35.010 align:start position:0% twice in order to provide always the 00:04:35.010 --> 00:04:36.830 align:start position:0% twice in order to provide always the best<00:04:35.280> and<00:04:35.550> the<00:04:35.670> clearest<00:04:36.090> message<00:04:36.330> to<00:04:36.720> the 00:04:36.830 --> 00:04:36.840 align:start position:0% best and the clearest message to the 00:04:36.840 --> 00:04:38.800 align:start position:0% best and the clearest message to the user<00:04:37.020> to<00:04:37.350> know<00:04:37.500> what<00:04:37.680> you<00:04:37.770> are<00:04:37.830> doing 00:04:38.800 --> 00:04:38.810 align:start position:0% user to know what you are doing 00:04:38.810 --> 00:04:42.650 align:start position:0% user to know what you are doing finally<00:04:40.160> remote<00:04:41.160> at<00:04:41.310> the<00:04:41.400> station<00:04:41.850> we<00:04:42.480> should 00:04:42.650 --> 00:04:42.660 align:start position:0% finally remote at the station we should 00:04:42.660 --> 00:04:46.580 align:start position:0% finally remote at the station we should have<00:04:42.810> a<00:04:42.870> way<00:04:43.080> in<00:04:43.350> an<00:04:43.710> enclave<00:04:44.040> or<00:04:44.460> in<00:04:45.110> like<00:04:46.110> we 00:04:46.580 --> 00:04:46.590 align:start position:0% have a way in an enclave or in like we 00:04:46.590 --> 00:04:48.350 align:start position:0% have a way in an enclave or in like we have<00:04:46.740> in<00:04:46.920> the<00:04:47.040> device<00:04:47.340> to<00:04:47.640> verify<00:04:48.030> that<00:04:48.060> the 00:04:48.350 --> 00:04:48.360 align:start position:0% have in the device to verify that the 00:04:48.360 --> 00:04:50.060 align:start position:0% have in the device to verify that the code<00:04:48.570> is<00:04:48.600> running<00:04:48.990> and<00:04:49.140> a<00:04:49.170> healthy<00:04:49.560> platform 00:04:50.060 --> 00:04:50.070 align:start position:0% code is running and a healthy platform 00:04:50.070 --> 00:04:51.710 align:start position:0% code is running and a healthy platform and<00:04:50.340> that<00:04:50.610> you<00:04:50.760> are<00:04:50.880> running<00:04:51.090> the<00:04:51.300> right<00:04:51.480> code 00:04:51.710 --> 00:04:51.720 align:start position:0% and that you are running the right code 00:04:51.720 --> 00:04:53.330 align:start position:0% and that you are running the right code so<00:04:52.140> you<00:04:52.200> should<00:04:52.440> be<00:04:52.560> able<00:04:52.620> to<00:04:52.740> verify<00:04:52.920> which 00:04:53.330 --> 00:04:53.340 align:start position:0% so you should be able to verify which 00:04:53.340 --> 00:04:55.010 align:start position:0% so you should be able to verify which code<00:04:53.550> you're<00:04:53.700> running<00:04:53.970> and<00:04:54.330> we'll<00:04:54.780> see<00:04:54.990> that 00:04:55.010 --> 00:04:55.020 align:start position:0% code you're running and we'll see that 00:04:55.020 --> 00:04:58.250 align:start position:0% code you're running and we'll see that this<00:04:55.500> comes<00:04:55.800> with<00:04:56.070> with<00:04:56.700> some<00:04:57.260> difficulties 00:04:58.250 --> 00:04:58.260 align:start position:0% this comes with with some difficulties 00:04:58.260 --> 00:05:00.650 align:start position:0% this comes with with some difficulties on<00:04:58.410> HDX<00:04:58.860> but<00:04:59.190> we<00:04:59.370> can<00:04:59.520> help<00:04:59.880> solving<00:05:00.300> that<00:05:00.510> as 00:05:00.650 --> 00:05:00.660 align:start position:0% on HDX but we can help solving that as 00:05:00.660 --> 00:05:04.160 align:start position:0% on HDX but we can help solving that as well<00:05:01.370> so<00:05:02.370> today<00:05:02.670> in<00:05:02.790> our<00:05:02.880> architecture<00:05:03.240> the 00:05:04.160 --> 00:05:04.170 align:start position:0% well so today in our architecture the 00:05:04.170 --> 00:05:05.570 align:start position:0% well so today in our architecture the way<00:05:04.200> we<00:05:04.560> achieved<00:05:04.950> source<00:05:05.190> code<00:05:05.400> portability 00:05:05.570 --> 00:05:05.580 align:start position:0% way we achieved source code portability 00:05:05.580 --> 00:05:08.150 align:start position:0% way we achieved source code portability between<00:05:06.300> secure<00:05:06.780> element<00:05:06.870> and<00:05:07.230> enclaves<00:05:07.620> is 00:05:08.150 --> 00:05:08.160 align:start position:0% between secure element and enclaves is 00:05:08.160 --> 00:05:11.000 align:start position:0% between secure element and enclaves is quite<00:05:08.670> simple<00:05:09.210> we<00:05:09.750> focus<00:05:10.140> on<00:05:10.320> C<00:05:10.620> source<00:05:10.890> code 00:05:11.000 --> 00:05:11.010 align:start position:0% quite simple we focus on C source code 00:05:11.010 --> 00:05:13.310 align:start position:0% quite simple we focus on C source code portability<00:05:11.310> so<00:05:11.850> we<00:05:12.270> write<00:05:12.480> the<00:05:12.660> code<00:05:12.690> once 00:05:13.310 --> 00:05:13.320 align:start position:0% portability so we write the code once 00:05:13.320 --> 00:05:16.040 align:start position:0% portability so we write the code once with<00:05:14.190> the<00:05:14.280> same<00:05:14.460> API<00:05:14.760> when<00:05:15.450> we<00:05:15.600> work<00:05:15.780> natively 00:05:16.040 --> 00:05:16.050 align:start position:0% with the same API when we work natively 00:05:16.050 --> 00:05:17.900 align:start position:0% with the same API when we work natively on<00:05:16.380> the<00:05:16.620> secure<00:05:16.920> element<00:05:17.010> we<00:05:17.430> are<00:05:17.460> compiling 00:05:17.900 --> 00:05:17.910 align:start position:0% on the secure element we are compiling 00:05:17.910 --> 00:05:20.000 align:start position:0% on the secure element we are compiling to<00:05:18.060> arm<00:05:18.390> because<00:05:18.960> our<00:05:19.080> secure<00:05:19.530> element<00:05:19.620> are 00:05:20.000 --> 00:05:20.010 align:start position:0% to arm because our secure element are 00:05:20.010 --> 00:05:22.250 align:start position:0% to arm because our secure element are based<00:05:20.250> on<00:05:20.490> sicker<00:05:20.940> sicker<00:05:21.330> of<00:05:21.540> course<00:05:21.780> which 00:05:22.250 --> 00:05:22.260 align:start position:0% based on sicker sicker of course which 00:05:22.260 --> 00:05:25.670 align:start position:0% based on sicker sicker of course which is<00:05:22.440> a<00:05:22.610> kind<00:05:23.610> of<00:05:23.790> a<00:05:23.910> secure<00:05:24.210> arm<00:05:24.450> and<00:05:24.690> when<00:05:25.530> we 00:05:25.670 --> 00:05:25.680 align:start position:0% is a kind of a secure arm and when we 00:05:25.680 --> 00:05:27.380 align:start position:0% is a kind of a secure arm and when we are<00:05:25.770> working<00:05:25.950> on<00:05:26.190> an<00:05:26.280> enclave<00:05:26.670> all<00:05:26.970> kind<00:05:27.300> of 00:05:27.380 --> 00:05:27.390 align:start position:0% are working on an enclave all kind of 00:05:27.390 --> 00:05:31.070 align:start position:0% are working on an enclave all kind of Enclave<00:05:28.110> so<00:05:28.320> it<00:05:28.410> could<00:05:28.560> be<00:05:28.680> HDX<00:05:29.220> te<00:05:30.030> or<00:05:30.540> NHS<00:05:30.900> M 00:05:31.070 --> 00:05:31.080 align:start position:0% Enclave so it could be HDX te or NHS M 00:05:31.080 --> 00:05:34.460 align:start position:0% Enclave so it could be HDX te or NHS M we<00:05:31.740> are<00:05:31.770> cross<00:05:32.220> compiling<00:05:32.910> to<00:05:33.150> moxie<00:05:33.630> which<00:05:34.320> is 00:05:34.460 --> 00:05:34.470 align:start position:0% we are cross compiling to moxie which is 00:05:34.470 --> 00:05:36.080 align:start position:0% we are cross compiling to moxie which is an<00:05:34.560> open<00:05:34.800> architecture<00:05:35.040> which<00:05:35.610> was<00:05:35.670> used 00:05:36.080 --> 00:05:36.090 align:start position:0% an open architecture which was used 00:05:36.090 --> 00:05:38.660 align:start position:0% an open architecture which was used usually<00:05:36.360> in<00:05:36.660> which<00:05:37.320> was<00:05:37.470> used<00:05:37.710> previously<00:05:38.010> or 00:05:38.660 --> 00:05:38.670 align:start position:0% usually in which was used previously or 00:05:38.670 --> 00:05:40.880 align:start position:0% usually in which was used previously or in<00:05:38.820> the<00:05:39.030> Bitcoin<00:05:39.240> project<00:05:39.840> as<00:05:40.230> an<00:05:40.350> experiment 00:05:40.880 --> 00:05:40.890 align:start position:0% in the Bitcoin project as an experiment 00:05:40.890 --> 00:05:44.120 align:start position:0% in the Bitcoin project as an experiment by<00:05:41.040> Jeff<00:05:41.280> Kazik<00:05:41.640> back<00:05:42.300> in<00:05:42.420> the<00:05:42.540> days<00:05:42.890> but<00:05:43.890> it's 00:05:44.120 --> 00:05:44.130 align:start position:0% by Jeff Kazik back in the days but it's 00:05:44.130 --> 00:05:46.760 align:start position:0% by Jeff Kazik back in the days but it's very<00:05:44.280> simple<00:05:44.820> it's<00:05:45.000> very<00:05:45.170> easy<00:05:46.170> to<00:05:46.440> review 00:05:46.760 --> 00:05:46.770 align:start position:0% very simple it's very easy to review 00:05:46.770 --> 00:05:48.440 align:start position:0% very simple it's very easy to review easy<00:05:47.070> to<00:05:47.190> secure<00:05:47.490> as<00:05:47.640> well<00:05:47.820> so<00:05:48.090> it's<00:05:48.210> a<00:05:48.300> good 00:05:48.440 --> 00:05:48.450 align:start position:0% easy to secure as well so it's a good 00:05:48.450 --> 00:05:53.740 align:start position:0% easy to secure as well so it's a good target<00:05:48.660> if<00:05:48.990> you<00:05:49.140> want<00:05:49.350> to<00:05:49.500> have<00:05:49.650> a<00:05:49.710> simple<00:05:49.920> VM 00:05:53.740 --> 00:05:53.750 align:start position:0% 00:05:53.750 --> 00:05:56.690 align:start position:0% regarding<00:05:54.750> the<00:05:54.900> architecture<00:05:55.380> itself<00:05:55.700> we 00:05:56.690 --> 00:05:56.700 align:start position:0% regarding the architecture itself we 00:05:56.700 --> 00:05:59.120 align:start position:0% regarding the architecture itself we will<00:05:57.150> try<00:05:57.510> to<00:05:57.540> reuse<00:05:58.050> this<00:05:58.200> model<00:05:58.560> as<00:05:58.740> much<00:05:58.950> as 00:05:59.120 --> 00:05:59.130 align:start position:0% will try to reuse this model as much as 00:05:59.130 --> 00:06:01.130 align:start position:0% will try to reuse this model as much as we<00:05:59.250> can<00:05:59.430> so<00:06:00.060> we<00:06:00.180> want<00:06:00.390> to<00:06:00.510> protect<00:06:00.870> the<00:06:00.960> user 00:06:01.130 --> 00:06:01.140 align:start position:0% we can so we want to protect the user 00:06:01.140 --> 00:06:04.010 align:start position:0% we can so we want to protect the user secrets<00:06:01.700> the<00:06:02.700> user<00:06:02.970> secrets<00:06:03.480> will<00:06:03.720> sit 00:06:04.010 --> 00:06:04.020 align:start position:0% secrets the user secrets will sit 00:06:04.020 --> 00:06:06.250 align:start position:0% secrets the user secrets will sit between<00:06:04.710> a<00:06:04.950> kind<00:06:05.520> of<00:06:05.640> a<00:06:05.730> firewall 00:06:06.250 --> 00:06:06.260 align:start position:0% between a kind of a firewall 00:06:06.260 --> 00:06:08.180 align:start position:0% between a kind of a firewall applications<00:06:07.260> will<00:06:07.440> be<00:06:07.470> firewall<00:06:08.010> between 00:06:08.180 --> 00:06:08.190 align:start position:0% applications will be firewall between 00:06:08.190 --> 00:06:10.220 align:start position:0% applications will be firewall between each<00:06:08.520> other<00:06:08.700> as<00:06:08.880> well<00:06:09.120> and<00:06:09.300> when<00:06:10.110> an 00:06:10.220 --> 00:06:10.230 align:start position:0% each other as well and when an 00:06:10.230 --> 00:06:12.290 align:start position:0% each other as well and when an application<00:06:10.590> wants<00:06:11.010> to<00:06:11.190> access<00:06:11.430> some 00:06:12.290 --> 00:06:12.300 align:start position:0% application wants to access some 00:06:12.300 --> 00:06:15.380 align:start position:0% application wants to access some cryptographic<00:06:12.600> material<00:06:13.380> it<00:06:13.890> will<00:06:14.130> use<00:06:14.390> it 00:06:15.380 --> 00:06:15.390 align:start position:0% cryptographic material it will use it 00:06:15.390 --> 00:06:16.670 align:start position:0% cryptographic material it will use it will<00:06:15.660> use<00:06:15.780> a<00:06:15.810> service<00:06:16.200> call 00:06:16.670 --> 00:06:16.680 align:start position:0% will use a service call 00:06:16.680 --> 00:06:18.530 align:start position:0% will use a service call so<00:06:16.860> service<00:06:17.190> cool<00:06:17.340> on<00:06:17.460> arm<00:06:17.730> or<00:06:17.940> something<00:06:17.970> else 00:06:18.530 --> 00:06:18.540 align:start position:0% so service cool on arm or something else 00:06:18.540 --> 00:06:20.450 align:start position:0% so service cool on arm or something else Universal<00:06:19.320> machine<00:06:19.470> to<00:06:19.860> access<00:06:20.160> the<00:06:20.280> secrets 00:06:20.450 --> 00:06:20.460 align:start position:0% Universal machine to access the secrets 00:06:20.460 --> 00:06:23.240 align:start position:0% Universal machine to access the secrets so<00:06:21.000> applications<00:06:21.750> can't<00:06:22.140> touch<00:06:22.710> secret 00:06:23.240 --> 00:06:23.250 align:start position:0% so applications can't touch secret 00:06:23.250 --> 00:06:26.270 align:start position:0% so applications can't touch secret unless<00:06:23.600> the<00:06:24.600> interpreter<00:06:25.440> mode<00:06:25.680> which<00:06:25.890> is<00:06:26.070> run 00:06:26.270 --> 00:06:26.280 align:start position:0% unless the interpreter mode which is run 00:06:26.280 --> 00:06:28.550 align:start position:0% unless the interpreter mode which is run by<00:06:26.310> the<00:06:26.520> kernel<00:06:26.970> and<00:06:27.440> applications<00:06:28.440> are 00:06:28.550 --> 00:06:28.560 align:start position:0% by the kernel and applications are 00:06:28.560 --> 00:06:30.020 align:start position:0% by the kernel and applications are isolated<00:06:29.040> and<00:06:29.220> of<00:06:29.310> course<00:06:29.520> come<00:06:29.730> touch<00:06:30.000> a 00:06:30.020 --> 00:06:30.030 align:start position:0% isolated and of course come touch a 00:06:30.030 --> 00:06:37.040 align:start position:0% isolated and of course come touch a camel<00:06:33.530> so<00:06:34.530> if<00:06:35.130> we<00:06:35.340> look<00:06:35.490> at<00:06:35.640> the<00:06:35.760> state<00:06:36.030> of<00:06:36.240> our 00:06:37.040 --> 00:06:37.050 align:start position:0% camel so if we look at the state of our 00:06:37.050 --> 00:06:40.610 align:start position:0% camel so if we look at the state of our HDX<00:06:37.740> stack<00:06:38.010> in<00:06:38.190> 2017<00:06:39.090> we<00:06:39.780> had<00:06:39.870> good<00:06:40.080> points<00:06:40.530> and 00:06:40.610 --> 00:06:40.620 align:start position:0% HDX stack in 2017 we had good points and 00:06:40.620 --> 00:06:41.480 align:start position:0% HDX stack in 2017 we had good points and but 00:06:41.480 --> 00:06:41.490 align:start position:0% but 00:06:41.490 --> 00:06:44.180 align:start position:0% but so<00:06:42.060> the<00:06:42.240> first<00:06:42.510> good<00:06:42.750> point<00:06:43.020> is<00:06:43.320> that<00:06:43.350> it<00:06:43.890> works 00:06:44.180 --> 00:06:44.190 align:start position:0% so the first good point is that it works 00:06:44.190 --> 00:06:46.340 align:start position:0% so the first good point is that it works so<00:06:44.640> if<00:06:44.850> you<00:06:45.030> want<00:06:45.210> to<00:06:45.300> try<00:06:45.570> it<00:06:45.630> today<00:06:45.900> you<00:06:46.110> can 00:06:46.340 --> 00:06:46.350 align:start position:0% so if you want to try it today you can 00:06:46.350 --> 00:06:48.230 align:start position:0% so if you want to try it today you can do<00:06:46.470> something<00:06:46.830> you<00:06:47.040> can<00:06:47.490> run<00:06:47.670> some<00:06:47.850> simple 00:06:48.230 --> 00:06:48.240 align:start position:0% do something you can run some simple 00:06:48.240 --> 00:06:51.350 align:start position:0% do something you can run some simple applications<00:06:49.220> you<00:06:50.220> can<00:06:50.460> we<00:06:50.700> demonstrate<00:06:50.850> it 00:06:51.350 --> 00:06:51.360 align:start position:0% applications you can we demonstrate it 00:06:51.360 --> 00:06:52.940 align:start position:0% applications you can we demonstrate it on<00:06:51.510> China<00:06:51.840> at<00:06:51.930> the<00:06:52.050> station<00:06:52.410> so<00:06:52.680> you<00:06:52.710> can 00:06:52.940 --> 00:06:52.950 align:start position:0% on China at the station so you can 00:06:52.950 --> 00:06:55.370 align:start position:0% on China at the station so you can verify<00:06:53.220> that<00:06:53.430> your<00:06:53.730> Enclave<00:06:54.120> is<00:06:54.630> legitimate 00:06:55.370 --> 00:06:55.380 align:start position:0% verify that your Enclave is legitimate 00:06:55.380 --> 00:06:57.350 align:start position:0% verify that your Enclave is legitimate on<00:06:55.620> chain<00:06:55.980> after<00:06:56.580> you<00:06:56.700> pass<00:06:56.910> internet<00:06:57.330> a 00:06:57.350 --> 00:06:57.360 align:start position:0% on chain after you pass internet a 00:06:57.360 --> 00:06:59.570 align:start position:0% on chain after you pass internet a station<00:06:57.810> you<00:06:57.960> can<00:06:58.140> verify<00:06:58.320> that<00:06:58.680> your<00:06:58.860> code<00:06:59.070> is 00:06:59.570 --> 00:06:59.580 align:start position:0% station you can verify that your code is 00:06:59.580 --> 00:07:01.690 align:start position:0% station you can verify that your code is the<00:06:59.850> code<00:06:59.880> that<00:07:00.150> is<00:07:00.300> supposed<00:07:00.660> to<00:07:00.720> be<00:07:00.870> on<00:07:01.020> chain 00:07:01.690 --> 00:07:01.700 align:start position:0% the code that is supposed to be on chain 00:07:01.700 --> 00:07:05.000 align:start position:0% the code that is supposed to be on chain and<00:07:02.700> we<00:07:02.910> have<00:07:03.000> an<00:07:03.120> open<00:07:03.330> source<00:07:03.480> sdk<00:07:03.890> even<00:07:04.890> if 00:07:05.000 --> 00:07:05.010 align:start position:0% and we have an open source sdk even if 00:07:05.010 --> 00:07:06.410 align:start position:0% and we have an open source sdk even if the<00:07:05.130> code<00:07:05.310> is<00:07:05.340> deprecated<00:07:06.060> it's<00:07:06.210> still 00:07:06.410 --> 00:07:06.420 align:start position:0% the code is deprecated it's still 00:07:06.420 --> 00:07:08.360 align:start position:0% the code is deprecated it's still completely<00:07:06.870> usable<00:07:07.530> and<00:07:07.710> you<00:07:07.800> can<00:07:07.950> still<00:07:08.130> play 00:07:08.360 --> 00:07:08.370 align:start position:0% completely usable and you can still play 00:07:08.370 --> 00:07:12.320 align:start position:0% completely usable and you can still play with<00:07:08.400> it<00:07:08.640> on<00:07:08.930> the<00:07:09.930> bad<00:07:10.290> side<00:07:10.590> on<00:07:11.040> the<00:07:11.790> negative 00:07:12.320 --> 00:07:12.330 align:start position:0% with it on the bad side on the negative 00:07:12.330 --> 00:07:15.830 align:start position:0% with it on the bad side on the negative side<00:07:13.220> you<00:07:14.250> we<00:07:14.640> had<00:07:14.790> no<00:07:15.000> user<00:07:15.390> confirmation 00:07:15.830 --> 00:07:15.840 align:start position:0% side you we had no user confirmation 00:07:15.840 --> 00:07:18.830 align:start position:0% side you we had no user confirmation possible<00:07:16.500> since<00:07:16.980> we<00:07:17.160> didn't<00:07:17.460> have<00:07:17.580> a<00:07:17.940> display 00:07:18.830 --> 00:07:18.840 align:start position:0% possible since we didn't have a display 00:07:18.840 --> 00:07:21.920 align:start position:0% possible since we didn't have a display API<00:07:19.080> so<00:07:20.010> you<00:07:20.430> couldn't<00:07:20.730> use<00:07:21.270> it<00:07:21.420> really<00:07:21.750> as<00:07:21.900> a 00:07:21.920 --> 00:07:21.930 align:start position:0% API so you couldn't use it really as a 00:07:21.930 --> 00:07:27.140 align:start position:0% API so you couldn't use it really as a wallet<00:07:24.710> so<00:07:25.710> if<00:07:25.800> all<00:07:26.040> code<00:07:26.460> that<00:07:26.640> you<00:07:26.760> wanted<00:07:27.030> to 00:07:27.140 --> 00:07:27.150 align:start position:0% wallet so if all code that you wanted to 00:07:27.150 --> 00:07:29.000 align:start position:0% wallet so if all code that you wanted to run<00:07:27.360> on<00:07:27.510> the<00:07:27.630> Enclave<00:07:28.020> had<00:07:28.380> to<00:07:28.530> be<00:07:28.650> signed<00:07:28.890> by 00:07:29.000 --> 00:07:29.010 align:start position:0% run on the Enclave had to be signed by 00:07:29.010 --> 00:07:32.930 align:start position:0% run on the Enclave had to be signed by us<00:07:29.250> so<00:07:30.030> that<00:07:30.240> the<00:07:30.510> biggest<00:07:30.980> things<00:07:31.980> that<00:07:32.130> deter 00:07:32.930 --> 00:07:32.940 align:start position:0% us so that the biggest things that deter 00:07:32.940 --> 00:07:35.120 align:start position:0% us so that the biggest things that deter people<00:07:33.180> from<00:07:33.390> using<00:07:33.720> the<00:07:33.930> Enclave<00:07:34.290> because<00:07:35.010> at 00:07:35.120 --> 00:07:35.130 align:start position:0% people from using the Enclave because at 00:07:35.130 --> 00:07:37.130 align:start position:0% people from using the Enclave because at some<00:07:35.310> point<00:07:35.340> if<00:07:35.760> you<00:07:35.850> wanted<00:07:36.150> to<00:07:36.270> run<00:07:36.420> with<00:07:36.480> in 00:07:37.130 --> 00:07:37.140 align:start position:0% some point if you wanted to run with in 00:07:37.140 --> 00:07:39.200 align:start position:0% some point if you wanted to run with in a<00:07:37.200> protected<00:07:37.620> environment<00:07:37.760> you<00:07:38.760> had<00:07:38.880> to<00:07:39.030> send 00:07:39.200 --> 00:07:39.210 align:start position:0% a protected environment you had to send 00:07:39.210 --> 00:07:41.810 align:start position:0% a protected environment you had to send us<00:07:39.360> the<00:07:39.480> code<00:07:39.720> or<00:07:39.960> we<00:07:40.770> had<00:07:40.890> to<00:07:40.920> assign<00:07:41.430> a<00:07:41.460> key 00:07:41.810 --> 00:07:41.820 align:start position:0% us the code or we had to assign a key 00:07:41.820 --> 00:07:44.630 align:start position:0% us the code or we had to assign a key which<00:07:42.360> was<00:07:42.570> more<00:07:42.840> convenient<00:07:43.200> but<00:07:44.070> still<00:07:44.370> a 00:07:44.630 --> 00:07:44.640 align:start position:0% which was more convenient but still a 00:07:44.640 --> 00:07:46.430 align:start position:0% which was more convenient but still a lot<00:07:45.000> of<00:07:45.060> people<00:07:45.270> didn't<00:07:45.720> want<00:07:45.780> to<00:07:45.930> contact<00:07:46.320> us 00:07:46.430 --> 00:07:46.440 align:start position:0% lot of people didn't want to contact us 00:07:46.440 --> 00:07:49.220 align:start position:0% lot of people didn't want to contact us for<00:07:46.650> that<00:07:46.800> so<00:07:47.700> that's<00:07:48.000> why<00:07:48.240> in<00:07:48.510> my<00:07:48.720> opinion<00:07:48.750> it 00:07:49.220 --> 00:07:49.230 align:start position:0% for that so that's why in my opinion it 00:07:49.230 --> 00:07:52.190 align:start position:0% for that so that's why in my opinion it wasn't<00:07:49.440> very<00:07:49.650> popular<00:07:49.890> and<00:07:50.490> of<00:07:51.300> course<00:07:51.870> we<00:07:52.050> did 00:07:52.190 --> 00:07:52.200 align:start position:0% wasn't very popular and of course we did 00:07:52.200 --> 00:07:54.140 align:start position:0% wasn't very popular and of course we did no<00:07:52.350> security<00:07:52.830> audit<00:07:53.100> so<00:07:53.430> the<00:07:53.580> code<00:07:53.790> is<00:07:53.940> really 00:07:54.140 --> 00:07:54.150 align:start position:0% no security audit so the code is really 00:07:54.150 --> 00:07:57.350 align:start position:0% no security audit so the code is really sent<00:07:55.080> to<00:07:55.230> you<00:07:55.410> to<00:07:55.440> be<00:07:55.740> to<00:07:56.670> be<00:07:56.790> tried<00:07:57.120> and 00:07:57.350 --> 00:07:57.360 align:start position:0% sent to you to be to be tried and 00:07:57.360 --> 00:07:59.720 align:start position:0% sent to you to be to be tried and without<00:07:57.780> any<00:07:57.960> kind<00:07:58.140> of<00:07:58.290> guarantee<00:07:58.650> so<00:07:59.430> how<00:07:59.670> can 00:07:59.720 --> 00:07:59.730 align:start position:0% without any kind of guarantee so how can 00:07:59.730 --> 00:08:04.370 align:start position:0% without any kind of guarantee so how can we<00:08:00.030> improve<00:08:00.240> that<00:08:02.330> of<00:08:03.330> course<00:08:03.690> regarding<00:08:04.230> the 00:08:04.370 --> 00:08:04.380 align:start position:0% we improve that of course regarding the 00:08:04.380 --> 00:08:05.840 align:start position:0% we improve that of course regarding the attestation<00:08:04.620> well<00:08:05.310> people<00:08:05.610> have<00:08:05.790> been 00:08:05.840 --> 00:08:05.850 align:start position:0% attestation well people have been 00:08:05.850 --> 00:08:09.100 align:start position:0% attestation well people have been talking<00:08:06.360> about<00:08:07.040> Intel<00:08:08.040> at<00:08:08.280> the<00:08:08.490> station<00:08:08.850> a<00:08:08.880> lot 00:08:09.100 --> 00:08:09.110 align:start position:0% talking about Intel at the station a lot 00:08:09.110 --> 00:08:11.840 align:start position:0% talking about Intel at the station a lot so<00:08:10.110> the<00:08:10.230> thing<00:08:10.410> is<00:08:10.440> internet<00:08:11.130> station<00:08:11.580> today 00:08:11.840 --> 00:08:11.850 align:start position:0% so the thing is internet station today 00:08:11.850 --> 00:08:13.520 align:start position:0% so the thing is internet station today is<00:08:12.210> still<00:08:12.480> very<00:08:12.690> useful<00:08:12.930> in<00:08:13.380> my<00:08:13.500> opinion 00:08:13.520 --> 00:08:13.530 align:start position:0% is still very useful in my opinion 00:08:13.530 --> 00:08:15.560 align:start position:0% is still very useful in my opinion because<00:08:14.280> you<00:08:14.580> need<00:08:14.970> to<00:08:15.090> validate<00:08:15.270> the 00:08:15.560 --> 00:08:15.570 align:start position:0% because you need to validate the 00:08:15.570 --> 00:08:17.690 align:start position:0% because you need to validate the platform<00:08:15.990> house<00:08:16.200> from<00:08:16.470> time<00:08:16.650> to<00:08:16.830> time<00:08:16.860> for 00:08:17.690 --> 00:08:17.700 align:start position:0% platform house from time to time for 00:08:17.700 --> 00:08:19.250 align:start position:0% platform house from time to time for example<00:08:17.850> when<00:08:18.150> there<00:08:18.480> is<00:08:18.570> a<00:08:18.600> new<00:08:18.840> security 00:08:19.250 --> 00:08:19.260 align:start position:0% example when there is a new security 00:08:19.260 --> 00:08:21.710 align:start position:0% example when there is a new security exploit<00:08:19.620> that<00:08:19.740> involves<00:08:20.460> updating<00:08:21.270> your<00:08:21.450> bios 00:08:21.710 --> 00:08:21.720 align:start position:0% exploit that involves updating your bios 00:08:21.720 --> 00:08:24.680 align:start position:0% exploit that involves updating your bios updating<00:08:22.590> the<00:08:22.740> microcode<00:08:23.190> of<00:08:23.310> your<00:08:23.460> cpu<00:08:23.850> the 00:08:24.680 --> 00:08:24.690 align:start position:0% updating the microcode of your cpu the 00:08:24.690 --> 00:08:26.840 align:start position:0% updating the microcode of your cpu the only<00:08:24.900> way<00:08:25.020> to<00:08:25.080> know<00:08:26.010> that<00:08:26.040> is<00:08:26.490> to<00:08:26.670> have<00:08:26.820> a 00:08:26.840 --> 00:08:26.850 align:start position:0% only way to know that is to have a 00:08:26.850 --> 00:08:29.600 align:start position:0% only way to know that is to have a centralized<00:08:27.420> API<00:08:27.960> at<00:08:28.170> some<00:08:28.350> point<00:08:28.590> so<00:08:29.370> it's 00:08:29.600 --> 00:08:29.610 align:start position:0% centralized API at some point so it's 00:08:29.610 --> 00:08:32.240 align:start position:0% centralized API at some point so it's still<00:08:29.850> used<00:08:30.060> today<00:08:30.240> but<00:08:31.020> you<00:08:31.440> can<00:08:31.680> select 00:08:32.240 --> 00:08:32.250 align:start position:0% still used today but you can select 00:08:32.250 --> 00:08:34.520 align:start position:0% still used today but you can select different<00:08:32.820> setups<00:08:33.479> depending<00:08:34.020> what<00:08:34.140> you<00:08:34.320> want 00:08:34.520 --> 00:08:34.530 align:start position:0% different setups depending what you want 00:08:34.530 --> 00:08:36.650 align:start position:0% different setups depending what you want for<00:08:34.740> your<00:08:34.890> application<00:08:35.430> when<00:08:36.060> you<00:08:36.090> are<00:08:36.330> using 00:08:36.650 --> 00:08:36.660 align:start position:0% for your application when you are using 00:08:36.660 --> 00:08:41.900 align:start position:0% for your application when you are using your<00:08:36.990> Enclave<00:08:39.740> so<00:08:40.740> if<00:08:41.039> you<00:08:41.160> don't<00:08:41.340> want<00:08:41.580> to<00:08:41.729> use 00:08:41.900 --> 00:08:41.910 align:start position:0% your Enclave so if you don't want to use 00:08:41.910 --> 00:08:44.810 align:start position:0% your Enclave so if you don't want to use internet<00:08:42.330> a<00:08:42.360> station<00:08:42.810> you<00:08:43.320> can<00:08:43.560> it<00:08:43.919> works<00:08:44.190> the 00:08:44.810 --> 00:08:44.820 align:start position:0% internet a station you can it works the 00:08:44.820 --> 00:08:46.400 align:start position:0% internet a station you can it works the code<00:08:45.060> is<00:08:45.180> still<00:08:45.330> secure<00:08:45.690> because<00:08:46.050> the<00:08:46.200> code<00:08:46.380> is 00:08:46.400 --> 00:08:46.410 align:start position:0% code is still secure because the code is 00:08:46.410 --> 00:08:48.530 align:start position:0% code is still secure because the code is signed<00:08:46.800> so<00:08:47.010> you<00:08:47.100> can<00:08:47.280> verify<00:08:47.490> you<00:08:47.760> can<00:08:48.150> rebuild 00:08:48.530 --> 00:08:48.540 align:start position:0% signed so you can verify you can rebuild 00:08:48.540 --> 00:08:50.000 align:start position:0% signed so you can verify you can rebuild the<00:08:48.750> code<00:08:48.960> on<00:08:49.080> your<00:08:49.110> side<00:08:49.440> and<00:08:49.680> verify<00:08:49.980> that 00:08:50.000 --> 00:08:50.010 align:start position:0% the code on your side and verify that 00:08:50.010 --> 00:08:52.220 align:start position:0% the code on your side and verify that the<00:08:50.250> crisco<00:08:50.700> right<00:08:50.850> but<00:08:51.450> in<00:08:51.600> this<00:08:51.720> case<00:08:51.990> you 00:08:52.220 --> 00:08:52.230 align:start position:0% the crisco right but in this case you 00:08:52.230 --> 00:08:54.370 align:start position:0% the crisco right but in this case you don't<00:08:52.410> get<00:08:52.560> remote<00:08:52.950> at<00:08:53.070> the<00:08:53.100> station<00:08:53.490> at<00:08:53.610> all 00:08:54.370 --> 00:08:54.380 align:start position:0% don't get remote at the station at all 00:08:54.380 --> 00:08:56.170 align:start position:0% don't get remote at the station at all it's<00:08:54.620> a<00:08:54.710> choice<00:08:54.920> if<00:08:55.490> you<00:08:55.610> want<00:08:55.760> to<00:08:55.880> run<00:08:56.000> your 00:08:56.170 --> 00:08:56.180 align:start position:0% it's a choice if you want to run your 00:08:56.180 --> 00:08:57.550 align:start position:0% it's a choice if you want to run your wallet<00:08:56.450> on<00:08:56.570> your<00:08:56.720> side<00:08:56.900> you<00:08:57.050> can<00:08:57.200> do<00:08:57.380> that 00:08:57.550 --> 00:08:57.560 align:start position:0% wallet on your side you can do that 00:08:57.560 --> 00:08:59.740 align:start position:0% wallet on your side you can do that maybe<00:08:58.460> not<00:08:58.730> the<00:08:58.880> best<00:08:58.910> choice<00:08:59.150> but<00:08:59.540> it's<00:08:59.690> a 00:08:59.740 --> 00:08:59.750 align:start position:0% maybe not the best choice but it's a 00:08:59.750 --> 00:09:02.260 align:start position:0% maybe not the best choice but it's a choice<00:08:59.990> you<00:09:00.980> can<00:09:01.160> run<00:09:01.370> internet<00:09:01.850> sensation 00:09:02.260 --> 00:09:02.270 align:start position:0% choice you can run internet sensation 00:09:02.270 --> 00:09:04.780 align:start position:0% choice you can run internet sensation once<00:09:02.540> if<00:09:02.870> you<00:09:02.930> do<00:09:03.230> that<00:09:03.440> you<00:09:03.590> get<00:09:03.710> a<00:09:03.770> week<00:09:04.100> later 00:09:04.780 --> 00:09:04.790 align:start position:0% once if you do that you get a week later 00:09:04.790 --> 00:09:06.850 align:start position:0% once if you do that you get a week later at<00:09:05.000> the<00:09:05.030> station<00:09:05.180> I<00:09:05.600> put<00:09:05.840> week<00:09:06.080> here<00:09:06.440> because 00:09:06.850 --> 00:09:06.860 align:start position:0% at the station I put week here because 00:09:06.860 --> 00:09:09.850 align:start position:0% at the station I put week here because it<00:09:07.670> will<00:09:07.910> not<00:09:08.240> be<00:09:08.630> up<00:09:08.780> to<00:09:08.960> date<00:09:09.110> regarding<00:09:09.740> the 00:09:09.850 --> 00:09:09.860 align:start position:0% it will not be up to date regarding the 00:09:09.860 --> 00:09:11.140 align:start position:0% it will not be up to date regarding the health<00:09:10.100> of<00:09:10.220> your<00:09:10.400> platform<00:09:10.790> which<00:09:10.940> can<00:09:11.120> change 00:09:11.140 --> 00:09:11.150 align:start position:0% health of your platform which can change 00:09:11.150 --> 00:09:14.950 align:start position:0% health of your platform which can change so<00:09:12.140> again<00:09:12.860> it's<00:09:13.010> a<00:09:13.100> choice<00:09:13.240> but<00:09:14.240> if<00:09:14.540> you<00:09:14.810> do 00:09:14.950 --> 00:09:14.960 align:start position:0% so again it's a choice but if you do 00:09:14.960 --> 00:09:16.840 align:start position:0% so again it's a choice but if you do internet<00:09:15.440> if<00:09:15.710> you<00:09:15.830> run<00:09:16.040> internet<00:09:16.460> sensation 00:09:16.840 --> 00:09:16.850 align:start position:0% internet if you run internet sensation 00:09:16.850 --> 00:09:18.310 align:start position:0% internet if you run internet sensation from<00:09:17.030> time<00:09:17.180> to<00:09:17.360> time<00:09:17.390> then<00:09:17.840> you<00:09:17.960> can<00:09:18.110> get<00:09:18.260> a 00:09:18.310 --> 00:09:18.320 align:start position:0% from time to time then you can get a 00:09:18.320 --> 00:09:20.890 align:start position:0% from time to time then you can get a stronger<00:09:18.620> attestation<00:09:19.100> and<00:09:19.420> the<00:09:20.420> biggest 00:09:20.890 --> 00:09:20.900 align:start position:0% stronger attestation and the biggest 00:09:20.900 --> 00:09:21.940 align:start position:0% stronger attestation and the biggest difference<00:09:21.410> here 00:09:21.940 --> 00:09:21.950 align:start position:0% difference here 00:09:21.950 --> 00:09:24.610 align:start position:0% difference here according<00:09:22.610> to<00:09:22.640> compare<00:09:23.480> to<00:09:23.810> is<00:09:24.320> at<00:09:24.530> the 00:09:24.610 --> 00:09:24.620 align:start position:0% according to compare to is at the 00:09:24.620 --> 00:09:26.830 align:start position:0% according to compare to is at the station<00:09:24.830> today<00:09:25.250> is<00:09:25.520> that<00:09:25.970> it's<00:09:26.360> something<00:09:26.600> you 00:09:26.830 --> 00:09:26.840 align:start position:0% station today is that it's something you 00:09:26.840 --> 00:09:34.330 align:start position:0% station today is that it's something you can<00:09:26.990> validate<00:09:27.200> on<00:09:27.530> chain<00:09:31.930> so<00:09:33.130> the<00:09:34.130> good<00:09:34.310> news 00:09:34.330 --> 00:09:34.340 align:start position:0% can validate on chain so the good news 00:09:34.340 --> 00:09:37.450 align:start position:0% can validate on chain so the good news is<00:09:35.090> that<00:09:35.150> with<00:09:35.870> a<00:09:35.900> new<00:09:36.140> in<00:09:36.470> therapy<00:09:36.950> I<00:09:36.980> call 00:09:37.450 --> 00:09:37.460 align:start position:0% is that with a new in therapy I call 00:09:37.460 --> 00:09:39.820 align:start position:0% is that with a new in therapy I call protected<00:09:38.030> connection<00:09:38.510> display<00:09:38.870> we<00:09:39.530> can 00:09:39.820 --> 00:09:39.830 align:start position:0% protected connection display we can 00:09:39.830 --> 00:09:42.580 align:start position:0% protected connection display we can solve<00:09:40.430> two<00:09:41.180> problems<00:09:41.210> so<00:09:41.930> we<00:09:42.080> can<00:09:42.230> solve<00:09:42.440> the 00:09:42.580 --> 00:09:42.590 align:start position:0% solve two problems so we can solve the 00:09:42.590 --> 00:09:44.860 align:start position:0% solve two problems so we can solve the confirmation<00:09:43.190> if<00:09:43.310> you<00:09:43.490> and<00:09:43.790> we<00:09:43.910> can<00:09:44.090> solve<00:09:44.690> the 00:09:44.860 --> 00:09:44.870 align:start position:0% confirmation if you and we can solve the 00:09:44.870 --> 00:09:47.290 align:start position:0% confirmation if you and we can solve the fact<00:09:45.140> that<00:09:45.260> you<00:09:46.250> couldn't<00:09:46.490> run<00:09:46.760> on<00:09:46.940> any<00:09:47.150> moose 00:09:47.290 --> 00:09:47.300 align:start position:0% fact that you couldn't run on any moose 00:09:47.300 --> 00:09:50.380 align:start position:0% fact that you couldn't run on any moose code<00:09:47.570> so<00:09:48.500> far<00:09:48.770> so<00:09:49.160> now<00:09:49.340> you<00:09:49.940> won't<00:09:50.120> have<00:09:50.240> to 00:09:50.380 --> 00:09:50.390 align:start position:0% code so far so now you won't have to 00:09:50.390 --> 00:09:51.760 align:start position:0% code so far so now you won't have to contact<00:09:50.720> us<00:09:50.870> to<00:09:51.020> run<00:09:51.170> your<00:09:51.350> code<00:09:51.500> on<00:09:51.650> the 00:09:51.760 --> 00:09:51.770 align:start position:0% contact us to run your code on the 00:09:51.770 --> 00:09:56.380 align:start position:0% contact us to run your code on the Enclave<00:09:52.160> once<00:09:52.460> this<00:09:52.790> is<00:09:52.970> released<00:09:54.100> so<00:09:55.100> if<00:09:56.060> we 00:09:56.380 --> 00:09:56.390 align:start position:0% Enclave once this is released so if we 00:09:56.390 --> 00:09:59.170 align:start position:0% Enclave once this is released so if we want<00:09:56.600> to<00:09:56.690> summarize<00:09:57.190> very<00:09:58.190> quickly<00:09:58.340> get<00:09:58.970> an 00:09:59.170 --> 00:09:59.180 align:start position:0% want to summarize very quickly get an 00:09:59.180 --> 00:10:00.700 align:start position:0% want to summarize very quickly get an overview<00:09:59.420> of<00:09:59.690> protected<00:10:00.290> transaction 00:10:00.700 --> 00:10:00.710 align:start position:0% overview of protected transaction 00:10:00.710 --> 00:10:03.790 align:start position:0% overview of protected transaction display<00:10:01.240> it<00:10:02.240> will<00:10:02.510> be<00:10:02.630> a<00:10:02.660> way<00:10:02.900> to<00:10:02.930> create<00:10:03.530> a 00:10:03.790 --> 00:10:03.800 align:start position:0% display it will be a way to create a 00:10:03.800 --> 00:10:06.670 align:start position:0% display it will be a way to create a secure<00:10:04.610> display<00:10:05.390> to<00:10:06.140> display<00:10:06.440> something 00:10:06.670 --> 00:10:06.680 align:start position:0% secure display to display something 00:10:06.680 --> 00:10:09.160 align:start position:0% secure display to display something securely<00:10:07.280> so<00:10:07.640> on<00:10:07.820> your<00:10:08.030> own<00:10:08.090> device<00:10:08.300> that<00:10:08.990> will 00:10:09.160 --> 00:10:09.170 align:start position:0% securely so on your own device that will 00:10:09.170 --> 00:10:12.250 align:start position:0% securely so on your own device that will be<00:10:09.400> prepared<00:10:10.400> by<00:10:10.460> the<00:10:10.610> Enclave<00:10:11.060> so<00:10:11.960> the<00:10:12.110> way 00:10:12.250 --> 00:10:12.260 align:start position:0% be prepared by the Enclave so the way 00:10:12.260 --> 00:10:15.040 align:start position:0% be prepared by the Enclave so the way this<00:10:12.320> works<00:10:12.650> is<00:10:13.130> that<00:10:13.210> PTD<00:10:14.210> will<00:10:14.480> allow<00:10:14.810> you<00:10:14.870> to 00:10:15.040 --> 00:10:15.050 align:start position:0% this works is that PTD will allow you to 00:10:15.050 --> 00:10:19.660 align:start position:0% this works is that PTD will allow you to create<00:10:16.750> confidential<00:10:17.750> output<00:10:18.110> on<00:10:18.320> display<00:10:18.830> so 00:10:19.660 --> 00:10:19.670 align:start position:0% create confidential output on display so 00:10:19.670 --> 00:10:22.750 align:start position:0% create confidential output on display so the<00:10:19.700> display<00:10:20.210> here<00:10:20.570> is<00:10:20.960> a<00:10:21.020> mixed<00:10:21.530> display<00:10:22.160> in 00:10:22.750 --> 00:10:22.760 align:start position:0% the display here is a mixed display in 00:10:22.760 --> 00:10:24.880 align:start position:0% the display here is a mixed display in this<00:10:22.940> window<00:10:23.360> you<00:10:23.480> have<00:10:23.540> a<00:10:23.630> mixed<00:10:23.960> display<00:10:24.380> so 00:10:24.880 --> 00:10:24.890 align:start position:0% this window you have a mixed display so 00:10:24.890 --> 00:10:27.640 align:start position:0% this window you have a mixed display so some<00:10:25.250> is<00:10:25.520> done<00:10:25.820> by<00:10:25.970> PTD<00:10:26.420> so<00:10:26.690> can't<00:10:26.990> be<00:10:27.260> spied<00:10:27.620> on 00:10:27.640 --> 00:10:27.650 align:start position:0% some is done by PTD so can't be spied on 00:10:27.650 --> 00:10:30.550 align:start position:0% some is done by PTD so can't be spied on by<00:10:27.860> the<00:10:28.160> host<00:10:28.580> so<00:10:29.330> PIN<00:10:29.540> pad<00:10:29.720> here<00:10:30.110> is<00:10:30.230> done<00:10:30.410> by 00:10:30.550 --> 00:10:30.560 align:start position:0% by the host so PIN pad here is done by 00:10:30.560 --> 00:10:33.220 align:start position:0% by the host so PIN pad here is done by PTD<00:10:31.010> this<00:10:31.670> line<00:10:31.910> is<00:10:32.090> displayed<00:10:32.330> by<00:10:32.630> PT<00:10:32.930> d<00:10:33.050> and 00:10:33.220 --> 00:10:33.230 align:start position:0% PTD this line is displayed by PT d and 00:10:33.230 --> 00:10:34.870 align:start position:0% PTD this line is displayed by PT d and this<00:10:33.320> line<00:10:33.560> is<00:10:33.590> displayed<00:10:33.920> by<00:10:34.220> PT<00:10:34.490> D<00:10:34.580> as<00:10:34.700> well 00:10:34.870 --> 00:10:34.880 align:start position:0% this line is displayed by PT D as well 00:10:34.880 --> 00:10:39.040 align:start position:0% this line is displayed by PT D as well the<00:10:35.540> buttons<00:10:35.900> are<00:10:36.110> not<00:10:36.260> and<00:10:36.620> this<00:10:37.630> label<00:10:38.630> and 00:10:39.040 --> 00:10:39.050 align:start position:0% the buttons are not and this label and 00:10:39.050 --> 00:10:45.430 align:start position:0% the buttons are not and this label and string<00:10:40.240> are<00:10:41.240> not<00:10:42.670> so<00:10:43.670> the<00:10:44.540> input<00:10:44.870> the<00:10:45.410> output 00:10:45.430 --> 00:10:45.440 align:start position:0% string are not so the input the output 00:10:45.440 --> 00:10:47.470 align:start position:0% string are not so the input the output is<00:10:45.890> confidential<00:10:46.520> because<00:10:46.880> the<00:10:47.000> host<00:10:47.240> cannot 00:10:47.470 --> 00:10:47.480 align:start position:0% is confidential because the host cannot 00:10:47.480 --> 00:10:50.710 align:start position:0% is confidential because the host cannot read<00:10:47.750> anything<00:10:47.960> and<00:10:48.640> with<00:10:49.640> the<00:10:50.090> fact<00:10:50.390> that<00:10:50.510> you 00:10:50.710 --> 00:10:50.720 align:start position:0% read anything and with the fact that you 00:10:50.720 --> 00:10:53.860 align:start position:0% read anything and with the fact that you can<00:10:50.900> display<00:10:51.320> a<00:10:51.980> pin<00:10:52.940> code<00:10:53.150> that<00:10:53.390> is<00:10:53.540> randomly 00:10:53.860 --> 00:10:53.870 align:start position:0% can display a pin code that is randomly 00:10:53.870 --> 00:10:55.630 align:start position:0% can display a pin code that is randomly swap<00:10:54.200> by<00:10:54.410> PT<00:10:54.740> D<00:10:54.890> you<00:10:55.310> can<00:10:55.520> achieve 00:10:55.630 --> 00:10:55.640 align:start position:0% swap by PT D you can achieve 00:10:55.640 --> 00:10:57.940 align:start position:0% swap by PT D you can achieve confidential<00:10:56.390> input<00:10:56.690> as<00:10:56.810> well<00:10:57.020> because<00:10:57.800> if 00:10:57.940 --> 00:10:57.950 align:start position:0% confidential input as well because if 00:10:57.950 --> 00:10:59.650 align:start position:0% confidential input as well because if for<00:10:57.980> example<00:10:58.160> here<00:10:58.760> you<00:10:58.880> type<00:10:59.120> your<00:10:59.240> PIN<00:10:59.420> code 00:10:59.650 --> 00:10:59.660 align:start position:0% for example here you type your PIN code 00:10:59.660 --> 00:11:01.960 align:start position:0% for example here you type your PIN code so<00:11:00.200> host<00:11:00.410> has<00:11:00.590> asked<00:11:00.920> no<00:11:01.220> way<00:11:01.370> to<00:11:01.430> know<00:11:01.760> that 00:11:01.960 --> 00:11:01.970 align:start position:0% so host has asked no way to know that 00:11:01.970 --> 00:11:04.120 align:start position:0% so host has asked no way to know that you<00:11:02.090> typed<00:11:02.330> one<00:11:02.600> two<00:11:02.810> three<00:11:03.020> four<00:11:03.290> if<00:11:03.740> you<00:11:03.920> kick 00:11:04.120 --> 00:11:04.130 align:start position:0% you typed one two three four if you kick 00:11:04.130 --> 00:11:05.800 align:start position:0% you typed one two three four if you kick that<00:11:04.160> I<00:11:04.550> mean<00:11:04.760> the<00:11:04.880> host<00:11:05.090> will<00:11:05.270> just<00:11:05.510> see<00:11:05.660> that 00:11:05.800 --> 00:11:05.810 align:start position:0% that I mean the host will just see that 00:11:05.810 --> 00:11:07.280 align:start position:0% that I mean the host will just see that you<00:11:05.930> clicked<00:11:06.200> some 00:11:07.280 --> 00:11:07.290 align:start position:0% you clicked some 00:11:07.290 --> 00:11:09.530 align:start position:0% you clicked some turns<00:11:07.500> on<00:11:07.620> your<00:11:07.770> screen<00:11:08.070> but<00:11:08.610> this<00:11:09.180> way<00:11:09.480> you 00:11:09.530 --> 00:11:09.540 align:start position:0% turns on your screen but this way you 00:11:09.540 --> 00:11:11.540 align:start position:0% turns on your screen but this way you can<00:11:09.900> manage<00:11:10.170> to<00:11:10.290> have<00:11:10.650> some<00:11:10.860> securing<00:11:11.310> put 00:11:11.540 --> 00:11:11.550 align:start position:0% can manage to have some securing put 00:11:11.550 --> 00:11:14.110 align:start position:0% can manage to have some securing put even<00:11:12.360> if<00:11:12.450> it's<00:11:12.630> not<00:11:12.810> very<00:11:13.110> convenient<00:11:13.770> and 00:11:14.110 --> 00:11:14.120 align:start position:0% even if it's not very convenient and 00:11:14.120 --> 00:11:17.360 align:start position:0% even if it's not very convenient and here<00:11:15.120> we<00:11:15.690> have<00:11:15.870> a<00:11:16.230> way<00:11:16.590> to<00:11:16.650> display<00:11:17.130> some 00:11:17.360 --> 00:11:17.370 align:start position:0% here we have a way to display some 00:11:17.370 --> 00:11:21.680 align:start position:0% here we have a way to display some additional<00:11:17.760> data<00:11:18.000> on<00:11:18.450> PTD<00:11:19.410> so<00:11:20.390> you<00:11:21.390> see<00:11:21.570> an 00:11:21.680 --> 00:11:21.690 align:start position:0% additional data on PTD so you see an 00:11:21.690 --> 00:11:26.330 align:start position:0% additional data on PTD so you see an amount<00:11:21.960> which<00:11:22.200> is<00:11:23.190> an<00:11:23.460> amount<00:11:23.820> of<00:11:25.190> 0.096 00:11:26.330 --> 00:11:26.340 align:start position:0% amount which is an amount of 0.096 00:11:26.340 --> 00:11:28.640 align:start position:0% amount which is an amount of 0.096 errors<00:11:26.790> so<00:11:27.600> here<00:11:27.930> you<00:11:28.050> see<00:11:28.200> the<00:11:28.320> number<00:11:28.560> of 00:11:28.640 --> 00:11:28.650 align:start position:0% errors so here you see the number of 00:11:28.650 --> 00:11:30.800 align:start position:0% errors so here you see the number of decimal<00:11:29.100> below<00:11:29.430> which<00:11:29.970> is<00:11:30.150> again<00:11:30.450> not<00:11:30.480> the 00:11:30.800 --> 00:11:30.810 align:start position:0% decimal below which is again not the 00:11:30.810 --> 00:11:34.220 align:start position:0% decimal below which is again not the best<00:11:30.990> UI<00:11:31.230> but<00:11:31.590> well<00:11:32.010> I'm<00:11:32.600> that's<00:11:33.600> what<00:11:33.930> you<00:11:34.080> can 00:11:34.220 --> 00:11:34.230 align:start position:0% best UI but well I'm that's what you can 00:11:34.230 --> 00:11:36.410 align:start position:0% best UI but well I'm that's what you can do<00:11:34.410> today<00:11:34.560> and<00:11:35.010> part<00:11:35.640> of<00:11:35.790> a<00:11:35.880> native<00:11:36.150> remedy 00:11:36.410 --> 00:11:36.420 align:start position:0% do today and part of a native remedy 00:11:36.420 --> 00:11:38.300 align:start position:0% do today and part of a native remedy right<00:11:36.600> so<00:11:36.900> after<00:11:37.050> you<00:11:37.500> do<00:11:37.620> that<00:11:37.650> after<00:11:38.040> you 00:11:38.300 --> 00:11:38.310 align:start position:0% right so after you do that after you 00:11:38.310 --> 00:11:40.790 align:start position:0% right so after you do that after you enter<00:11:38.580> your<00:11:38.730> PIN<00:11:38.910> wallet<00:11:39.750> codes<00:11:40.110> and<00:11:40.380> hand<00:11:40.710> it 00:11:40.790 --> 00:11:40.800 align:start position:0% enter your PIN wallet codes and hand it 00:11:40.800 --> 00:11:47.000 align:start position:0% enter your PIN wallet codes and hand it around<00:11:41.130> addiction<00:11:45.710> limitations<00:11:46.710> we<00:11:46.890> have 00:11:47.000 --> 00:11:47.010 align:start position:0% around addiction limitations we have 00:11:47.010 --> 00:11:49.910 align:start position:0% around addiction limitations we have repeatedly<00:11:47.580> today<00:11:47.810> they<00:11:48.810> eat<00:11:48.990> the<00:11:49.320> output<00:11:49.770> is 00:11:49.910 --> 00:11:49.920 align:start position:0% repeatedly today they eat the output is 00:11:49.920 --> 00:11:51.950 align:start position:0% repeatedly today they eat the output is confidential<00:11:50.550> so<00:11:50.760> the<00:11:50.940> output<00:11:51.450> cannot<00:11:51.720> be 00:11:51.950 --> 00:11:51.960 align:start position:0% confidential so the output cannot be 00:11:51.960 --> 00:11:54.500 align:start position:0% confidential so the output cannot be spied<00:11:52.200> on<00:11:52.230> but<00:11:53.130> it<00:11:53.670> cannot<00:11:53.880> be<00:11:54.060> trusted 00:11:54.500 --> 00:11:54.510 align:start position:0% spied on but it cannot be trusted 00:11:54.510 --> 00:11:56.480 align:start position:0% spied on but it cannot be trusted because<00:11:55.050> you<00:11:55.230> can<00:11:55.380> still<00:11:55.740> display<00:11:56.190> something 00:11:56.480 --> 00:11:56.490 align:start position:0% because you can still display something 00:11:56.490 --> 00:11:58.940 align:start position:0% because you can still display something on<00:11:56.820> top<00:11:57.090> of<00:11:57.270> the<00:11:57.420> output<00:11:57.750> so<00:11:58.380> in<00:11:58.500> this<00:11:58.650> case 00:11:58.940 --> 00:11:58.950 align:start position:0% on top of the output so in this case 00:11:58.950 --> 00:12:01.340 align:start position:0% on top of the output so in this case that's<00:11:59.160> why<00:11:59.490> we<00:12:00.090> are<00:12:00.210> do<00:12:00.390> that's<00:12:00.780> why<00:12:00.990> we<00:12:01.230> are 00:12:01.340 --> 00:12:01.350 align:start position:0% that's why we are do that's why we are 00:12:01.350 --> 00:12:02.900 align:start position:0% that's why we are do that's why we are you<00:12:01.590> have<00:12:01.740> to<00:12:01.920> do<00:12:02.070> this<00:12:02.280> user<00:12:02.490> confirmation 00:12:02.900 --> 00:12:02.910 align:start position:0% you have to do this user confirmation 00:12:02.910 --> 00:12:06.740 align:start position:0% you have to do this user confirmation twice<00:12:03.590> so<00:12:04.590> it's<00:12:04.800> not<00:12:05.070> the<00:12:05.310> best<00:12:05.490> you<00:12:06.330> expose 00:12:06.740 --> 00:12:06.750 align:start position:0% twice so it's not the best you expose 00:12:06.750 --> 00:12:09.260 align:start position:0% twice so it's not the best you expose evil<00:12:07.050> but<00:12:07.800> I<00:12:07.830> would<00:12:08.220> say<00:12:08.370> it<00:12:08.490> works<00:12:08.790> with<00:12:09.030> what 00:12:09.260 --> 00:12:09.270 align:start position:0% evil but I would say it works with what 00:12:09.270 --> 00:12:12.560 align:start position:0% evil but I would say it works with what is<00:12:09.420> available<00:12:09.510> there<00:12:10.440> so<00:12:10.760> the<00:12:11.760> IO<00:12:11.910> primitives 00:12:12.560 --> 00:12:12.570 align:start position:0% is available there so the IO primitives 00:12:12.570 --> 00:12:14.540 align:start position:0% is available there so the IO primitives are<00:12:12.720> very<00:12:12.930> limited<00:12:13.080> today<00:12:13.500> that's<00:12:14.130> probably 00:12:14.540 --> 00:12:14.550 align:start position:0% are very limited today that's probably 00:12:14.550 --> 00:12:17.000 align:start position:0% are very limited today that's probably something<00:12:14.790> that<00:12:14.970> can<00:12:15.240> change<00:12:15.650> but<00:12:16.650> you<00:12:16.830> don't 00:12:17.000 --> 00:12:17.010 align:start position:0% something that can change but you don't 00:12:17.010 --> 00:12:18.950 align:start position:0% something that can change but you don't have<00:12:17.130> the<00:12:17.280> flexibility<00:12:17.820> of<00:12:17.970> global<00:12:18.480> platform 00:12:18.950 --> 00:12:18.960 align:start position:0% have the flexibility of global platform 00:12:18.960 --> 00:12:22.670 align:start position:0% have the flexibility of global platform te<00:12:19.590> twisted<00:12:20.280> UI<00:12:20.460> if<00:12:20.730> you<00:12:20.910> want<00:12:21.210> so<00:12:22.020> one<00:12:22.380> thing 00:12:22.670 --> 00:12:22.680 align:start position:0% te twisted UI if you want so one thing 00:12:22.680 --> 00:12:24.980 align:start position:0% te twisted UI if you want so one thing that's<00:12:22.860> popular<00:12:23.370> in<00:12:23.400> with<00:12:23.970> the<00:12:24.060> CPI<00:12:24.420> is<00:12:24.570> to 00:12:24.980 --> 00:12:24.990 align:start position:0% that's popular in with the CPI is to 00:12:24.990 --> 00:12:26.570 align:start position:0% that's popular in with the CPI is to basically<00:12:25.170> register<00:12:25.890> an<00:12:26.040> image<00:12:26.310> on<00:12:26.490> the 00:12:26.570 --> 00:12:26.580 align:start position:0% basically register an image on the 00:12:26.580 --> 00:12:28.970 align:start position:0% basically register an image on the server<00:12:26.790> and<00:12:27.120> then<00:12:27.570> this<00:12:27.810> play<00:12:28.020> this<00:12:28.080> image<00:12:28.470> so 00:12:28.970 --> 00:12:28.980 align:start position:0% server and then this play this image so 00:12:28.980 --> 00:12:30.470 align:start position:0% server and then this play this image so you<00:12:29.040> can<00:12:29.280> be<00:12:29.460> sure<00:12:29.670> that<00:12:29.700> nobody<00:12:30.090> can 00:12:30.470 --> 00:12:30.480 align:start position:0% you can be sure that nobody can 00:12:30.480 --> 00:12:33.680 align:start position:0% you can be sure that nobody can intercept<00:12:31.050> the<00:12:31.170> image<00:12:31.440> and<00:12:31.850> a<00:12:32.850> malware<00:12:33.450> on<00:12:33.540> the 00:12:33.680 --> 00:12:33.690 align:start position:0% intercept the image and a malware on the 00:12:33.690 --> 00:12:35.720 align:start position:0% intercept the image and a malware on the host<00:12:33.930> could<00:12:34.230> not<00:12:34.440> replace<00:12:34.800> it<00:12:34.980> was<00:12:35.130> the<00:12:35.250> UI<00:12:35.430> but 00:12:35.720 --> 00:12:35.730 align:start position:0% host could not replace it was the UI but 00:12:35.730 --> 00:12:40.940 align:start position:0% host could not replace it was the UI but you<00:12:35.910> can't<00:12:36.120> in<00:12:36.270> that<00:12:36.420> case<00:12:38.390> so<00:12:39.390> that's<00:12:39.630> why<00:12:39.950> you 00:12:40.940 --> 00:12:40.950 align:start position:0% you can't in that case so that's why you 00:12:40.950 --> 00:12:43.130 align:start position:0% you can't in that case so that's why you have<00:12:41.130> to<00:12:41.280> add<00:12:41.370> the<00:12:41.490> user<00:12:41.670> type<00:12:42.090> again<00:12:42.840> and 00:12:43.130 --> 00:12:43.140 align:start position:0% have to add the user type again and 00:12:43.140 --> 00:12:46.040 align:start position:0% have to add the user type again and confirm<00:12:43.380> twice<00:12:44.300> which<00:12:45.300> is<00:12:45.330> not<00:12:45.840> the<00:12:46.020> most 00:12:46.040 --> 00:12:46.050 align:start position:0% confirm twice which is not the most 00:12:46.050 --> 00:12:49.670 align:start position:0% confirm twice which is not the most convenient<00:12:46.530> thing<00:12:46.710> but<00:12:47.160> it<00:12:47.730> works<00:12:48.410> so<00:12:49.410> the 00:12:49.670 --> 00:12:49.680 align:start position:0% convenient thing but it works so the 00:12:49.680 --> 00:12:51.950 align:start position:0% convenient thing but it works so the alternative<00:12:50.070> options<00:12:50.550> you<00:12:50.700> can<00:12:50.880> think<00:12:51.330> of<00:12:51.570> or 00:12:51.950 --> 00:12:51.960 align:start position:0% alternative options you can think of or 00:12:51.960 --> 00:12:53.890 align:start position:0% alternative options you can think of or at<00:12:52.260> least<00:12:52.500> I<00:12:52.590> can<00:12:52.770> think<00:12:52.980> of<00:12:53.100> hours<00:12:53.490> and 00:12:53.890 --> 00:12:53.900 align:start position:0% at least I can think of hours and 00:12:53.900 --> 00:12:56.960 align:start position:0% at least I can think of hours and typically<00:12:54.900> if<00:12:55.200> I<00:12:55.320> want<00:12:55.590> a<00:12:55.770> user<00:12:55.980> to<00:12:56.430> if<00:12:56.670> I<00:12:56.790> want 00:12:56.960 --> 00:12:56.970 align:start position:0% typically if I want a user to if I want 00:12:56.970 --> 00:12:58.850 align:start position:0% typically if I want a user to if I want to<00:12:57.090> use<00:12:57.240> it<00:12:57.390> to<00:12:57.510> verify<00:12:57.690> that<00:12:57.960> was<00:12:58.440> the<00:12:58.560> UI<00:12:58.710> is 00:12:58.850 --> 00:12:58.860 align:start position:0% to use it to verify that was the UI is 00:12:58.860 --> 00:13:00.890 align:start position:0% to use it to verify that was the UI is genuine<00:12:59.400> you<00:12:59.610> would<00:13:00.150> have<00:13:00.270> to<00:13:00.420> train<00:13:00.720> your 00:13:00.890 --> 00:13:00.900 align:start position:0% genuine you would have to train your 00:13:00.900 --> 00:13:03.440 align:start position:0% genuine you would have to train your users<00:13:00.960> to<00:13:01.320> try<00:13:02.070> to<00:13:02.130> take<00:13:02.550> screenshots<00:13:03.150> for 00:13:03.440 --> 00:13:03.450 align:start position:0% users to try to take screenshots for 00:13:03.450 --> 00:13:05.060 align:start position:0% users to try to take screenshots for example<00:13:03.870> and<00:13:04.110> see<00:13:04.350> that<00:13:04.530> the<00:13:04.650> contact 00:13:05.060 --> 00:13:05.070 align:start position:0% example and see that the contact 00:13:05.070 --> 00:13:06.890 align:start position:0% example and see that the contact screenshots<00:13:05.610> so<00:13:05.850> that's<00:13:06.120> not<00:13:06.300> something<00:13:06.570> is 00:13:06.890 --> 00:13:06.900 align:start position:0% screenshots so that's not something is 00:13:06.900 --> 00:13:09.110 align:start position:0% screenshots so that's not something is really<00:13:07.230> realistic<00:13:07.860> I<00:13:07.980> mean<00:13:08.130> geeks<00:13:08.820> can 00:13:09.110 --> 00:13:09.120 align:start position:0% really realistic I mean geeks can 00:13:09.120 --> 00:13:11.150 align:start position:0% really realistic I mean geeks can probably<00:13:09.360> do<00:13:09.690> that<00:13:09.840> but<00:13:10.410> that's<00:13:10.950> a<00:13:11.040> regular 00:13:11.150 --> 00:13:11.160 align:start position:0% probably do that but that's a regular 00:13:11.160 --> 00:13:14.240 align:start position:0% probably do that but that's a regular user<00:13:11.520> and<00:13:11.880> so<00:13:12.780> five<00:13:12.990> windows<00:13:13.440> only<00:13:13.590> so<00:13:14.010> if<00:13:14.100> you 00:13:14.240 --> 00:13:14.250 align:start position:0% user and so five windows only so if you 00:13:14.250 --> 00:13:16.250 align:start position:0% user and so five windows only so if you want<00:13:14.430> to<00:13:14.520> run<00:13:14.670> those<00:13:14.850> tests<00:13:15.150> you<00:13:15.840> can't<00:13:16.080> want 00:13:16.250 --> 00:13:16.260 align:start position:0% want to run those tests you can't want 00:13:16.260 --> 00:13:18.920 align:start position:0% want to run those tests you can't want them<00:13:16.410> online<00:13:16.530> X<00:13:16.910> that<00:13:17.910> will<00:13:18.300> probably<00:13:18.720> change 00:13:18.920 --> 00:13:18.930 align:start position:0% them online X that will probably change 00:13:18.930 --> 00:13:23.350 align:start position:0% them online X that will probably change over<00:13:19.200> time<00:13:19.350> as<00:13:19.530> well 00:13:23.350 --> 00:13:23.360 align:start position:0% 00:13:23.360 --> 00:13:25.970 align:start position:0% we<00:13:24.360> are<00:13:24.510> still<00:13:24.780> to<00:13:25.020> one<00:13:25.260> part<00:13:25.560> we<00:13:25.710> are<00:13:25.770> still 00:13:25.970 --> 00:13:25.980 align:start position:0% we are still to one part we are still 00:13:25.980 --> 00:13:28.670 align:start position:0% we are still to one part we are still missing<00:13:26.130> compared<00:13:26.790> to<00:13:26.850> 2017<00:13:27.780> is<00:13:27.990> a<00:13:28.020> security 00:13:28.670 --> 00:13:28.680 align:start position:0% missing compared to 2017 is a security 00:13:28.680 --> 00:13:31.310 align:start position:0% missing compared to 2017 is a security audit<00:13:28.770> and<00:13:29.130> that's<00:13:30.090> what<00:13:30.390> we<00:13:30.690> will<00:13:31.170> be 00:13:31.310 --> 00:13:31.320 align:start position:0% audit and that's what we will be 00:13:31.320 --> 00:13:32.930 align:start position:0% audit and that's what we will be focusing<00:13:31.740> on<00:13:31.950> right<00:13:31.980> now<00:13:32.190> and<00:13:32.640> that's<00:13:32.820> the 00:13:32.930 --> 00:13:32.940 align:start position:0% focusing on right now and that's the 00:13:32.940 --> 00:13:34.940 align:start position:0% focusing on right now and that's the reason<00:13:33.210> why<00:13:33.390> I<00:13:33.420> didn't<00:13:34.380> update<00:13:34.650> the<00:13:34.770> code 00:13:34.940 --> 00:13:34.950 align:start position:0% reason why I didn't update the code 00:13:34.950 --> 00:13:37.370 align:start position:0% reason why I didn't update the code because<00:13:35.760> we<00:13:36.060> didn't<00:13:36.330> run<00:13:36.510> our<00:13:36.690> security<00:13:37.080> audit 00:13:37.370 --> 00:13:37.380 align:start position:0% because we didn't run our security audit 00:13:37.380 --> 00:13:41.210 align:start position:0% because we didn't run our security audit yet<00:13:37.620> so<00:13:38.360> on<00:13:39.360> the<00:13:39.840> first<00:13:40.110> part<00:13:40.590> of<00:13:40.740> the<00:13:40.860> security 00:13:41.210 --> 00:13:41.220 align:start position:0% yet so on the first part of the security 00:13:41.220 --> 00:13:42.710 align:start position:0% yet so on the first part of the security audit<00:13:41.460> you<00:13:41.730> want<00:13:41.940> to<00:13:42.060> run<00:13:42.240> that<00:13:42.450> like<00:13:42.690> a 00:13:42.710 --> 00:13:42.720 align:start position:0% audit you want to run that like a 00:13:42.720 --> 00:13:44.600 align:start position:0% audit you want to run that like a standard<00:13:43.170> security<00:13:43.650> audit<00:13:43.980> so<00:13:44.190> you<00:13:44.250> want<00:13:44.490> to 00:13:44.600 --> 00:13:44.610 align:start position:0% standard security audit so you want to 00:13:44.610 --> 00:13:46.010 align:start position:0% standard security audit so you want to verify<00:13:44.730> that<00:13:45.000> your<00:13:45.300> own<00:13:45.390> clave<00:13:45.660> is<00:13:45.810> not 00:13:46.010 --> 00:13:46.020 align:start position:0% verify that your own clave is not 00:13:46.020 --> 00:13:47.690 align:start position:0% verify that your own clave is not vulnerable<00:13:46.140> to<00:13:46.560> typical<00:13:47.220> bugs 00:13:47.690 --> 00:13:47.700 align:start position:0% vulnerable to typical bugs 00:13:47.700 --> 00:13:50.360 align:start position:0% vulnerable to typical bugs buffer<00:13:48.420> overflows<00:13:48.870> and<00:13:49.110> so<00:13:49.410> on<00:13:49.530> so<00:13:50.160> that's 00:13:50.360 --> 00:13:50.370 align:start position:0% buffer overflows and so on so that's 00:13:50.370 --> 00:13:54.220 align:start position:0% buffer overflows and so on so that's very<00:13:50.940> very<00:13:51.270> normal<00:13:51.620> then<00:13:52.620> you<00:13:53.130> want<00:13:53.370> to<00:13:53.430> verify 00:13:54.220 --> 00:13:54.230 align:start position:0% very very normal then you want to verify 00:13:54.230 --> 00:13:57.680 align:start position:0% very very normal then you want to verify something<00:13:55.230> more<00:13:55.740> you<00:13:56.670> want<00:13:56.910> to<00:13:57.060> see<00:13:57.270> if<00:13:57.540> your 00:13:57.680 --> 00:13:57.690 align:start position:0% something more you want to see if your 00:13:57.690 --> 00:14:00.020 align:start position:0% something more you want to see if your key<00:13:57.960> can<00:13:58.290> withstand<00:13:58.680> server<00:13:59.460> side<00:13:59.730> channel 00:14:00.020 --> 00:14:00.030 align:start position:0% key can withstand server side channel 00:14:00.030 --> 00:14:02.450 align:start position:0% key can withstand server side channel attacks<00:14:00.380> because<00:14:01.380> side<00:14:01.590> channel<00:14:01.860> attacks<00:14:02.190> got 00:14:02.450 --> 00:14:02.460 align:start position:0% attacks because side channel attacks got 00:14:02.460 --> 00:14:05.900 align:start position:0% attacks because side channel attacks got very<00:14:02.730> popular<00:14:02.970> during<00:14:03.870> last<00:14:04.170> year<00:14:04.440> so<00:14:05.430> more 00:14:05.900 --> 00:14:05.910 align:start position:0% very popular during last year so more 00:14:05.910 --> 00:14:07.670 align:start position:0% very popular during last year so more and<00:14:05.940> more<00:14:06.090> people<00:14:06.330> I've<00:14:06.630> been<00:14:06.660> able<00:14:06.870> to<00:14:07.050> have 00:14:07.670 --> 00:14:07.680 align:start position:0% and more people I've been able to have 00:14:07.680 --> 00:14:10.310 align:start position:0% and more people I've been able to have been<00:14:07.860> demonstrating<00:14:08.670> ways<00:14:09.360> to<00:14:09.690> extract<00:14:09.930> keys 00:14:10.310 --> 00:14:10.320 align:start position:0% been demonstrating ways to extract keys 00:14:10.320 --> 00:14:12.650 align:start position:0% been demonstrating ways to extract keys from<00:14:10.950> enclaves<00:14:11.430> either<00:14:11.760> by<00:14:12.090> attacking<00:14:12.420> the 00:14:12.650 --> 00:14:12.660 align:start position:0% from enclaves either by attacking the 00:14:12.660 --> 00:14:14.570 align:start position:0% from enclaves either by attacking the Enclave<00:14:12.990> from<00:14:13.140> another<00:14:13.470> one<00:14:13.710> of<00:14:13.950> whom<00:14:14.460> the 00:14:14.570 --> 00:14:14.580 align:start position:0% Enclave from another one of whom the 00:14:14.580 --> 00:14:17.600 align:start position:0% Enclave from another one of whom the host<00:14:14.790> and<00:14:15.140> today<00:14:16.140> that<00:14:16.320> was<00:14:16.440> still<00:14:16.710> a<00:14:16.950> state<00:14:17.400> of 00:14:17.600 --> 00:14:17.610 align:start position:0% host and today that was still a state of 00:14:17.610 --> 00:14:20.780 align:start position:0% host and today that was still a state of the<00:14:17.760> art<00:14:17.790> to<00:14:18.270> be<00:14:18.420> written<00:14:18.570> to<00:14:18.930> know<00:14:19.560> if<00:14:19.890> keys 00:14:20.780 --> 00:14:20.790 align:start position:0% the art to be written to know if keys 00:14:20.790 --> 00:14:22.460 align:start position:0% the art to be written to know if keys are<00:14:21.000> correctly<00:14:21.360> protected<00:14:21.870> in<00:14:22.020> an<00:14:22.140> enclave 00:14:22.460 --> 00:14:22.470 align:start position:0% are correctly protected in an enclave 00:14:22.470 --> 00:14:24.740 align:start position:0% are correctly protected in an enclave and<00:14:22.770> we<00:14:23.280> aren't<00:14:23.520> we<00:14:23.880> are<00:14:24.000> very<00:14:24.210> interested<00:14:24.420> to 00:14:24.740 --> 00:14:24.750 align:start position:0% and we aren't we are very interested to 00:14:24.750 --> 00:14:26.990 align:start position:0% and we aren't we are very interested to answer<00:14:25.560> this<00:14:25.710> question<00:14:25.860> we're<00:14:26.760> very 00:14:26.990 --> 00:14:27.000 align:start position:0% answer this question we're very 00:14:27.000 --> 00:14:29.030 align:start position:0% answer this question we're very interested<00:14:27.180> to<00:14:27.450> publish<00:14:27.930> result<00:14:28.320> and<00:14:28.680> we<00:14:28.860> want 00:14:29.030 --> 00:14:29.040 align:start position:0% interested to publish result and we want 00:14:29.040 --> 00:14:30.790 align:start position:0% interested to publish result and we want to<00:14:29.190> advance<00:14:29.550> the<00:14:29.880> state<00:14:30.060> of<00:14:30.120> the<00:14:30.390> art<00:14:30.540> of 00:14:30.790 --> 00:14:30.800 align:start position:0% to advance the state of the art of 00:14:30.800 --> 00:14:35.660 align:start position:0% to advance the state of the art of protecting<00:14:31.800> key<00:14:32.010> and<00:14:32.190> Enclave<00:14:32.870> so<00:14:34.490> good<00:14:35.490> news 00:14:35.660 --> 00:14:35.670 align:start position:0% protecting key and Enclave so good news 00:14:35.670 --> 00:14:39.410 align:start position:0% protecting key and Enclave so good news is<00:14:35.880> that<00:14:36.030> we<00:14:36.660> are<00:14:36.810> I<00:14:37.080> think<00:14:37.890> good<00:14:38.280> at<00:14:38.430> it<00:14:38.580> at 00:14:39.410 --> 00:14:39.420 align:start position:0% is that we are I think good at it at 00:14:39.420 --> 00:14:41.180 align:start position:0% is that we are I think good at it at least<00:14:39.720> we<00:14:39.870> already<00:14:40.140> did<00:14:40.320> it<00:14:40.440> on<00:14:40.590> hardware<00:14:41.010> so 00:14:41.180 --> 00:14:41.190 align:start position:0% least we already did it on hardware so 00:14:41.190 --> 00:14:42.680 align:start position:0% least we already did it on hardware so we<00:14:41.220> should<00:14:41.520> be<00:14:41.640> able<00:14:41.730> to<00:14:41.850> do<00:14:42.060> it<00:14:42.210> and<00:14:42.360> bigger 00:14:42.680 --> 00:14:42.690 align:start position:0% we should be able to do it and bigger 00:14:42.690 --> 00:14:46.430 align:start position:0% we should be able to do it and bigger hollow<00:14:42.960> as<00:14:43.170> well<00:14:43.380> and<00:14:44.340> I<00:14:45.270> just<00:14:45.720> run<00:14:46.110> them<00:14:46.320> at 00:14:46.430 --> 00:14:46.440 align:start position:0% hollow as well and I just run them at 00:14:46.440 --> 00:14:48.530 align:start position:0% hollow as well and I just run them at the<00:14:46.530> adjustment<00:14:47.010> which<00:14:47.160> is<00:14:47.190> not<00:14:47.610> very<00:14:48.000> related 00:14:48.530 --> 00:14:48.540 align:start position:0% the adjustment which is not very related 00:14:48.540 --> 00:14:50.930 align:start position:0% the adjustment which is not very related to<00:14:48.720> side<00:14:48.960> channel<00:14:49.320> on<00:14:49.590> a<00:14:49.650> cache<00:14:50.010> but<00:14:50.670> it's<00:14:50.850> a 00:14:50.930 --> 00:14:50.940 align:start position:0% to side channel on a cache but it's a 00:14:50.940 --> 00:14:52.430 align:start position:0% to side channel on a cache but it's a general<00:14:51.300> Zhai<00:14:51.540> channel<00:14:51.840> api<00:14:52.110> that<00:14:52.230> we 00:14:52.430 --> 00:14:52.440 align:start position:0% general Zhai channel api that we 00:14:52.440 --> 00:14:54.620 align:start position:0% general Zhai channel api that we published<00:14:52.890> a<00:14:53.010> few<00:14:53.190> days<00:14:53.370> ago<00:14:53.610> that<00:14:53.880> will<00:14:54.480> let 00:14:54.620 --> 00:14:54.630 align:start position:0% published a few days ago that will let 00:14:54.630 --> 00:14:57.860 align:start position:0% published a few days ago that will let you<00:14:54.780> test<00:14:55.050> on<00:14:55.910> state<00:14:56.910> of<00:14:57.060> the<00:14:57.210> art<00:14:57.330> state 00:14:57.860 --> 00:14:57.870 align:start position:0% you test on state of the art state 00:14:57.870 --> 00:15:06.140 align:start position:0% you test on state of the art state channel<00:14:58.260> on<00:14:58.470> completing<00:15:03.380> so<00:15:04.380> how<00:15:05.250> can<00:15:05.550> we<00:15:05.760> how 00:15:06.140 --> 00:15:06.150 align:start position:0% channel on completing so how can we how 00:15:06.150 --> 00:15:07.730 align:start position:0% channel on completing so how can we how will<00:15:06.390> we<00:15:06.570> proceed<00:15:06.780> with<00:15:07.140> this<00:15:07.230> audit 00:15:07.730 --> 00:15:07.740 align:start position:0% will we proceed with this audit 00:15:07.740 --> 00:15:10.070 align:start position:0% will we proceed with this audit so<00:15:08.400> first<00:15:08.730> we'll<00:15:08.940> focus<00:15:09.330> on<00:15:09.450> a<00:15:09.480> single<00:15:09.690> curve 00:15:10.070 --> 00:15:10.080 align:start position:0% so first we'll focus on a single curve 00:15:10.080 --> 00:15:13.640 align:start position:0% so first we'll focus on a single curve will<00:15:10.470> focus<00:15:10.830> on<00:15:11.010> SEC<00:15:11.220> P<00:15:11.400> 256<00:15:12.060> K<00:15:12.690> 1<00:15:12.870> which<00:15:13.440> is<00:15:13.620> a 00:15:13.640 --> 00:15:13.650 align:start position:0% will focus on SEC P 256 K 1 which is a 00:15:13.650 --> 00:15:16.070 align:start position:0% will focus on SEC P 256 K 1 which is a curved<00:15:13.980> used<00:15:14.250> by<00:15:14.520> a<00:15:14.850> lot<00:15:15.210> of<00:15:15.240> kryptos<00:15:15.720> today<00:15:16.020> so 00:15:16.070 --> 00:15:16.080 align:start position:0% curved used by a lot of kryptos today so 00:15:16.080 --> 00:15:18.980 align:start position:0% curved used by a lot of kryptos today so at<00:15:16.440> least<00:15:16.620> Bitcoin<00:15:17.100> and<00:15:17.280> aetherium<00:15:17.730> so<00:15:18.090> for 00:15:18.980 --> 00:15:18.990 align:start position:0% at least Bitcoin and aetherium so for 00:15:18.990 --> 00:15:20.810 align:start position:0% at least Bitcoin and aetherium so for the<00:15:19.080> time<00:15:19.290> being<00:15:19.590> that<00:15:19.890> the<00:15:20.100> curve<00:15:20.430> we<00:15:20.610> are<00:15:20.700> the 00:15:20.810 --> 00:15:20.820 align:start position:0% the time being that the curve we are the 00:15:20.820 --> 00:15:22.910 align:start position:0% the time being that the curve we are the most<00:15:21.000> interested<00:15:21.450> in<00:15:21.540> we<00:15:22.320> will<00:15:22.470> review<00:15:22.830> the 00:15:22.910 --> 00:15:22.920 align:start position:0% most interested in we will review the 00:15:22.920 --> 00:15:24.800 align:start position:0% most interested in we will review the state-of-the-art<00:15:23.610> library<00:15:23.940> used<00:15:24.480> to<00:15:24.690> dye 00:15:24.800 --> 00:15:24.810 align:start position:0% state-of-the-art library used to dye 00:15:24.810 --> 00:15:27.470 align:start position:0% state-of-the-art library used to dye power<00:15:25.050> by<00:15:25.410> multiple<00:15:25.860> project<00:15:26.340> coming<00:15:27.210> from 00:15:27.470 --> 00:15:27.480 align:start position:0% power by multiple project coming from 00:15:27.480 --> 00:15:31.240 align:start position:0% power by multiple project coming from Bitcoin<00:15:27.840> core<00:15:28.050> so<00:15:28.560> ellipsoid<00:15:29.070> P<00:15:29.280> 256<00:15:29.910> K<00:15:30.480> 1<00:15:30.630> and 00:15:31.240 --> 00:15:31.250 align:start position:0% Bitcoin core so ellipsoid P 256 K 1 and 00:15:31.250 --> 00:15:34.820 align:start position:0% Bitcoin core so ellipsoid P 256 K 1 and we<00:15:32.250> will<00:15:32.400> test<00:15:32.640> it<00:15:32.820> against<00:15:33.360> state-of-the-art 00:15:34.820 --> 00:15:34.830 align:start position:0% we will test it against state-of-the-art 00:15:34.830 --> 00:15:38.320 align:start position:0% we will test it against state-of-the-art side<00:15:35.130> channel<00:15:35.430> attacks<00:15:35.760> that<00:15:36.120> we<00:15:36.300> have<00:15:36.450> on<00:15:37.350> hgx 00:15:38.320 --> 00:15:38.330 align:start position:0% side channel attacks that we have on hgx 00:15:38.330 --> 00:15:40.960 align:start position:0% side channel attacks that we have on hgx we<00:15:39.330> will<00:15:39.450> publish<00:15:39.660> a<00:15:39.900> review<00:15:40.770> on<00:15:40.890> that 00:15:40.960 --> 00:15:40.970 align:start position:0% we will publish a review on that 00:15:40.970 --> 00:15:43.460 align:start position:0% we will publish a review on that detailed<00:15:41.970> report<00:15:42.360> if<00:15:42.630> there<00:15:42.840> are<00:15:42.960> patches<00:15:43.170> to 00:15:43.460 --> 00:15:43.470 align:start position:0% detailed report if there are patches to 00:15:43.470 --> 00:15:46.460 align:start position:0% detailed report if there are patches to be<00:15:43.590> written<00:15:43.950> we<00:15:44.160> will<00:15:44.340> do<00:15:45.000> that<00:15:45.150> as<00:15:45.330> well<00:15:45.480> if<00:15:46.140> we 00:15:46.460 --> 00:15:46.470 align:start position:0% be written we will do that as well if we 00:15:46.470 --> 00:15:49.310 align:start position:0% be written we will do that as well if we have<00:15:46.620> some<00:15:47.010> well<00:15:47.610> parts<00:15:48.300> to<00:15:48.450> rewrite<00:15:48.780> we<00:15:49.170> will 00:15:49.310 --> 00:15:49.320 align:start position:0% have some well parts to rewrite we will 00:15:49.320 --> 00:15:52.070 align:start position:0% have some well parts to rewrite we will also<00:15:49.590> do<00:15:49.770> that<00:15:49.800> and<00:15:50.250> in<00:15:51.030> the<00:15:51.270> end<00:15:51.450> we<00:15:51.660> want<00:15:51.840> to 00:15:52.070 --> 00:15:52.080 align:start position:0% also do that and in the end we want to 00:15:52.080 --> 00:15:57.050 align:start position:0% also do that and in the end we want to know<00:15:52.260> if<00:15:52.920> and<00:15:53.600> when<00:15:54.600> how<00:15:55.380> long<00:15:55.590> we<00:15:56.580> can<00:15:56.730> store 00:15:57.050 --> 00:15:57.060 align:start position:0% know if and when how long we can store 00:15:57.060 --> 00:16:00.950 align:start position:0% know if and when how long we can store keys<00:15:57.300> on<00:15:57.570> HDX<00:15:58.170> and<00:15:58.670> I<00:15:59.670> think<00:16:00.180> that<00:16:00.360> using<00:16:00.690> this 00:16:00.950 --> 00:16:00.960 align:start position:0% keys on HDX and I think that using this 00:16:00.960 --> 00:16:04.160 align:start position:0% keys on HDX and I think that using this research<00:16:01.410> we<00:16:02.190> will<00:16:02.340> be<00:16:02.490> able<00:16:02.580> to<00:16:02.870> finally<00:16:03.870> have 00:16:04.160 --> 00:16:04.170 align:start position:0% research we will be able to finally have 00:16:04.170 --> 00:16:06.860 align:start position:0% research we will be able to finally have a<00:16:04.470> workable<00:16:04.950> and<00:16:05.160> workable<00:16:06.030> hardware<00:16:06.600> wallet 00:16:06.860 --> 00:16:06.870 align:start position:0% a workable and workable hardware wallet 00:16:06.870 --> 00:16:09.530 align:start position:0% a workable and workable hardware wallet on<00:16:07.050> an<00:16:07.170> enclave<00:16:07.530> and<00:16:07.800> with<00:16:08.700> strong<00:16:08.970> guarantees 00:16:09.530 --> 00:16:09.540 align:start position:0% on an enclave and with strong guarantees 00:16:09.540 --> 00:16:12.080 align:start position:0% on an enclave and with strong guarantees that<00:16:09.810> the<00:16:10.140> keys<00:16:10.350> are<00:16:10.380> going<00:16:10.740> to<00:16:10.920> be<00:16:11.090> available 00:16:12.080 --> 00:16:12.090 align:start position:0% that the keys are going to be available 00:16:12.090 --> 00:16:13.790 align:start position:0% that the keys are going to be available and<00:16:12.540> that<00:16:12.720> the<00:16:12.840> keys<00:16:13.050> are<00:16:13.230> not<00:16:13.320> going<00:16:13.560> to<00:16:13.680> be 00:16:13.790 --> 00:16:13.800 align:start position:0% and that the keys are not going to be 00:16:13.800 --> 00:16:16.400 align:start position:0% and that the keys are not going to be stolen<00:16:14.160> for<00:16:14.430> a<00:16:14.460> given<00:16:14.730> amount<00:16:14.910> of<00:16:15.090> time<00:16:15.330> so<00:16:16.170> for 00:16:16.400 --> 00:16:16.410 align:start position:0% stolen for a given amount of time so for 00:16:16.410 --> 00:16:18.410 align:start position:0% stolen for a given amount of time so for this<00:16:16.560> we<00:16:16.800> chose<00:16:17.070> not<00:16:17.100> to<00:16:17.460> use<00:16:17.610> the<00:16:18.000> Intel 00:16:18.410 --> 00:16:18.420 align:start position:0% this we chose not to use the Intel 00:16:18.420 --> 00:16:21.560 align:start position:0% this we chose not to use the Intel proprietary<00:16:19.260> the<00:16:19.770> graphic<00:16:20.040> library<00:16:20.570> because 00:16:21.560 --> 00:16:21.570 align:start position:0% proprietary the graphic library because 00:16:21.570 --> 00:16:24.020 align:start position:0% proprietary the graphic library because we<00:16:21.780> figure<00:16:22.080> that<00:16:22.260> working<00:16:23.040> on<00:16:23.310> an<00:16:23.640> open<00:16:23.760> source 00:16:24.020 --> 00:16:24.030 align:start position:0% we figure that working on an open source 00:16:24.030 --> 00:16:26.390 align:start position:0% we figure that working on an open source code<00:16:24.270> and<00:16:24.570> providing<00:16:25.230> some<00:16:25.530> providing<00:16:26.220> some 00:16:26.390 --> 00:16:26.400 align:start position:0% code and providing some providing some 00:16:26.400 --> 00:16:28.640 align:start position:0% code and providing some providing some review<00:16:26.730> of<00:16:26.760> that<00:16:26.880> will<00:16:27.810> benefit<00:16:28.200> more<00:16:28.440> to<00:16:28.590> the 00:16:28.640 --> 00:16:28.650 align:start position:0% review of that will benefit more to the 00:16:28.650 --> 00:16:31.460 align:start position:0% review of that will benefit more to the community<00:16:29.160> by<00:16:29.400> knowing<00:16:29.760> how<00:16:30.000> we<00:16:30.150> can<00:16:30.440> how<00:16:31.440> we 00:16:31.460 --> 00:16:31.470 align:start position:0% community by knowing how we can how we 00:16:31.470 --> 00:16:34.490 align:start position:0% community by knowing how we can how we can<00:16:31.590> work<00:16:32.040> and<00:16:32.600> design<00:16:33.600> new<00:16:33.840> side-channel 00:16:34.490 --> 00:16:34.500 align:start position:0% can work and design new side-channel 00:16:34.500 --> 00:16:36.620 align:start position:0% can work and design new side-channel protection<00:16:35.100> attacks<00:16:35.430> which<00:16:36.030> could<00:16:36.270> later<00:16:36.480> be 00:16:36.620 --> 00:16:36.630 align:start position:0% protection attacks which could later be 00:16:36.630 --> 00:16:44.290 align:start position:0% protection attacks which could later be applied<00:16:37.080> to<00:16:37.260> other<00:16:37.380> curves<00:16:41.750> so<00:16:42.750> to<00:16:43.140> finish 00:16:44.290 --> 00:16:44.300 align:start position:0% applied to other curves so to finish 00:16:44.300 --> 00:16:47.630 align:start position:0% applied to other curves so to finish summary<00:16:45.300> of<00:16:45.570> what<00:16:45.870> is<00:16:46.020> coming<00:16:46.200> next<00:16:46.530> in<00:16:46.800> 2019 00:16:47.630 --> 00:16:47.640 align:start position:0% summary of what is coming next in 2019 00:16:47.640 --> 00:16:50.930 align:start position:0% summary of what is coming next in 2019 for<00:16:47.940> Enclave<00:16:48.740> first<00:16:49.740> we<00:16:50.190> want<00:16:50.400> to<00:16:50.460> start<00:16:50.610> with 00:16:50.930 --> 00:16:50.940 align:start position:0% for Enclave first we want to start with 00:16:50.940 --> 00:16:54.500 align:start position:0% for Enclave first we want to start with the<00:16:51.060> CTF<00:16:51.480> so<00:16:51.900> after<00:16:52.380> with<00:16:52.800> you<00:16:53.010> we<00:16:53.670> will<00:16:53.850> test 00:16:54.500 --> 00:16:54.510 align:start position:0% the CTF so after with you we will test 00:16:54.510 --> 00:16:56.990 align:start position:0% the CTF so after with you we will test so<00:16:55.020> we<00:16:55.200> will<00:16:55.350> publish<00:16:55.590> what<00:16:56.370> we<00:16:56.550> did<00:16:56.700> with<00:16:56.880> our 00:16:56.990 --> 00:16:57.000 align:start position:0% so we will publish what we did with our 00:16:57.000 --> 00:17:01.700 align:start position:0% so we will publish what we did with our hardened<00:16:57.630> API<00:16:58.200> and<00:16:59.030> well<00:17:00.030> standard<00:17:00.870> CTF<00:17:01.350> so<00:17:01.590> if 00:17:01.700 --> 00:17:01.710 align:start position:0% hardened API and well standard CTF so if 00:17:01.710 --> 00:17:04.490 align:start position:0% hardened API and well standard CTF so if you<00:17:01.890> win<00:17:02.070> you<00:17:02.520> get<00:17:02.670> better<00:17:02.880> because<00:17:03.690> well 00:17:04.490 --> 00:17:04.500 align:start position:0% you win you get better because well 00:17:04.500 --> 00:17:08.060 align:start position:0% you win you get better because well we'll<00:17:04.709> put<00:17:04.980> some<00:17:05.220> ads<00:17:05.550> in<00:17:06.480> our<00:17:06.660> Enclave<00:17:07.170> so<00:17:07.830> we 00:17:08.060 --> 00:17:08.070 align:start position:0% we'll put some ads in our Enclave so we 00:17:08.070 --> 00:17:09.829 align:start position:0% we'll put some ads in our Enclave so we will<00:17:08.220> usually<00:17:08.459> increase<00:17:09.150> the<00:17:09.330> amount<00:17:09.630> and 00:17:09.829 --> 00:17:09.839 align:start position:0% will usually increase the amount and 00:17:09.839 --> 00:17:12.650 align:start position:0% will usually increase the amount and we'll<00:17:10.560> see<00:17:10.830> if<00:17:10.980> people<00:17:11.190> are<00:17:11.459> interested<00:17:11.699> in<00:17:12.180> if 00:17:12.650 --> 00:17:12.660 align:start position:0% we'll see if people are interested in if 00:17:12.660 --> 00:17:15.050 align:start position:0% we'll see if people are interested in if people<00:17:13.050> manage<00:17:13.380> to<00:17:13.560> extract<00:17:13.680> something<00:17:14.130> as<00:17:14.580> I 00:17:15.050 --> 00:17:15.060 align:start position:0% people manage to extract something as I 00:17:15.060 --> 00:17:17.870 align:start position:0% people manage to extract something as I talked<00:17:15.390> for<00:17:15.949> cryptographic<00:17:16.949> API<00:17:17.520> on<00:17:17.760> our 00:17:17.870 --> 00:17:17.880 align:start position:0% talked for cryptographic API on our 00:17:17.880 --> 00:17:21.650 align:start position:0% talked for cryptographic API on our Hardware<00:17:18.300> wallet<00:17:18.570> so<00:17:19.410> that<00:17:19.440> works<00:17:19.920> on<00:17:20.360> well<00:17:21.360> - 00:17:21.650 --> 00:17:21.660 align:start position:0% Hardware wallet so that works on well - 00:17:21.660 --> 00:17:24.199 align:start position:0% Hardware wallet so that works on well - bitcoins<00:17:22.080> I<00:17:22.320> think<00:17:22.709> on<00:17:23.100> one<00:17:23.370> Bitcoin<00:17:23.610> nobody 00:17:24.199 --> 00:17:24.209 align:start position:0% bitcoins I think on one Bitcoin nobody 00:17:24.209 --> 00:17:24.800 align:start position:0% bitcoins I think on one Bitcoin nobody steal<00:17:24.510> it 00:17:24.800 --> 00:17:24.810 align:start position:0% steal it 00:17:24.810 --> 00:17:26.930 align:start position:0% steal it nobody<00:17:25.290> stole<00:17:25.530> it<00:17:25.680> on<00:17:25.860> to<00:17:26.040> bitcoins<00:17:26.430> we<00:17:26.670> found 00:17:26.930 --> 00:17:26.940 align:start position:0% nobody stole it on to bitcoins we found 00:17:26.940 --> 00:17:29.240 align:start position:0% nobody stole it on to bitcoins we found some<00:17:27.600> motivated<00:17:28.140> parties<00:17:28.500> so<00:17:28.770> maybe<00:17:29.010> we<00:17:29.190> will 00:17:29.240 --> 00:17:29.250 align:start position:0% some motivated parties so maybe we will 00:17:29.250 --> 00:17:31.910 align:start position:0% some motivated parties so maybe we will see<00:17:29.460> the<00:17:29.550> same<00:17:29.730> here<00:17:30.320> after<00:17:31.320> we<00:17:31.470> do<00:17:31.590> that<00:17:31.770> and 00:17:31.910 --> 00:17:31.920 align:start position:0% see the same here after we do that and 00:17:31.920 --> 00:17:33.580 align:start position:0% see the same here after we do that and we're<00:17:32.100> convinced<00:17:32.550> that<00:17:32.700> our<00:17:32.880> security<00:17:33.180> is 00:17:33.580 --> 00:17:33.590 align:start position:0% we're convinced that our security is 00:17:33.590 --> 00:17:36.950 align:start position:0% we're convinced that our security is fine<00:17:34.590> then<00:17:35.130> we<00:17:35.490> can<00:17:35.760> we<00:17:36.390> will<00:17:36.540> be<00:17:36.660> able<00:17:36.840> to 00:17:36.950 --> 00:17:36.960 align:start position:0% fine then we can we will be able to 00:17:36.960 --> 00:17:38.990 align:start position:0% fine then we can we will be able to release<00:17:37.230> the<00:17:37.380> wallet<00:17:37.650> so<00:17:37.920> we<00:17:38.490> will<00:17:38.700> really<00:17:38.880> the 00:17:38.990 --> 00:17:39.000 align:start position:0% release the wallet so we will really the 00:17:39.000 --> 00:17:40.880 align:start position:0% release the wallet so we will really the simple<00:17:39.450> wallet<00:17:39.750> that<00:17:39.900> will<00:17:40.110> work<00:17:40.290> first<00:17:40.680> for 00:17:40.880 --> 00:17:40.890 align:start position:0% simple wallet that will work first for 00:17:40.890 --> 00:17:43.280 align:start position:0% simple wallet that will work first for Bitcoin<00:17:41.250> in<00:17:41.400> atrium<00:17:41.820> and<00:17:42.090> then<00:17:42.810> we<00:17:42.960> can<00:17:43.110> move 00:17:43.280 --> 00:17:43.290 align:start position:0% Bitcoin in atrium and then we can move 00:17:43.290 --> 00:17:46.760 align:start position:0% Bitcoin in atrium and then we can move forward<00:17:43.640> and<00:17:44.640> release<00:17:45.120> an<00:17:45.240> SDK<00:17:45.720> that<00:17:46.320> will<00:17:46.560> let 00:17:46.760 --> 00:17:46.770 align:start position:0% forward and release an SDK that will let 00:17:46.770 --> 00:17:48.590 align:start position:0% forward and release an SDK that will let people<00:17:47.190> write<00:17:47.460> their<00:17:47.520> own<00:17:47.880> application 00:17:48.590 --> 00:17:48.600 align:start position:0% people write their own application 00:17:48.600 --> 00:17:50.810 align:start position:0% people write their own application and<00:17:48.750> use<00:17:49.259> PTD<00:17:49.799> to<00:17:50.309> secure<00:17:50.610> their<00:17:50.789> own 00:17:50.810 --> 00:17:50.820 align:start position:0% and use PTD to secure their own 00:17:50.820 --> 00:17:56.749 align:start position:0% and use PTD to secure their own applications<00:17:51.590> so<00:17:53.509> that's<00:17:54.509> it<00:17:54.750> and<00:17:55.460> we<00:17:56.460> still 00:17:56.749 --> 00:17:56.759 align:start position:0% applications so that's it and we still 00:17:56.759 --> 00:17:59.180 align:start position:0% applications so that's it and we still have<00:17:56.880> some<00:17:57.210> minutes<00:17:57.539> for<00:17:57.720> questions<00:17:58.139> if<00:17:58.889> you 00:17:59.180 --> 00:17:59.190 align:start position:0% have some minutes for questions if you 00:17:59.190 --> 00:18:07.340 align:start position:0% have some minutes for questions if you want 00:18:07.340 --> 00:18:07.350 align:start position:0% 00:18:07.350 --> 00:18:09.410 align:start position:0% you