WEBVTT Kind: captions Language: en 00:00:04.490 --> 00:00:07.460 align:start position:0% yeah<00:00:05.490> hello<00:00:05.790> everyone<00:00:06.450> very<00:00:06.870> excited<00:00:07.260> to<00:00:07.350> be 00:00:07.460 --> 00:00:07.470 align:start position:0% yeah hello everyone very excited to be 00:00:07.470 --> 00:00:09.930 align:start position:0% yeah hello everyone very excited to be here<00:00:07.710> I<00:00:07.920> will<00:00:08.670> be<00:00:08.790> talking<00:00:09.120> to 00:00:09.930 --> 00:00:09.940 align:start position:0% here I will be talking to 00:00:09.940 --> 00:00:11.759 align:start position:0% here I will be talking to the<00:00:10.030> future<00:00:10.360> of<00:00:10.389> open<00:00:10.690> hardware<00:00:10.959> verifiable 00:00:11.759 --> 00:00:11.769 align:start position:0% the future of open hardware verifiable 00:00:11.769 --> 00:00:14.339 align:start position:0% the future of open hardware verifiable decentralized<00:00:12.490> world<00:00:12.730> and<00:00:13.110> to<00:00:14.110> give<00:00:14.230> an 00:00:14.339 --> 00:00:14.349 align:start position:0% decentralized world and to give an 00:00:14.349 --> 00:00:15.839 align:start position:0% decentralized world and to give an overview<00:00:14.619> of<00:00:14.799> what<00:00:14.980> I<00:00:15.009> will<00:00:15.279> be<00:00:15.400> covering<00:00:15.429> in 00:00:15.839 --> 00:00:15.849 align:start position:0% overview of what I will be covering in 00:00:15.849 --> 00:00:17.519 align:start position:0% overview of what I will be covering in this<00:00:15.940> talk<00:00:16.209> I<00:00:16.240> will<00:00:16.449> first<00:00:17.050> of<00:00:17.230> all<00:00:17.349> give<00:00:17.500> a 00:00:17.519 --> 00:00:17.529 align:start position:0% this talk I will first of all give a 00:00:17.529 --> 00:00:23.279 align:start position:0% this talk I will first of all give a brief<00:00:17.800> introduction<00:00:21.810> I<00:00:22.810> am<00:00:22.840> representing 00:00:23.279 --> 00:00:23.289 align:start position:0% brief introduction I am representing 00:00:23.289 --> 00:00:24.720 align:start position:0% brief introduction I am representing about<00:00:23.650> the<00:00:23.739> Australia<00:00:24.160> open<00:00:24.400> source<00:00:24.579> hardware 00:00:24.720 --> 00:00:24.730 align:start position:0% about the Australia open source hardware 00:00:24.730 --> 00:00:26.909 align:start position:0% about the Australia open source hardware Association<00:00:25.419> and<00:00:25.630> about<00:00:26.380> the<00:00:26.469> open<00:00:26.710> hardware 00:00:26.909 --> 00:00:26.919 align:start position:0% Association and about the open hardware 00:00:26.919 --> 00:00:29.490 align:start position:0% Association and about the open hardware month<00:00:27.189> which<00:00:27.399> is<00:00:27.550> happening<00:00:28.029> this<00:00:28.119> month<00:00:28.500> the 00:00:29.490 --> 00:00:29.500 align:start position:0% month which is happening this month the 00:00:29.500 --> 00:00:31.200 align:start position:0% month which is happening this month the main<00:00:29.649> part<00:00:29.890> of<00:00:29.980> my<00:00:30.099> talk<00:00:30.309> will<00:00:30.550> be<00:00:30.579> dealing 00:00:31.200 --> 00:00:31.210 align:start position:0% main part of my talk will be dealing 00:00:31.210 --> 00:00:33.780 align:start position:0% main part of my talk will be dealing with<00:00:31.390> what<00:00:31.930> open<00:00:32.379> source<00:00:32.410> hardware<00:00:33.100> is<00:00:33.520> what 00:00:33.780 --> 00:00:33.790 align:start position:0% with what open source hardware is what 00:00:33.790 --> 00:00:35.850 align:start position:0% with what open source hardware is what can<00:00:33.940> we<00:00:34.059> understand<00:00:34.690> about<00:00:34.960> open<00:00:35.680> source 00:00:35.850 --> 00:00:35.860 align:start position:0% can we understand about open source 00:00:35.860 --> 00:00:38.040 align:start position:0% can we understand about open source hardware<00:00:36.010> what<00:00:36.670> is<00:00:36.789> verifiable<00:00:37.270> hardware<00:00:37.840> I 00:00:38.040 --> 00:00:38.050 align:start position:0% hardware what is verifiable hardware I 00:00:38.050 --> 00:00:39.660 align:start position:0% hardware what is verifiable hardware I would<00:00:38.200> give<00:00:38.320> a<00:00:38.350> few<00:00:38.530> examples<00:00:38.559> to<00:00:39.219> make<00:00:39.430> it 00:00:39.660 --> 00:00:39.670 align:start position:0% would give a few examples to make it 00:00:39.670 --> 00:00:42.029 align:start position:0% would give a few examples to make it tangible<00:00:39.820> I<00:00:40.660> will<00:00:41.110> talk<00:00:41.289> very<00:00:41.620> briefly<00:00:41.739> about 00:00:42.029 --> 00:00:42.039 align:start position:0% tangible I will talk very briefly about 00:00:42.039 --> 00:00:44.220 align:start position:0% tangible I will talk very briefly about how<00:00:42.820> the<00:00:42.879> security<00:00:43.420> modules<00:00:43.780> and<00:00:43.929> trusted 00:00:44.220 --> 00:00:44.230 align:start position:0% how the security modules and trusted 00:00:44.230 --> 00:00:47.970 align:start position:0% how the security modules and trusted execution<00:00:44.710> environments<00:00:45.249> and<00:00:46.079> solutions<00:00:47.079> for 00:00:47.970 --> 00:00:47.980 align:start position:0% execution environments and solutions for 00:00:47.980 --> 00:00:49.529 align:start position:0% execution environments and solutions for the<00:00:48.069> future<00:00:48.100> that<00:00:48.819> are<00:00:48.940> based<00:00:49.120> on<00:00:49.269> open 00:00:49.529 --> 00:00:49.539 align:start position:0% the future that are based on open 00:00:49.539 --> 00:00:52.829 align:start position:0% the future that are based on open silicon<00:00:50.429> so<00:00:51.429> to<00:00:51.879> give<00:00:51.999> a<00:00:52.030> bit<00:00:52.149> of<00:00:52.179> context<00:00:52.749> my 00:00:52.829 --> 00:00:52.839 align:start position:0% silicon so to give a bit of context my 00:00:52.839 --> 00:00:54.630 align:start position:0% silicon so to give a bit of context my name<00:00:52.989> is<00:00:53.109> matthias<00:00:53.440> Tanzimat<00:00:53.980> i'm<00:00:54.190> the 00:00:54.630 --> 00:00:54.640 align:start position:0% name is matthias Tanzimat i'm the 00:00:54.640 --> 00:00:57.059 align:start position:0% name is matthias Tanzimat i'm the director<00:00:54.879> of<00:00:55.089> the<00:00:55.210> rad<00:00:55.390> institute<00:00:55.929> i'm<00:00:56.530> also<00:00:56.859> a 00:00:57.059 --> 00:00:57.069 align:start position:0% director of the rad institute i'm also a 00:00:57.069 --> 00:00:58.649 align:start position:0% director of the rad institute i'm also a board<00:00:57.399> member<00:00:57.519> of<00:00:57.789> the<00:00:57.940> author<00:00:58.089> of<00:00:58.300> the<00:00:58.420> open 00:00:58.649 --> 00:00:58.659 align:start position:0% board member of the author of the open 00:00:58.659 --> 00:01:00.569 align:start position:0% board member of the author of the open source<00:00:58.780> Heart<00:00:59.019> Association<00:00:59.289> and<00:01:00.069> please<00:01:00.429> get 00:01:00.569 --> 00:01:00.579 align:start position:0% source Heart Association and please get 00:01:00.579 --> 00:01:02.579 align:start position:0% source Heart Association and please get in<00:01:00.699> contact<00:01:00.729> with<00:01:01.089> me<00:01:01.329> in<00:01:01.899> case<00:01:02.109> I'm<00:01:02.289> talking 00:01:02.579 --> 00:01:02.589 align:start position:0% in contact with me in case I'm talking 00:01:02.589 --> 00:01:04.290 align:start position:0% in contact with me in case I'm talking too<00:01:02.710> fast<00:01:02.739> or<00:01:03.190> the<00:01:03.339> slides<00:01:03.550> are<00:01:03.729> confusing<00:01:04.120> or 00:01:04.290 --> 00:01:04.300 align:start position:0% too fast or the slides are confusing or 00:01:04.300 --> 00:01:08.010 align:start position:0% too fast or the slides are confusing or something<00:01:05.610> basically<00:01:06.610> I<00:01:06.820> want<00:01:07.420> to<00:01:07.479> also<00:01:07.630> refer 00:01:08.010 --> 00:01:08.020 align:start position:0% something basically I want to also refer 00:01:08.020 --> 00:01:10.530 align:start position:0% something basically I want to also refer to<00:01:08.049> a<00:01:08.280> talk<00:01:09.280> I've<00:01:09.460> been<00:01:09.670> giving<00:01:09.940> this<00:01:10.330> week 00:01:10.530 --> 00:01:10.540 align:start position:0% to a talk I've been giving this week 00:01:10.540 --> 00:01:11.820 align:start position:0% to a talk I've been giving this week which<00:01:10.720> was<00:01:10.810> called<00:01:11.080> the<00:01:11.140> past<00:01:11.409> present<00:01:11.740> the 00:01:11.820 --> 00:01:11.830 align:start position:0% which was called the past present the 00:01:11.830 --> 00:01:13.649 align:start position:0% which was called the past present the future<00:01:12.159> of<00:01:12.250> opt-out<00:01:12.670> with<00:01:12.940> open<00:01:13.270> and<00:01:13.360> Libre 00:01:13.649 --> 00:01:13.659 align:start position:0% future of opt-out with open and Libre 00:01:13.659 --> 00:01:16.320 align:start position:0% future of opt-out with open and Libre Hardware<00:01:13.990> at<00:01:14.620> HTTP<00:01:15.310> 19<00:01:15.670> the<00:01:15.760> hackers<00:01:16.000> Congress 00:01:16.320 --> 00:01:16.330 align:start position:0% Hardware at HTTP 19 the hackers Congress 00:01:16.330 --> 00:01:17.730 align:start position:0% Hardware at HTTP 19 the hackers Congress panel<00:01:16.570> any<00:01:16.720> Poly's<00:01:17.050> which<00:01:17.200> is<00:01:17.320> dealing<00:01:17.590> also 00:01:17.730 --> 00:01:17.740 align:start position:0% panel any Poly's which is dealing also 00:01:17.740 --> 00:01:20.520 align:start position:0% panel any Poly's which is dealing also with<00:01:17.920> open<00:01:18.490> hardware<00:01:18.730> so<00:01:19.510> it's<00:01:20.080> a<00:01:20.170> little<00:01:20.440> bit 00:01:20.520 --> 00:01:20.530 align:start position:0% with open hardware so it's a little bit 00:01:20.530 --> 00:01:22.200 align:start position:0% with open hardware so it's a little bit was<00:01:20.710> a<00:01:20.740> bit<00:01:20.920> of<00:01:21.010> a<00:01:21.070> longer<00:01:21.370> talk<00:01:21.610> about<00:01:21.640> one<00:01:22.090> or 00:01:22.200 --> 00:01:22.210 align:start position:0% was a bit of a longer talk about one or 00:01:22.210 --> 00:01:24.180 align:start position:0% was a bit of a longer talk about one or so<00:01:22.510> this<00:01:22.660> might<00:01:22.810> be<00:01:22.890> more<00:01:23.890> of<00:01:24.040> a 00:01:24.180 --> 00:01:24.190 align:start position:0% so this might be more of a 00:01:24.190 --> 00:01:25.860 align:start position:0% so this might be more of a contextualization<00:01:25.000> if<00:01:25.240> your<00:01:25.360> interest<00:01:25.660> this 00:01:25.860 --> 00:01:25.870 align:start position:0% contextualization if your interest this 00:01:25.870 --> 00:01:27.990 align:start position:0% contextualization if your interest this should<00:01:26.020> be<00:01:26.110> like<00:01:26.260> online<00:01:26.470> already<00:01:26.800> I<00:01:26.950> guess<00:01:27.160> so 00:01:27.990 --> 00:01:28.000 align:start position:0% should be like online already I guess so 00:01:28.000 --> 00:01:30.090 align:start position:0% should be like online already I guess so um<00:01:28.300> but<00:01:28.810> brief<00:01:28.990> dangerous<00:01:29.440> riot<00:01:29.710> we're<00:01:30.010> an 00:01:30.090 --> 00:01:30.100 align:start position:0% um but brief dangerous riot we're an 00:01:30.100 --> 00:01:32.220 align:start position:0% um but brief dangerous riot we're an independent<00:01:30.280> Institute<00:01:31.060> we're<00:01:31.540> working<00:01:31.900> with 00:01:32.220 --> 00:01:32.230 align:start position:0% independent Institute we're working with 00:01:32.230 --> 00:01:34.560 align:start position:0% independent Institute we're working with crypto<00:01:33.160> economics<00:01:33.610> future<00:01:33.910> crypt<00:01:34.120> economics 00:01:34.560 --> 00:01:34.570 align:start position:0% crypto economics future crypt economics 00:01:34.570 --> 00:01:36.570 align:start position:0% crypto economics future crypt economics to<00:01:34.690> me<00:01:34.810> to<00:01:35.110> be<00:01:35.230> more<00:01:35.380> precise<00:01:35.740> we're<00:01:36.340> working 00:01:36.570 --> 00:01:36.580 align:start position:0% to me to be more precise we're working 00:01:36.580 --> 00:01:37.950 align:start position:0% to me to be more precise we're working with<00:01:36.670> privacy<00:01:37.030> technologies<00:01:37.600> and<00:01:37.750> open 00:01:37.950 --> 00:01:37.960 align:start position:0% with privacy technologies and open 00:01:37.960 --> 00:01:40.140 align:start position:0% with privacy technologies and open hardware<00:01:38.260> and<00:01:38.800> we're<00:01:38.920> doing<00:01:38.980> this<00:01:39.160> since<00:01:39.760> 2009 00:01:40.140 --> 00:01:40.150 align:start position:0% hardware and we're doing this since 2009 00:01:40.150 --> 00:01:42.870 align:start position:0% hardware and we're doing this since 2009 and<00:01:40.600> formally<00:01:41.590> as<00:01:41.800> this<00:01:42.010> organization's<00:01:42.760> is 00:01:42.870 --> 00:01:42.880 align:start position:0% and formally as this organization's is 00:01:42.880 --> 00:01:46.110 align:start position:0% and formally as this organization's is 2012<00:01:43.600> and<00:01:43.930> we<00:01:44.380> have<00:01:44.500> a<00:01:44.670> background<00:01:45.670> also 00:01:46.110 --> 00:01:46.120 align:start position:0% 2012 and we have a background also 00:01:46.120 --> 00:01:47.190 align:start position:0% 2012 and we have a background also working<00:01:46.300> with<00:01:46.450> diverse 00:01:47.190 --> 00:01:47.200 align:start position:0% working with diverse 00:01:47.200 --> 00:01:49.290 align:start position:0% working with diverse open<00:01:47.590> hardware<00:01:47.950> projects<00:01:48.400> this<00:01:48.520> is<00:01:48.580> maybe<00:01:49.000> a 00:01:49.290 --> 00:01:49.300 align:start position:0% open hardware projects this is maybe a 00:01:49.300 --> 00:01:51.000 align:start position:0% open hardware projects this is maybe a more<00:01:49.750> well-known<00:01:50.170> project<00:01:50.680> this<00:01:50.770> is<00:01:50.890> the 00:01:51.000 --> 00:01:51.010 align:start position:0% more well-known project this is the 00:01:51.010 --> 00:01:51.480 align:start position:0% more well-known project this is the apparatus 00:01:51.480 --> 00:01:51.490 align:start position:0% apparatus 00:01:51.490 --> 00:01:53.090 align:start position:0% apparatus open<00:01:51.760> source<00:01:51.970> Cinema<00:01:52.330> Camera<00:01:52.480> which<00:01:52.900> is<00:01:53.020> a 00:01:53.090 --> 00:01:53.100 align:start position:0% open source Cinema Camera which is a 00:01:53.100 --> 00:01:55.950 align:start position:0% open source Cinema Camera which is a full<00:01:54.100> camera<00:01:54.610> based<00:01:54.940> around<00:01:55.390> open<00:01:55.720> hardware 00:01:55.950 --> 00:01:55.960 align:start position:0% full camera based around open hardware 00:01:55.960 --> 00:01:58.260 align:start position:0% full camera based around open hardware so<00:01:56.170> every<00:01:56.410> part<00:01:56.680> of<00:01:56.800> this<00:01:56.920> camera<00:01:57.250> except<00:01:57.550> that 00:01:58.260 --> 00:01:58.270 align:start position:0% so every part of this camera except that 00:01:58.270 --> 00:02:00.600 align:start position:0% so every part of this camera except that the<00:01:58.420> lens<00:01:58.600> of<00:01:58.780> course<00:01:59.050> are<00:01:59.470> open<00:01:59.860> hardware<00:02:00.280> so 00:02:00.600 --> 00:02:00.610 align:start position:0% the lens of course are open hardware so 00:02:00.610 --> 00:02:04.320 align:start position:0% the lens of course are open hardware so you<00:02:01.150> can<00:02:01.270> see<00:02:01.480> my<00:02:01.660> presentation<00:02:02.290> at<00:02:02.440> the<00:02:03.000> 32<00:02:04.000> C 00:02:04.320 --> 00:02:04.330 align:start position:0% you can see my presentation at the 32 C 00:02:04.330 --> 00:02:06.300 align:start position:0% you can see my presentation at the 32 C 3<00:02:04.570> which<00:02:05.200> I<00:02:05.320> have<00:02:05.410> been<00:02:05.530> given<00:02:05.770> at<00:02:05.860> cost 00:02:06.300 --> 00:02:06.310 align:start position:0% 3 which I have been given at cost 00:02:06.310 --> 00:02:08.550 align:start position:0% 3 which I have been given at cost Communication<00:02:06.880> Congress<00:02:07.440> which<00:02:08.440> is 00:02:08.550 --> 00:02:08.560 align:start position:0% Communication Congress which is 00:02:08.560 --> 00:02:09.990 align:start position:0% Communication Congress which is explaining<00:02:08.920> the<00:02:08.950> project<00:02:09.399> is<00:02:09.489> an<00:02:09.640> older 00:02:09.990 --> 00:02:10.000 align:start position:0% explaining the project is an older 00:02:10.000 --> 00:02:11.250 align:start position:0% explaining the project is an older project<00:02:10.179> but<00:02:10.479> this<00:02:10.599> project<00:02:10.780> is<00:02:10.959> still<00:02:11.110> going 00:02:11.250 --> 00:02:11.260 align:start position:0% project but this project is still going 00:02:11.260 --> 00:02:14.640 align:start position:0% project but this project is still going on<00:02:11.440> it's<00:02:12.040> also<00:02:12.670> interesting<00:02:13.030> to<00:02:13.209> see<00:02:13.510> how<00:02:13.750> kind 00:02:14.640 --> 00:02:14.650 align:start position:0% on it's also interesting to see how kind 00:02:14.650 --> 00:02:16.320 align:start position:0% on it's also interesting to see how kind of<00:02:14.680> long<00:02:14.920> lifespans<00:02:15.519> is<00:02:15.700> hoping<00:02:16.030> how<00:02:16.269> the 00:02:16.320 --> 00:02:16.330 align:start position:0% of long lifespans is hoping how the 00:02:16.330 --> 00:02:18.750 align:start position:0% of long lifespans is hoping how the projects<00:02:16.750> have<00:02:16.870> so<00:02:17.260> I<00:02:17.500> can<00:02:17.769> strongly<00:02:18.190> suggest 00:02:18.750 --> 00:02:18.760 align:start position:0% projects have so I can strongly suggest 00:02:18.760 --> 00:02:22.740 align:start position:0% projects have so I can strongly suggest if<00:02:19.270> you<00:02:19.390> want<00:02:19.569> to<00:02:19.800> see<00:02:20.800> a<00:02:21.210> quite<00:02:22.210> large<00:02:22.450> open 00:02:22.740 --> 00:02:22.750 align:start position:0% if you want to see a quite large open 00:02:22.750 --> 00:02:23.300 align:start position:0% if you want to see a quite large open other 00:02:23.300 --> 00:02:23.310 align:start position:0% other 00:02:23.310 --> 00:02:25.970 align:start position:0% other to<00:02:23.810> see<00:02:24.810> this<00:02:24.959> taco<00:02:25.260> gets<00:02:25.650> more<00:02:25.890> information 00:02:25.970 --> 00:02:25.980 align:start position:0% to see this taco gets more information 00:02:25.980 --> 00:02:29.210 align:start position:0% to see this taco gets more information that<00:02:26.459> appear<00:02:26.700> to<00:02:26.730> stud<00:02:27.060> org<00:02:27.330> website<00:02:28.220> you 00:02:29.210 --> 00:02:29.220 align:start position:0% that appear to stud org website you 00:02:29.220 --> 00:02:31.100 align:start position:0% that appear to stud org website you might<00:02:29.340> also<00:02:29.580> remember<00:02:29.670> this<00:02:30.150> thing<00:02:30.360> this<00:02:30.870> was 00:02:31.100 --> 00:02:31.110 align:start position:0% might also remember this thing this was 00:02:31.110 --> 00:02:32.480 align:start position:0% might also remember this thing this was actually<00:02:31.290> a<00:02:31.500> magazine<00:02:31.890> we<00:02:32.100> have<00:02:32.130> live<00:02:32.400> in 00:02:32.480 --> 00:02:32.490 align:start position:0% actually a magazine we have live in 00:02:32.490 --> 00:02:34.699 align:start position:0% actually a magazine we have live in after<00:02:32.670> the<00:02:32.790> last<00:02:33.000> Def<00:02:33.240> Con<00:02:33.510> so<00:02:33.780> it's<00:02:33.930> a<00:02:34.080> kind<00:02:34.650> of 00:02:34.699 --> 00:02:34.709 align:start position:0% after the last Def Con so it's a kind of 00:02:34.709 --> 00:02:36.410 align:start position:0% after the last Def Con so it's a kind of a<00:02:34.800> newspaper<00:02:35.040> it's<00:02:35.580> kind<00:02:36.120> of<00:02:36.150> a<00:02:36.240> book 00:02:36.410 --> 00:02:36.420 align:start position:0% a newspaper it's kind of a book 00:02:36.420 --> 00:02:38.960 align:start position:0% a newspaper it's kind of a book obfuscated<00:02:37.380> in<00:02:37.470> a<00:02:37.590> newspaper<00:02:37.830> and<00:02:38.370> we<00:02:38.880> have 00:02:38.960 --> 00:02:38.970 align:start position:0% obfuscated in a newspaper and we have 00:02:38.970 --> 00:02:40.940 align:start position:0% obfuscated in a newspaper and we have been<00:02:39.090> distributing<00:02:39.540> this<00:02:39.660> at<00:02:39.840> the<00:02:40.020> last<00:02:40.620> Def 00:02:40.940 --> 00:02:40.950 align:start position:0% been distributing this at the last Def 00:02:40.950 --> 00:02:44.479 align:start position:0% been distributing this at the last Def Con<00:02:41.220> and<00:02:41.430> um<00:02:42.239> this<00:02:42.770> month<00:02:43.770> we<00:02:43.950> have<00:02:44.069> two<00:02:44.190> open 00:02:44.479 --> 00:02:44.489 align:start position:0% Con and um this month we have two open 00:02:44.489 --> 00:02:45.770 align:start position:0% Con and um this month we have two open source<00:02:44.730> hardware<00:02:44.970> month<00:02:45.300> to<00:02:45.510> open<00:02:45.690> another 00:02:45.770 --> 00:02:45.780 align:start position:0% source hardware month to open another 00:02:45.780 --> 00:02:47.930 align:start position:0% source hardware month to open another month<00:02:46.110> from<00:02:47.010> the<00:02:47.130> Oshawa<00:02:47.520> and<00:02:47.730> in<00:02:47.850> this 00:02:47.930 --> 00:02:47.940 align:start position:0% month from the Oshawa and in this 00:02:47.940 --> 00:02:50.330 align:start position:0% month from the Oshawa and in this context<00:02:48.510> riots<00:02:49.260> and<00:02:49.500> we<00:02:49.739> will<00:02:49.920> be<00:02:50.010> giving<00:02:50.250> out 00:02:50.330 --> 00:02:50.340 align:start position:0% context riots and we will be giving out 00:02:50.340 --> 00:02:53.809 align:start position:0% context riots and we will be giving out this<00:02:50.790> kind<00:02:51.000> of<00:02:51.090> bags<00:02:51.360> with<00:02:52.069> also<00:02:53.069> the<00:02:53.280> future 00:02:53.809 --> 00:02:53.819 align:start position:0% this kind of bags with also the future 00:02:53.819 --> 00:02:55.220 align:start position:0% this kind of bags with also the future cryptic<00:02:54.120> Atomics<00:02:54.390> magazine<00:02:54.690> but<00:02:54.780> also<00:02:54.959> with 00:02:55.220 --> 00:02:55.230 align:start position:0% cryptic Atomics magazine but also with 00:02:55.230 --> 00:02:57.590 align:start position:0% cryptic Atomics magazine but also with open<00:02:56.100> ism<00:02:56.340> conversations<00:02:56.910> in<00:02:57.000> open<00:02:57.269> hardware 00:02:57.590 --> 00:02:57.600 align:start position:0% open ism conversations in open hardware 00:02:57.600 --> 00:02:59.540 align:start position:0% open ism conversations in open hardware which<00:02:57.750> is<00:02:57.900> a<00:02:57.930> book<00:02:58.739> and<00:02:58.950> a<00:02:58.980> conversation 00:02:59.540 --> 00:02:59.550 align:start position:0% which is a book and a conversation 00:02:59.550 --> 00:03:01.670 align:start position:0% which is a book and a conversation series<00:02:59.880> where<00:03:00.060> we<00:03:00.180> try<00:03:00.450> to<00:03:00.480> figure<00:03:01.140> out<00:03:01.260> and 00:03:01.670 --> 00:03:01.680 align:start position:0% series where we try to figure out and 00:03:01.680 --> 00:03:04.940 align:start position:0% series where we try to figure out and find<00:03:01.860> out<00:03:02.070> how<00:03:02.610> projects<00:03:03.570> are<00:03:03.800> which<00:03:04.800> cut 00:03:04.940 --> 00:03:04.950 align:start position:0% find out how projects are which cut 00:03:04.950 --> 00:03:06.020 align:start position:0% find out how projects are which cut different<00:03:05.250> open<00:03:05.459> source<00:03:05.670> strategies 00:03:06.020 --> 00:03:06.030 align:start position:0% different open source strategies 00:03:06.030 --> 00:03:07.940 align:start position:0% different open source strategies projects<00:03:06.450> have<00:03:06.660> and<00:03:06.930> why<00:03:07.350> are<00:03:07.590> the<00:03:07.680> open 00:03:07.940 --> 00:03:07.950 align:start position:0% projects have and why are the open 00:03:07.950 --> 00:03:11.270 align:start position:0% projects have and why are the open sourcing<00:03:08.600> really<00:03:09.600> hard<00:03:10.470> we're<00:03:10.709> hardly 00:03:11.270 --> 00:03:11.280 align:start position:0% sourcing really hard we're hardly 00:03:11.280 --> 00:03:13.160 align:start position:0% sourcing really hard we're hardly approaching<00:03:11.760> it<00:03:11.880> and<00:03:12.030> how<00:03:12.300> far<00:03:12.600> can<00:03:12.780> you<00:03:12.870> go<00:03:13.019> in 00:03:13.160 --> 00:03:13.170 align:start position:0% approaching it and how far can you go in 00:03:13.170 --> 00:03:15.410 align:start position:0% approaching it and how far can you go in doing<00:03:13.410> so<00:03:13.620> so<00:03:14.340> maybe<00:03:14.730> two<00:03:14.910> contexts<00:03:15.239> there's 00:03:15.410 --> 00:03:15.420 align:start position:0% doing so so maybe two contexts there's 00:03:15.420 --> 00:03:16.880 align:start position:0% doing so so maybe two contexts there's also<00:03:15.540> the<00:03:15.720> open<00:03:15.900> harder<00:03:16.170> month<00:03:16.410> what<00:03:16.739> will 00:03:16.880 --> 00:03:16.890 align:start position:0% also the open harder month what will 00:03:16.890 --> 00:03:18.620 align:start position:0% also the open harder month what will happen<00:03:17.160> in<00:03:17.340> this<00:03:17.489> month<00:03:17.730> it's<00:03:18.330> already 00:03:18.620 --> 00:03:18.630 align:start position:0% happen in this month it's already 00:03:18.630 --> 00:03:20.000 align:start position:0% happen in this month it's already running<00:03:18.870> the<00:03:18.959> month<00:03:19.140> and<00:03:19.410> there's<00:03:19.680> a<00:03:19.769> lot<00:03:19.890> of 00:03:20.000 --> 00:03:20.010 align:start position:0% running the month and there's a lot of 00:03:20.010 --> 00:03:21.890 align:start position:0% running the month and there's a lot of other<00:03:20.430> events<00:03:20.550> coming<00:03:20.819> coming<00:03:21.360> up<00:03:21.510> this<00:03:21.660> talk 00:03:21.890 --> 00:03:21.900 align:start position:0% other events coming coming up this talk 00:03:21.900 --> 00:03:23.240 align:start position:0% other events coming coming up this talk is<00:03:22.019> also<00:03:22.170> part<00:03:22.440> of<00:03:22.500> up<00:03:22.620> another<00:03:22.860> month<00:03:23.130> and 00:03:23.240 --> 00:03:23.250 align:start position:0% is also part of up another month and 00:03:23.250 --> 00:03:26.030 align:start position:0% is also part of up another month and this<00:03:23.819> worldwide<00:03:24.630> events<00:03:25.319> most<00:03:25.739> different 00:03:26.030 --> 00:03:26.040 align:start position:0% this worldwide events most different 00:03:26.040 --> 00:03:28.430 align:start position:0% this worldwide events most different hacker<00:03:26.190> spaces<00:03:26.550> from<00:03:26.970> industry<00:03:27.930> from<00:03:27.959> a<00:03:28.290> lot 00:03:28.430 --> 00:03:28.440 align:start position:0% hacker spaces from industry from a lot 00:03:28.440 --> 00:03:30.410 align:start position:0% hacker spaces from industry from a lot of<00:03:28.530> different<00:03:28.890> actors<00:03:29.310> there's<00:03:29.940> workshops 00:03:30.410 --> 00:03:30.420 align:start position:0% of different actors there's workshops 00:03:30.420 --> 00:03:31.850 align:start position:0% of different actors there's workshops there's<00:03:30.780> a<00:03:30.810> lot<00:03:30.930> of<00:03:31.019> our<00:03:31.110> formats<00:03:31.530> and<00:03:31.739> there's 00:03:31.850 --> 00:03:31.860 align:start position:0% there's a lot of our formats and there's 00:03:31.860 --> 00:03:33.800 align:start position:0% there's a lot of our formats and there's a<00:03:31.890> lot<00:03:32.010> of<00:03:32.070> communication<00:03:32.690> and<00:03:33.690> documentation 00:03:33.800 --> 00:03:33.810 align:start position:0% a lot of communication and documentation 00:03:33.810 --> 00:03:35.810 align:start position:0% a lot of communication and documentation going<00:03:34.560> on<00:03:34.709> so<00:03:34.950> there<00:03:35.070> will<00:03:35.160> be<00:03:35.220> a<00:03:35.370> lot<00:03:35.700> of 00:03:35.810 --> 00:03:35.820 align:start position:0% going on so there will be a lot of 00:03:35.820 --> 00:03:38.390 align:start position:0% going on so there will be a lot of projects<00:03:36.600> made<00:03:36.810> visible<00:03:37.140> online<00:03:37.920> on<00:03:38.160> the 00:03:38.390 --> 00:03:38.400 align:start position:0% projects made visible online on the 00:03:38.400 --> 00:03:40.900 align:start position:0% projects made visible online on the under<00:03:38.850> the<00:03:38.940> hashtag<00:03:39.060> Oh<00:03:39.450> hm<00:03:39.870> 2019<00:03:40.530> on<00:03:40.590> Twitter 00:03:40.900 --> 00:03:40.910 align:start position:0% under the hashtag Oh hm 2019 on Twitter 00:03:40.910 --> 00:03:43.670 align:start position:0% under the hashtag Oh hm 2019 on Twitter you<00:03:41.910> can<00:03:42.060> also<00:03:42.209> still<00:03:42.510> post<00:03:42.959> some<00:03:43.380> pop-up 00:03:43.670 --> 00:03:43.680 align:start position:0% you can also still post some pop-up 00:03:43.680 --> 00:03:45.979 align:start position:0% you can also still post some pop-up events<00:03:44.040> under<00:03:44.190> OAH<00:03:44.579> m<00:03:44.760> dot<00:03:44.940> or<00:03:45.120> dot<00:03:45.299> org<00:03:45.660> and 00:03:45.979 --> 00:03:45.989 align:start position:0% events under OAH m dot or dot org and 00:03:45.989 --> 00:03:48.319 align:start position:0% events under OAH m dot or dot org and maybe<00:03:46.590> to<00:03:46.739> briefly<00:03:46.950> explain<00:03:47.280> what<00:03:47.910> this<00:03:48.090> or 00:03:48.319 --> 00:03:48.329 align:start position:0% maybe to briefly explain what this or 00:03:48.329 --> 00:03:51.550 align:start position:0% maybe to briefly explain what this or schwa<00:03:48.540> is<00:03:48.720> it's<00:03:48.989> in<00:03:49.459> 501c3<00:03:50.459> so<00:03:50.910> it's<00:03:51.060> an<00:03:51.209> arm 00:03:51.550 --> 00:03:51.560 align:start position:0% schwa is it's in 501c3 so it's an arm 00:03:51.560 --> 00:03:52.729 align:start position:0% schwa is it's in 501c3 so it's an arm association 00:03:52.729 --> 00:03:52.739 align:start position:0% association 00:03:52.739 --> 00:03:55.009 align:start position:0% association it's<00:03:52.890> an<00:03:53.010> NGO<00:03:53.310> and<00:03:53.609> its<00:03:54.239> main<00:03:54.390> purpose<00:03:54.660> is<00:03:54.989> to 00:03:55.009 --> 00:03:55.019 align:start position:0% it's an NGO and its main purpose is to 00:03:55.019 --> 00:03:56.840 align:start position:0% it's an NGO and its main purpose is to organize<00:03:55.470> conference<00:03:55.920> the<00:03:56.070> community<00:03:56.489> events 00:03:56.840 --> 00:03:56.850 align:start position:0% organize conference the community events 00:03:56.850 --> 00:03:59.569 align:start position:0% organize conference the community events to<00:03:57.420> educate<00:03:57.930> the<00:03:58.380> general<00:03:58.500> public<00:03:58.709> about<00:03:59.130> open 00:03:59.569 --> 00:03:59.579 align:start position:0% to educate the general public about open 00:03:59.579 --> 00:04:02.870 align:start position:0% to educate the general public about open source<00:03:59.790> hardware<00:04:01.190> to<00:04:02.190> organize<00:04:02.519> to<00:04:02.670> open 00:04:02.870 --> 00:04:02.880 align:start position:0% source hardware to organize to open 00:04:02.880 --> 00:04:04.250 align:start position:0% source hardware to organize to open source<00:04:03.060> hardware<00:04:03.150> movement<00:04:03.480> around<00:04:03.959> shared 00:04:04.250 --> 00:04:04.260 align:start position:0% source hardware movement around shared 00:04:04.260 --> 00:04:06.680 align:start position:0% source hardware movement around shared values<00:04:04.560> and<00:04:04.590> principles<00:04:05.130> to<00:04:05.690> collect 00:04:06.680 --> 00:04:06.690 align:start position:0% values and principles to collect 00:04:06.690 --> 00:04:08.500 align:start position:0% values and principles to collect compiler<00:04:07.140> publish<00:04:07.500> data<00:04:07.650> on<00:04:07.890> the<00:04:07.980> open<00:04:08.280> source 00:04:08.500 --> 00:04:08.510 align:start position:0% compiler publish data on the open source 00:04:08.510 --> 00:04:11.000 align:start position:0% compiler publish data on the open source hardware<00:04:09.510> movement<00:04:09.930> to<00:04:10.290> provide<00:04:10.590> a<00:04:10.620> painless 00:04:11.000 --> 00:04:11.010 align:start position:0% hardware movement to provide a painless 00:04:11.010 --> 00:04:12.860 align:start position:0% hardware movement to provide a painless way<00:04:11.220> for<00:04:11.640> creators<00:04:11.910> to<00:04:12.060> indicate<00:04:12.540> that<00:04:12.600> their 00:04:12.860 --> 00:04:12.870 align:start position:0% way for creators to indicate that their 00:04:12.870 --> 00:04:14.300 align:start position:0% way for creators to indicate that their products<00:04:13.200> meet<00:04:13.350> a<00:04:13.380> standard<00:04:13.799> for<00:04:13.950> open<00:04:14.190> source 00:04:14.300 --> 00:04:14.310 align:start position:0% products meet a standard for open source 00:04:14.310 --> 00:04:16.210 align:start position:0% products meet a standard for open source compliance<00:04:14.940> and<00:04:15.180> what<00:04:15.540> that<00:04:15.690> standard<00:04:16.079> means 00:04:16.210 --> 00:04:16.220 align:start position:0% compliance and what that standard means 00:04:16.220 --> 00:04:18.729 align:start position:0% compliance and what that standard means or<00:04:17.220> what<00:04:17.519> the<00:04:17.579> context<00:04:18.090> means<00:04:18.299> it's<00:04:18.510> very 00:04:18.729 --> 00:04:18.739 align:start position:0% or what the context means it's very 00:04:18.739 --> 00:04:21.289 align:start position:0% or what the context means it's very visible<00:04:19.739> on<00:04:20.190> this<00:04:20.340> website<00:04:20.760> I<00:04:20.789> can<00:04:20.970> strongly 00:04:21.289 --> 00:04:21.299 align:start position:0% visible on this website I can strongly 00:04:21.299 --> 00:04:22.640 align:start position:0% visible on this website I can strongly recommend<00:04:21.690> to<00:04:21.720> take<00:04:21.930> a<00:04:21.989> look<00:04:22.200> at<00:04:22.320> so<00:04:22.410> you<00:04:22.500> also 00:04:22.640 --> 00:04:22.650 align:start position:0% recommend to take a look at so you also 00:04:22.650 --> 00:04:24.260 align:start position:0% recommend to take a look at so you also get<00:04:22.770> an<00:04:22.890> idea<00:04:23.160> what<00:04:23.340> kind<00:04:23.550> of<00:04:23.729> products<00:04:24.150> are 00:04:24.260 --> 00:04:24.270 align:start position:0% get an idea what kind of products are 00:04:24.270 --> 00:04:26.120 align:start position:0% get an idea what kind of products are out<00:04:24.419> there<00:04:24.690> it's<00:04:25.169> a<00:04:25.260> very<00:04:25.289> good<00:04:25.590> director<00:04:25.710> in 00:04:26.120 --> 00:04:26.130 align:start position:0% out there it's a very good director in 00:04:26.130 --> 00:04:28.279 align:start position:0% out there it's a very good director in my<00:04:26.250> opinion<00:04:26.580> to<00:04:26.700> see<00:04:26.900> what<00:04:27.900> kind<00:04:28.140> of 00:04:28.279 --> 00:04:28.289 align:start position:0% my opinion to see what kind of 00:04:28.289 --> 00:04:30.800 align:start position:0% my opinion to see what kind of certifications<00:04:28.979> our<00:04:29.100> author<00:04:29.490> what-who<00:04:30.390> under 00:04:30.800 --> 00:04:30.810 align:start position:0% certifications our author what-who under 00:04:30.810 --> 00:04:33.200 align:start position:0% certifications our author what-who under underwent<00:04:31.530> this<00:04:31.740> certification<00:04:32.430> process<00:04:32.849> I 00:04:33.200 --> 00:04:33.210 align:start position:0% underwent this certification process I 00:04:33.210 --> 00:04:36.050 align:start position:0% underwent this certification process I also<00:04:34.140> want<00:04:34.409> to<00:04:34.500> direct<00:04:35.280> your<00:04:35.580> attention<00:04:35.640> to 00:04:36.050 --> 00:04:36.060 align:start position:0% also want to direct your attention to 00:04:36.060 --> 00:04:37.020 align:start position:0% also want to direct your attention to this<00:04:36.240> thing 00:04:37.020 --> 00:04:37.030 align:start position:0% this thing 00:04:37.030 --> 00:04:39.480 align:start position:0% this thing the<00:04:37.240> open<00:04:37.960> source<00:04:38.140> it's<00:04:38.710> open<00:04:38.920> how<00:04:39.010> the<00:04:39.070> summit 00:04:39.480 --> 00:04:39.490 align:start position:0% the open source it's open how the summit 00:04:39.490 --> 00:04:41.010 align:start position:0% the open source it's open how the summit which<00:04:39.820> will<00:04:40.030> which<00:04:40.540> has<00:04:40.690> a<00:04:40.720> 10<00:04:40.990> year 00:04:41.010 --> 00:04:41.020 align:start position:0% which will which has a 10 year 00:04:41.020 --> 00:04:43.710 align:start position:0% which will which has a 10 year anniversary<00:04:41.350> and<00:04:41.950> it<00:04:42.070> will<00:04:42.190> happen<00:04:42.310> in<00:04:43.300> March 00:04:43.710 --> 00:04:43.720 align:start position:0% anniversary and it will happen in March 00:04:43.720 --> 00:04:46.110 align:start position:0% anniversary and it will happen in March next<00:04:44.440> year<00:04:44.650> in<00:04:44.950> New<00:04:45.070> York<00:04:45.340> so<00:04:45.610> you<00:04:45.670> can<00:04:45.940> already 00:04:46.110 --> 00:04:46.120 align:start position:0% next year in New York so you can already 00:04:46.120 --> 00:04:47.910 align:start position:0% next year in New York so you can already get<00:04:46.780> tickets<00:04:47.080> to<00:04:47.140> become<00:04:47.380> a<00:04:47.410> sponsor<00:04:47.650> if 00:04:47.910 --> 00:04:47.920 align:start position:0% get tickets to become a sponsor if 00:04:47.920 --> 00:04:50.340 align:start position:0% get tickets to become a sponsor if you're<00:04:48.010> interested<00:04:48.490> um<00:04:48.900> we<00:04:49.900> are<00:04:49.990> excited 00:04:50.340 --> 00:04:50.350 align:start position:0% you're interested um we are excited 00:04:50.350 --> 00:04:51.660 align:start position:0% you're interested um we are excited about<00:04:50.410> this<00:04:50.740> ones<00:04:50.980> because<00:04:51.280> it<00:04:51.370> would<00:04:51.520> be<00:04:51.640> a 00:04:51.660 --> 00:04:51.670 align:start position:0% about this ones because it would be a 00:04:51.670 --> 00:04:54.660 align:start position:0% about this ones because it would be a very<00:04:52.570> large<00:04:52.720> event<00:04:53.080> but<00:04:53.770> I'm<00:04:54.010> now<00:04:54.220> to<00:04:54.340> the<00:04:54.520> main 00:04:54.660 --> 00:04:54.670 align:start position:0% very large event but I'm now to the main 00:04:54.670 --> 00:04:56.130 align:start position:0% very large event but I'm now to the main part<00:04:54.850> of<00:04:55.030> my<00:04:55.120> talk<00:04:55.330> so<00:04:55.630> I<00:04:55.660> will<00:04:55.870> briefly 00:04:56.130 --> 00:04:56.140 align:start position:0% part of my talk so I will briefly 00:04:56.140 --> 00:04:58.290 align:start position:0% part of my talk so I will briefly introduce<00:04:56.530> what<00:04:57.070> open<00:04:57.550> source<00:04:57.580> hardware<00:04:57.940> is 00:04:58.290 --> 00:04:58.300 align:start position:0% introduce what open source hardware is 00:04:58.300 --> 00:05:00.690 align:start position:0% introduce what open source hardware is so<00:04:58.510> as<00:04:58.630> a<00:04:58.660> kind<00:04:59.440> of<00:04:59.560> long<00:04:59.800> a<00:04:59.830> description<00:05:00.310> that 00:05:00.690 --> 00:05:00.700 align:start position:0% so as a kind of long a description that 00:05:00.700 --> 00:05:02.280 align:start position:0% so as a kind of long a description that you<00:05:00.760> can<00:05:00.910> find<00:05:01.120> from<00:05:01.270> open<00:05:01.600> source<00:05:01.810> that<00:05:01.960> comic 00:05:02.280 --> 00:05:02.290 align:start position:0% you can find from open source that comic 00:05:02.290 --> 00:05:04.500 align:start position:0% you can find from open source that comic copied<00:05:02.530> is<00:05:02.650> robust<00:05:03.040> as<00:05:03.190> calm<00:05:03.580> and<00:05:03.760> pre-fit<00:05:04.360> to 00:05:04.500 --> 00:05:04.510 align:start position:0% copied is robust as calm and pre-fit to 00:05:04.510 --> 00:05:06.930 align:start position:0% copied is robust as calm and pre-fit to to<00:05:04.690> get<00:05:04.870> us<00:05:04.990> into<00:05:05.140> the<00:05:05.350> into<00:05:05.800> the<00:05:05.890> topic<00:05:06.280> open 00:05:06.930 --> 00:05:06.940 align:start position:0% to get us into the into the topic open 00:05:06.940 --> 00:05:08.400 align:start position:0% to get us into the into the topic open hardware<00:05:07.210> open<00:05:07.510> source<00:05:07.750> hardware<00:05:07.930> refers<00:05:08.380> to 00:05:08.400 --> 00:05:08.410 align:start position:0% hardware open source hardware refers to 00:05:08.410 --> 00:05:10.350 align:start position:0% hardware open source hardware refers to the<00:05:08.590> design<00:05:08.950> specifications<00:05:09.820> of<00:05:09.910> a<00:05:10.000> physical 00:05:10.350 --> 00:05:10.360 align:start position:0% the design specifications of a physical 00:05:10.360 --> 00:05:12.600 align:start position:0% the design specifications of a physical object<00:05:10.510> which<00:05:11.320> are<00:05:11.470> licensed<00:05:11.950> in<00:05:12.070> such<00:05:12.310> a<00:05:12.340> way 00:05:12.600 --> 00:05:12.610 align:start position:0% object which are licensed in such a way 00:05:12.610 --> 00:05:14.190 align:start position:0% object which are licensed in such a way that<00:05:12.880> said<00:05:13.390> objects<00:05:13.750> can<00:05:13.870> be<00:05:13.960> started 00:05:14.190 --> 00:05:14.200 align:start position:0% that said objects can be started 00:05:14.200 --> 00:05:15.930 align:start position:0% that said objects can be started modified<00:05:14.680> created<00:05:15.220> and<00:05:15.430> distributed<00:05:15.700> by 00:05:15.930 --> 00:05:15.940 align:start position:0% modified created and distributed by 00:05:15.940 --> 00:05:19.530 align:start position:0% modified created and distributed by anyone<00:05:16.330> that<00:05:16.360> means<00:05:16.860> in<00:05:17.860> opposition<00:05:18.640> to<00:05:19.210> open 00:05:19.530 --> 00:05:19.540 align:start position:0% anyone that means in opposition to open 00:05:19.540 --> 00:05:21.060 align:start position:0% anyone that means in opposition to open source<00:05:19.750> software<00:05:20.260> in<00:05:20.380> hardware<00:05:20.800> we<00:05:20.950> have<00:05:21.040> a 00:05:21.060 --> 00:05:21.070 align:start position:0% source software in hardware we have a 00:05:21.070 --> 00:05:24.140 align:start position:0% source software in hardware we have a lot<00:05:21.280> of<00:05:21.310> documentation<00:05:22.300> we<00:05:22.600> have<00:05:22.810> a<00:05:23.500> lot<00:05:23.950> of 00:05:24.140 --> 00:05:24.150 align:start position:0% lot of documentation we have a lot of 00:05:24.150 --> 00:05:27.420 align:start position:0% lot of documentation we have a lot of blueprints<00:05:25.150> logic<00:05:25.510> designs<00:05:25.810> a<00:05:25.960> lot<00:05:26.050> of<00:05:26.430> kind 00:05:27.420 --> 00:05:27.430 align:start position:0% blueprints logic designs a lot of kind 00:05:27.430 --> 00:05:29.100 align:start position:0% blueprints logic designs a lot of kind of<00:05:27.550> descriptions<00:05:28.240> about<00:05:28.540> the<00:05:28.660> object<00:05:28.990> we<00:05:29.080> are 00:05:29.100 --> 00:05:29.110 align:start position:0% of descriptions about the object we are 00:05:29.110 --> 00:05:31.770 align:start position:0% of descriptions about the object we are trying<00:05:29.380> to<00:05:29.470> open<00:05:30.340> source<00:05:30.520> and<00:05:30.880> these<00:05:31.330> all<00:05:31.540> are 00:05:31.770 --> 00:05:31.780 align:start position:0% trying to open source and these all are 00:05:31.780 --> 00:05:34.370 align:start position:0% trying to open source and these all are ideally<00:05:32.350> made<00:05:32.530> available<00:05:32.890> to<00:05:33.340> everyone 00:05:34.370 --> 00:05:34.380 align:start position:0% ideally made available to everyone 00:05:34.380 --> 00:05:38.180 align:start position:0% ideally made available to everyone there's<00:05:35.380> a<00:05:35.440> very<00:05:35.620> good<00:05:36.000> sum<00:05:37.000> up<00:05:37.210> of<00:05:37.480> this<00:05:37.720> whole 00:05:38.180 --> 00:05:38.190 align:start position:0% there's a very good sum up of this whole 00:05:38.190 --> 00:05:40.650 align:start position:0% there's a very good sum up of this whole movement<00:05:39.190> that<00:05:39.580> about<00:05:39.820> how<00:05:40.000> the<00:05:40.060> schwa<00:05:40.450> came 00:05:40.650 --> 00:05:40.660 align:start position:0% movement that about how the schwa came 00:05:40.660 --> 00:05:43.170 align:start position:0% movement that about how the schwa came came<00:05:41.350> to<00:05:41.500> be<00:05:41.620> this<00:05:41.890> book<00:05:42.700> which<00:05:42.940> is<00:05:42.970> called 00:05:43.170 --> 00:05:43.180 align:start position:0% came to be this book which is called 00:05:43.180 --> 00:05:45.120 align:start position:0% came to be this book which is called building<00:05:43.510> open-source<00:05:43.990> hardware<00:05:44.410> which<00:05:44.920> also 00:05:45.120 --> 00:05:45.130 align:start position:0% building open-source hardware which also 00:05:45.130 --> 00:05:46.860 align:start position:0% building open-source hardware which also explains<00:05:45.550> all<00:05:45.730> the<00:05:45.820> pitfalls<00:05:46.240> that<00:05:46.360> come<00:05:46.630> with 00:05:46.860 --> 00:05:46.870 align:start position:0% explains all the pitfalls that come with 00:05:46.870 --> 00:05:48.840 align:start position:0% explains all the pitfalls that come with open<00:05:47.530> source<00:05:47.860> hardware<00:05:48.010> the<00:05:48.310> differences 00:05:48.840 --> 00:05:48.850 align:start position:0% open source hardware the differences 00:05:48.850 --> 00:05:51.450 align:start position:0% open source hardware the differences also<00:05:49.270> from<00:05:49.510> a<00:05:49.570> logistic<00:05:50.110> point<00:05:50.680> of<00:05:50.800> view<00:05:51.010> this 00:05:51.450 --> 00:05:51.460 align:start position:0% also from a logistic point of view this 00:05:51.460 --> 00:05:53.610 align:start position:0% also from a logistic point of view this has<00:05:51.670> been<00:05:51.880> edited<00:05:52.750> by<00:05:52.810> Alicia<00:05:53.140> Cape<00:05:53.380> and 00:05:53.610 --> 00:05:53.620 align:start position:0% has been edited by Alicia Cape and 00:05:53.620 --> 00:05:55.860 align:start position:0% has been edited by Alicia Cape and features<00:05:53.950> also<00:05:54.130> a<00:05:54.250> lot<00:05:54.340> of<00:05:54.370> writers<00:05:55.270> and<00:05:55.570> a<00:05:55.720> lot 00:05:55.860 --> 00:05:55.870 align:start position:0% features also a lot of writers and a lot 00:05:55.870 --> 00:05:57.030 align:start position:0% features also a lot of writers and a lot of<00:05:55.900> different<00:05:56.200> projects<00:05:56.560> from<00:05:56.680> the<00:05:56.740> open 00:05:57.030 --> 00:05:57.040 align:start position:0% of different projects from the open 00:05:57.040 --> 00:05:59.520 align:start position:0% of different projects from the open source<00:05:57.220> hardware<00:05:57.310> context<00:05:58.260> but<00:05:59.260> to<00:05:59.350> explain 00:05:59.520 --> 00:05:59.530 align:start position:0% source hardware context but to explain 00:05:59.530 --> 00:06:01.170 align:start position:0% source hardware context but to explain better<00:05:59.740> what<00:05:59.860> it<00:06:00.130> is<00:06:00.310> what<00:06:00.520> is<00:06:00.640> actually<00:06:00.940> open 00:06:01.170 --> 00:06:01.180 align:start position:0% better what it is what is actually open 00:06:01.180 --> 00:06:04.050 align:start position:0% better what it is what is actually open hardware<00:06:01.420> so<00:06:01.960> as<00:06:02.530> Michael<00:06:03.010> Weinberg<00:06:03.460> here<00:06:03.700> I 00:06:04.050 --> 00:06:04.060 align:start position:0% hardware so as Michael Weinberg here I 00:06:04.060 --> 00:06:06.030 align:start position:0% hardware so as Michael Weinberg here I was<00:06:04.720> writing<00:06:05.020> in<00:06:05.110> this<00:06:05.170> book<00:06:05.230> hard<00:06:05.860> was 00:06:06.030 --> 00:06:06.040 align:start position:0% was writing in this book hard was 00:06:06.040 --> 00:06:08.100 align:start position:0% was writing in this book hard was already<00:06:06.430> born<00:06:06.730> open<00:06:07.210> but<00:06:07.600> we<00:06:07.870> have<00:06:07.990> to 00:06:08.100 --> 00:06:08.110 align:start position:0% already born open but we have to 00:06:08.110 --> 00:06:09.570 align:start position:0% already born open but we have to understand<00:06:08.530> also<00:06:08.770> that<00:06:08.890> hard<00:06:09.190> was<00:06:09.370> very 00:06:09.570 --> 00:06:09.580 align:start position:0% understand also that hard was very 00:06:09.580 --> 00:06:10.880 align:start position:0% understand also that hard was very different<00:06:09.820> and<00:06:10.120> open<00:06:10.360> source<00:06:10.540> software 00:06:10.880 --> 00:06:10.890 align:start position:0% different and open source software 00:06:10.890 --> 00:06:13.920 align:start position:0% different and open source software because<00:06:11.890> I'm<00:06:12.190> in<00:06:12.490> a<00:06:12.730> way<00:06:12.910> we<00:06:13.810> have<00:06:13.900> to 00:06:13.920 --> 00:06:13.930 align:start position:0% because I'm in a way we have to 00:06:13.930 --> 00:06:16.980 align:start position:0% because I'm in a way we have to understand<00:06:14.380> that<00:06:14.470> software<00:06:14.980> is<00:06:15.720> based<00:06:16.720> on 00:06:16.980 --> 00:06:16.990 align:start position:0% understand that software is based on 00:06:16.990 --> 00:06:18.780 align:start position:0% understand that software is based on copyright<00:06:17.380> and<00:06:17.800> software<00:06:18.160> protection<00:06:18.370> the 00:06:18.780 --> 00:06:18.790 align:start position:0% copyright and software protection the 00:06:18.790 --> 00:06:23.280 align:start position:0% copyright and software protection the GPL<00:06:19.180> and<00:06:19.290> CC<00:06:20.290> licenses<00:06:20.860> are<00:06:21.370> based<00:06:21.670> around<00:06:22.290> its 00:06:23.280 --> 00:06:23.290 align:start position:0% GPL and CC licenses are based around its 00:06:23.290 --> 00:06:25.440 align:start position:0% GPL and CC licenses are based around its are<00:06:23.860> considered<00:06:24.220> artistic<00:06:24.550> work<00:06:24.940> while 00:06:25.440 --> 00:06:25.450 align:start position:0% are considered artistic work while 00:06:25.450 --> 00:06:27.810 align:start position:0% are considered artistic work while hardware<00:06:26.170> falls<00:06:26.500> under<00:06:26.830> patent<00:06:27.280> law<00:06:27.430> because 00:06:27.810 --> 00:06:27.820 align:start position:0% hardware falls under patent law because 00:06:27.820 --> 00:06:29.550 align:start position:0% hardware falls under patent law because it's<00:06:27.940> considered<00:06:28.210> a<00:06:28.420> useful<00:06:28.810> article<00:06:28.960> or 00:06:29.550 --> 00:06:29.560 align:start position:0% it's considered a useful article or 00:06:29.560 --> 00:06:32.640 align:start position:0% it's considered a useful article or thinks<00:06:30.280> the<00:06:30.400> to<00:06:30.580> stuff<00:06:30.880> so<00:06:31.600> that<00:06:32.380> means 00:06:32.640 --> 00:06:32.650 align:start position:0% thinks the to stuff so that means 00:06:32.650 --> 00:06:34.350 align:start position:0% thinks the to stuff so that means there's<00:06:33.370> a<00:06:33.430> lot<00:06:33.550> of<00:06:33.640> patents<00:06:34.000> out<00:06:34.060> there<00:06:34.300> in 00:06:34.350 --> 00:06:34.360 align:start position:0% there's a lot of patents out there in 00:06:34.360 --> 00:06:37.470 align:start position:0% there's a lot of patents out there in the<00:06:34.420> hardware<00:06:34.690> world<00:06:34.930> so<00:06:35.500> how<00:06:36.250> kind<00:06:37.120> of<00:06:37.210> open 00:06:37.470 --> 00:06:37.480 align:start position:0% the hardware world so how kind of open 00:06:37.480 --> 00:06:38.910 align:start position:0% the hardware world so how kind of open hardware<00:06:37.690> projects<00:06:38.200> are<00:06:38.290> usually<00:06:38.410> protected 00:06:38.910 --> 00:06:38.920 align:start position:0% hardware projects are usually protected 00:06:38.920 --> 00:06:41.940 align:start position:0% hardware projects are usually protected then<00:06:39.430> in<00:06:39.520> a<00:06:39.610> way<00:06:39.730> is<00:06:39.940> through<00:06:40.770> its<00:06:41.770> through 00:06:41.940 --> 00:06:41.950 align:start position:0% then in a way is through its through 00:06:41.950 --> 00:06:44.220 align:start position:0% then in a way is through its through trademarks<00:06:42.640> as<00:06:42.850> is<00:06:43.030> very<00:06:43.240> evident<00:06:43.930> very 00:06:44.220 --> 00:06:44.230 align:start position:0% trademarks as is very evident very 00:06:44.230 --> 00:06:46.620 align:start position:0% trademarks as is very evident very visible<00:06:44.650> with<00:06:44.830> the<00:06:44.860> Arduino<00:06:45.370> project<00:06:45.850> which 00:06:46.620 --> 00:06:46.630 align:start position:0% visible with the Arduino project which 00:06:46.630 --> 00:06:48.030 align:start position:0% visible with the Arduino project which is<00:06:46.750> a<00:06:46.780> trademark<00:06:47.080> although<00:06:47.560> there<00:06:47.710> are<00:06:47.800> a<00:06:47.860> lot 00:06:48.030 --> 00:06:48.040 align:start position:0% is a trademark although there are a lot 00:06:48.040 --> 00:06:49.450 align:start position:0% is a trademark although there are a lot of<00:06:48.070> knockoffs<00:06:48.520> of<00:06:48.640> the<00:06:48.760> Rd<00:06:48.940> you<00:06:49.030> know 00:06:49.450 --> 00:06:49.460 align:start position:0% of knockoffs of the Rd you know 00:06:49.460 --> 00:06:50.920 align:start position:0% of knockoffs of the Rd you know everyone<00:06:49.820> knows<00:06:49.970> the<00:06:50.150> name<00:06:50.360> so<00:06:50.570> that<00:06:50.690> the 00:06:50.920 --> 00:06:50.930 align:start position:0% everyone knows the name so that the 00:06:50.930 --> 00:06:53.140 align:start position:0% everyone knows the name so that the trade<00:06:51.200> lock<00:06:51.410> is<00:06:51.620> secured<00:06:52.100> in<00:06:52.220> a<00:06:52.310> way<00:06:52.430> there's<00:06:53.060> a 00:06:53.140 --> 00:06:53.150 align:start position:0% trade lock is secured in a way there's a 00:06:53.150 --> 00:06:55.180 align:start position:0% trade lock is secured in a way there's a lot<00:06:53.240> of<00:06:53.390> specific<00:06:53.900> open<00:06:54.170> hardware<00:06:54.380> licenses<00:06:55.010> I 00:06:55.180 --> 00:06:55.190 align:start position:0% lot of specific open hardware licenses I 00:06:55.190 --> 00:06:56.740 align:start position:0% lot of specific open hardware licenses I listed<00:06:55.760> here<00:06:55.940> three<00:06:56.150> of<00:06:56.270> them<00:06:56.450> there's<00:06:56.660> the 00:06:56.740 --> 00:06:56.750 align:start position:0% listed here three of them there's the 00:06:56.750 --> 00:06:58.660 align:start position:0% listed here three of them there's the temporal<00:06:57.110> license<00:06:57.500> that's<00:06:57.980> the<00:06:58.100> Sun<00:06:58.340> open 00:06:58.660 --> 00:06:58.670 align:start position:0% temporal license that's the Sun open 00:06:58.670 --> 00:07:00.070 align:start position:0% temporal license that's the Sun open harbor<00:06:58.940> license<00:06:59.270> where<00:06:59.450> the<00:06:59.540> second<00:06:59.930> version 00:07:00.070 --> 00:07:00.080 align:start position:0% harbor license where the second version 00:07:00.080 --> 00:07:02.170 align:start position:0% harbor license where the second version is<00:07:00.260> currently<00:07:00.560> being<00:07:00.770> in<00:07:00.920> in<00:07:01.550> draft<00:07:01.790> it's<00:07:02.000> very 00:07:02.170 --> 00:07:02.180 align:start position:0% is currently being in in draft it's very 00:07:02.180 --> 00:07:03.910 align:start position:0% is currently being in in draft it's very interesting<00:07:02.600> read<00:07:03.140> if<00:07:03.260> you<00:07:03.350> are<00:07:03.410> interested 00:07:03.910 --> 00:07:03.920 align:start position:0% interesting read if you are interested 00:07:03.920 --> 00:07:05.830 align:start position:0% interesting read if you are interested in<00:07:04.550> looking<00:07:04.700> this<00:07:04.940> up<00:07:05.090> it's<00:07:05.600> a<00:07:05.660> lot<00:07:05.780> of 00:07:05.830 --> 00:07:05.840 align:start position:0% in looking this up it's a lot of 00:07:05.840 --> 00:07:07.210 align:start position:0% in looking this up it's a lot of discussion<00:07:06.320> also<00:07:06.620> on<00:07:06.680> what<00:07:06.830> are<00:07:06.950> the 00:07:07.210 --> 00:07:07.220 align:start position:0% discussion also on what are the 00:07:07.220 --> 00:07:11.080 align:start position:0% discussion also on what are the limitations<00:07:07.760> of<00:07:07.930> licenses<00:07:08.930> and<00:07:09.820> gplv3<00:07:10.820> is 00:07:11.080 --> 00:07:11.090 align:start position:0% limitations of licenses and gplv3 is 00:07:11.090 --> 00:07:13.720 align:start position:0% limitations of licenses and gplv3 is also<00:07:11.540> a<00:07:11.810> very<00:07:12.170> common<00:07:12.410> license<00:07:13.130> not<00:07:13.340> super 00:07:13.720 --> 00:07:13.730 align:start position:0% also a very common license not super 00:07:13.730 --> 00:07:15.400 align:start position:0% also a very common license not super common<00:07:14.090> but<00:07:14.120> would<00:07:14.540> be<00:07:14.660> the<00:07:14.720> ideal<00:07:14.990> license<00:07:15.320> in 00:07:15.400 --> 00:07:15.410 align:start position:0% common but would be the ideal license in 00:07:15.410 --> 00:07:17.710 align:start position:0% common but would be the ideal license in my<00:07:15.500> opinion<00:07:15.860> for<00:07:16.070> open<00:07:16.610> hardware<00:07:16.970> so<00:07:17.570> these 00:07:17.710 --> 00:07:17.720 align:start position:0% my opinion for open hardware so these 00:07:17.720 --> 00:07:21.370 align:start position:0% my opinion for open hardware so these are<00:07:17.900> the<00:07:17.990> two<00:07:18.170> most<00:07:18.830> common<00:07:19.570> unknown<00:07:20.570> open 00:07:21.370 --> 00:07:21.380 align:start position:0% are the two most common unknown open 00:07:21.380 --> 00:07:22.630 align:start position:0% are the two most common unknown open other<00:07:21.530> product<00:07:21.950> so<00:07:22.010> this<00:07:22.100> is<00:07:22.250> the<00:07:22.340> other<00:07:22.490> you 00:07:22.630 --> 00:07:22.640 align:start position:0% other product so this is the other you 00:07:22.640 --> 00:07:24.730 align:start position:0% other product so this is the other you all<00:07:22.940> know<00:07:23.480> it<00:07:23.600> possibly<00:07:24.110> it's<00:07:24.230> it's<00:07:24.530> coming 00:07:24.730 --> 00:07:24.740 align:start position:0% all know it possibly it's it's coming 00:07:24.740 --> 00:07:26.470 align:start position:0% all know it possibly it's it's coming from<00:07:24.860> the<00:07:25.010> maker<00:07:25.190> movement<00:07:25.310> it<00:07:25.790> was<00:07:25.910> it's 00:07:26.470 --> 00:07:26.480 align:start position:0% from the maker movement it was it's 00:07:26.480 --> 00:07:27.970 align:start position:0% from the maker movement it was it's considered<00:07:27.080> to<00:07:27.110> be<00:07:27.230> one<00:07:27.350> of<00:07:27.410> these<00:07:27.560> tools<00:07:27.800> for 00:07:27.970 --> 00:07:27.980 align:start position:0% considered to be one of these tools for 00:07:27.980 --> 00:07:29.980 align:start position:0% considered to be one of these tools for the<00:07:28.070> maker<00:07:28.250> movement<00:07:28.340> and<00:07:28.850> of<00:07:29.240> course<00:07:29.510> open 00:07:29.980 --> 00:07:29.990 align:start position:0% the maker movement and of course open 00:07:29.990 --> 00:07:33.520 align:start position:0% the maker movement and of course open like<00:07:30.680> like<00:07:31.270> RepRap<00:07:32.270> printers<00:07:32.720> or<00:07:32.840> 3d<00:07:33.080> printers 00:07:33.520 --> 00:07:33.530 align:start position:0% like like RepRap printers or 3d printers 00:07:33.530 --> 00:07:35.530 align:start position:0% like like RepRap printers or 3d printers are<00:07:33.890> also<00:07:34.100> considered<00:07:34.880> open<00:07:35.180> hardware<00:07:35.390> not 00:07:35.530 --> 00:07:35.540 align:start position:0% are also considered open hardware not 00:07:35.540 --> 00:07:37.660 align:start position:0% are also considered open hardware not all<00:07:35.690> of<00:07:35.810> them<00:07:35.990> but<00:07:36.560> the<00:07:37.070> Ultimaker<00:07:37.340> is 00:07:37.660 --> 00:07:37.670 align:start position:0% all of them but the Ultimaker is 00:07:37.670 --> 00:07:39.490 align:start position:0% all of them but the Ultimaker is Ultimaker<00:07:38.360> one<00:07:38.570> is<00:07:38.690> an<00:07:38.780> open<00:07:38.960> hardware<00:07:39.230> piece 00:07:39.490 --> 00:07:39.500 align:start position:0% Ultimaker one is an open hardware piece 00:07:39.500 --> 00:07:42.340 align:start position:0% Ultimaker one is an open hardware piece so<00:07:39.710> in<00:07:40.130> my<00:07:40.340> opinion<00:07:40.460> we<00:07:40.910> can<00:07:41.390> see<00:07:41.570> two<00:07:41.870> effects 00:07:42.340 --> 00:07:42.350 align:start position:0% so in my opinion we can see two effects 00:07:42.350 --> 00:07:43.780 align:start position:0% so in my opinion we can see two effects of<00:07:42.440> open<00:07:42.680> harder<00:07:42.890> which<00:07:43.040> are<00:07:43.220> in<00:07:43.310> my<00:07:43.430> opinion 00:07:43.780 --> 00:07:43.790 align:start position:0% of open harder which are in my opinion 00:07:43.790 --> 00:07:45.340 align:start position:0% of open harder which are in my opinion really<00:07:43.820> viable<00:07:44.480> and<00:07:44.600> which<00:07:44.720> are<00:07:44.870> different<00:07:45.140> to 00:07:45.340 --> 00:07:45.350 align:start position:0% really viable and which are different to 00:07:45.350 --> 00:07:47.140 align:start position:0% really viable and which are different to close<00:07:45.560> source<00:07:45.860> hardware<00:07:46.070> so<00:07:46.820> it's<00:07:46.970> very 00:07:47.140 --> 00:07:47.150 align:start position:0% close source hardware so it's very 00:07:47.150 --> 00:07:48.940 align:start position:0% close source hardware so it's very educational<00:07:47.300> that<00:07:47.990> means<00:07:48.200> it's<00:07:48.500> education 00:07:48.940 --> 00:07:48.950 align:start position:0% educational that means it's education 00:07:48.950 --> 00:07:50.530 align:start position:0% educational that means it's education because<00:07:49.220> you<00:07:49.310> can<00:07:49.460> study<00:07:49.730> the<00:07:49.940> designs<00:07:50.330> you 00:07:50.530 --> 00:07:50.540 align:start position:0% because you can study the designs you 00:07:50.540 --> 00:07:52.900 align:start position:0% because you can study the designs you can<00:07:50.660> study<00:07:50.840> the<00:07:51.670> specifications<00:07:52.670> you<00:07:52.760> can 00:07:52.900 --> 00:07:52.910 align:start position:0% can study the specifications you can 00:07:52.910 --> 00:07:54.070 align:start position:0% can study the specifications you can look<00:07:53.240> at<00:07:53.360> the<00:07:53.420> actual<00:07:53.720> hardware<00:07:54.020> could 00:07:54.070 --> 00:07:54.080 align:start position:0% look at the actual hardware could 00:07:54.080 --> 00:07:56.530 align:start position:0% look at the actual hardware could understand<00:07:54.530> what's<00:07:54.710> actually<00:07:54.800> going<00:07:55.100> on<00:07:55.540> that 00:07:56.530 --> 00:07:56.540 align:start position:0% understand what's actually going on that 00:07:56.540 --> 00:07:58.060 align:start position:0% understand what's actually going on that also<00:07:56.780> means<00:07:57.110> you<00:07:57.200> can<00:07:57.380> potentially<00:07:57.770> write 00:07:58.060 --> 00:07:58.070 align:start position:0% also means you can potentially write 00:07:58.070 --> 00:08:02.230 align:start position:0% also means you can potentially write your<00:07:58.280> own<00:07:58.400> farm<00:07:58.720> about<00:08:00.730> with<00:08:01.730> the<00:08:01.850> hardware 00:08:02.230 --> 00:08:02.240 align:start position:0% your own farm about with the hardware 00:08:02.240 --> 00:08:03.550 align:start position:0% your own farm about with the hardware that<00:08:02.270> you<00:08:02.480> are<00:08:02.630> looking<00:08:02.930> at<00:08:03.200> and 00:08:03.550 --> 00:08:03.560 align:start position:0% that you are looking at and 00:08:03.560 --> 00:08:05.830 align:start position:0% that you are looking at and verifiability<00:08:04.460> which<00:08:04.850> is<00:08:04.970> the<00:08:05.390> point<00:08:05.630> i'm 00:08:05.830 --> 00:08:05.840 align:start position:0% verifiability which is the point i'm 00:08:05.840 --> 00:08:09.640 align:start position:0% verifiability which is the point i'm stressing<00:08:06.680> much<00:08:06.950> more<00:08:07.190> because<00:08:07.520> in<00:08:08.210> a<00:08:08.650> much 00:08:09.640 --> 00:08:09.650 align:start position:0% stressing much more because in a much 00:08:09.650 --> 00:08:12.490 align:start position:0% stressing much more because in a much more<00:08:09.920> a<00:08:10.340> much<00:08:10.750> connected<00:08:11.750> world<00:08:11.960> that<00:08:12.230> we<00:08:12.350> have 00:08:12.490 --> 00:08:12.500 align:start position:0% more a much connected world that we have 00:08:12.500 --> 00:08:14.440 align:start position:0% more a much connected world that we have today<00:08:12.800> and<00:08:13.070> also<00:08:13.490> in<00:08:13.940> regards<00:08:14.390> to 00:08:14.440 --> 00:08:14.450 align:start position:0% today and also in regards to 00:08:14.450 --> 00:08:15.760 align:start position:0% today and also in regards to cryptography<00:08:15.110> and<00:08:15.470> blockchain 00:08:15.760 --> 00:08:15.770 align:start position:0% cryptography and blockchain 00:08:15.770 --> 00:08:18.610 align:start position:0% cryptography and blockchain verifiability<00:08:16.460> is<00:08:16.730> key<00:08:17.180> in<00:08:17.420> my<00:08:17.630> opinion<00:08:18.020> so 00:08:18.610 --> 00:08:18.620 align:start position:0% verifiability is key in my opinion so 00:08:18.620 --> 00:08:20.440 align:start position:0% verifiability is key in my opinion so also<00:08:19.160> if<00:08:19.220> we<00:08:19.310> look<00:08:19.460> at<00:08:19.580> this<00:08:19.670> kind<00:08:19.910> of<00:08:20.000> idea<00:08:20.330> of 00:08:20.440 --> 00:08:20.450 align:start position:0% also if we look at this kind of idea of 00:08:20.450 --> 00:08:23.950 align:start position:0% also if we look at this kind of idea of zero<00:08:20.570> trust<00:08:21.970> verifiability<00:08:22.970> is<00:08:23.390> it's<00:08:23.720> very 00:08:23.950 --> 00:08:23.960 align:start position:0% zero trust verifiability is it's very 00:08:23.960 --> 00:08:26.290 align:start position:0% zero trust verifiability is it's very important<00:08:24.470> in<00:08:24.530> order<00:08:24.740> to<00:08:24.800> make<00:08:25.730> sure<00:08:25.760> that<00:08:26.000> we 00:08:26.290 --> 00:08:26.300 align:start position:0% important in order to make sure that we 00:08:26.300 --> 00:08:28.240 align:start position:0% important in order to make sure that we don't<00:08:26.870> have<00:08:27.110> to<00:08:27.230> trust<00:08:27.530> we<00:08:27.740> can<00:08:27.770> always<00:08:28.100> verify 00:08:28.240 --> 00:08:28.250 align:start position:0% don't have to trust we can always verify 00:08:28.250 --> 00:08:30.370 align:start position:0% don't have to trust we can always verify and<00:08:28.760> this<00:08:28.880> is<00:08:29.000> very<00:08:29.240> complicated<00:08:29.690> with<00:08:30.110> modern 00:08:30.370 --> 00:08:30.380 align:start position:0% and this is very complicated with modern 00:08:30.380 --> 00:08:32.170 align:start position:0% and this is very complicated with modern hardware<00:08:30.590> it's<00:08:31.190> actually<00:08:31.430> not<00:08:31.550> only<00:08:31.640> not<00:08:31.940> even 00:08:32.170 --> 00:08:32.180 align:start position:0% hardware it's actually not only not even 00:08:32.180 --> 00:08:35.290 align:start position:0% hardware it's actually not only not even possible<00:08:32.570> in<00:08:32.690> most<00:08:32.900> cases<00:08:33.940> so<00:08:34.940> I<00:08:34.970> want<00:08:35.240> a 00:08:35.290 --> 00:08:35.300 align:start position:0% possible in most cases so I want a 00:08:35.300 --> 00:08:37.540 align:start position:0% possible in most cases so I want a little<00:08:35.660> bit<00:08:35.780> explain<00:08:36.530> is<00:08:36.950> that<00:08:37.160> they<00:08:37.280> are<00:08:37.370> very 00:08:37.540 --> 00:08:37.550 align:start position:0% little bit explain is that they are very 00:08:37.550 --> 00:08:39.250 align:start position:0% little bit explain is that they are very affordable<00:08:37.730> hardware<00:08:38.300> and<00:08:38.810> we<00:08:38.900> had<00:08:39.020> a<00:08:39.050> very 00:08:39.250 --> 00:08:39.260 align:start position:0% affordable hardware and we had a very 00:08:39.260 --> 00:08:42.190 align:start position:0% affordable hardware and we had a very interesting<00:08:39.620> panel<00:08:40.040> discussion<00:08:40.660> today<00:08:41.660> in 00:08:42.190 --> 00:08:42.200 align:start position:0% interesting panel discussion today in 00:08:42.200 --> 00:08:43.540 align:start position:0% interesting panel discussion today in the<00:08:42.350> Sun<00:08:42.530> it<00:08:42.650> was<00:08:42.710> a<00:08:42.770> bit<00:08:42.920> hot<00:08:43.100> but<00:08:43.340> we<00:08:43.430> had<00:08:43.520> a 00:08:43.540 --> 00:08:43.550 align:start position:0% the Sun it was a bit hot but we had a 00:08:43.550 --> 00:08:46.150 align:start position:0% the Sun it was a bit hot but we had a very<00:08:43.610> interesting<00:08:44.570> approach<00:08:44.930> we<00:08:45.320> discussed 00:08:46.150 --> 00:08:46.160 align:start position:0% very interesting approach we discussed 00:08:46.160 --> 00:08:47.650 align:start position:0% very interesting approach we discussed how<00:08:46.340> vintage<00:08:46.730> hardware<00:08:47.090> could<00:08:47.270> possibly 00:08:47.650 --> 00:08:47.660 align:start position:0% how vintage hardware could possibly 00:08:47.660 --> 00:08:49.510 align:start position:0% how vintage hardware could possibly solve<00:08:47.990> this<00:08:48.170> kind<00:08:48.440> of<00:08:48.560> security<00:08:49.130> nightmare 00:08:49.510 --> 00:08:49.520 align:start position:0% solve this kind of security nightmare 00:08:49.520 --> 00:08:51.280 align:start position:0% solve this kind of security nightmare this<00:08:49.940> verification<00:08:50.270> debacle<00:08:50.990> that<00:08:51.080> we<00:08:51.170> have 00:08:51.280 --> 00:08:51.290 align:start position:0% this verification debacle that we have 00:08:51.290 --> 00:08:53.400 align:start position:0% this verification debacle that we have these<00:08:51.470> days 00:08:53.400 --> 00:08:53.410 align:start position:0% these days 00:08:53.410 --> 00:08:55.600 align:start position:0% these days long<00:08:54.410> story<00:08:54.590> short<00:08:54.710> we're<00:08:55.070> using<00:08:55.220> a<00:08:55.370> lot<00:08:55.580> of 00:08:55.600 --> 00:08:55.610 align:start position:0% long story short we're using a lot of 00:08:55.610 --> 00:08:57.940 align:start position:0% long story short we're using a lot of non<00:08:56.020> verifiable<00:08:57.020> hardware<00:08:57.320> these<00:08:57.470> days<00:08:57.650> so<00:08:57.860> if 00:08:57.940 --> 00:08:57.950 align:start position:0% non verifiable hardware these days so if 00:08:57.950 --> 00:08:59.200 align:start position:0% non verifiable hardware these days so if you<00:08:58.040> look<00:08:58.190> at<00:08:58.310> your<00:08:58.400> phones<00:08:58.700> if<00:08:58.910> you<00:08:58.970> look<00:08:59.120> at 00:08:59.200 --> 00:08:59.210 align:start position:0% you look at your phones if you look at 00:08:59.210 --> 00:09:00.940 align:start position:0% you look at your phones if you look at all<00:08:59.360> these<00:08:59.510> kind<00:08:59.750> of<00:08:59.840> components<00:09:00.800> that<00:09:00.860> you 00:09:00.940 --> 00:09:00.950 align:start position:0% all these kind of components that you 00:09:00.950 --> 00:09:02.920 align:start position:0% all these kind of components that you have<00:09:00.980> around<00:09:01.310> your<00:09:01.460> computers<00:09:02.240> what<00:09:02.570> not 00:09:02.920 --> 00:09:02.930 align:start position:0% have around your computers what not 00:09:02.930 --> 00:09:05.350 align:start position:0% have around your computers what not all<00:09:03.110> are<00:09:03.650> not<00:09:04.070> really<00:09:04.400> verifiable<00:09:05.030> that<00:09:05.150> means 00:09:05.350 --> 00:09:05.360 align:start position:0% all are not really verifiable that means 00:09:05.360 --> 00:09:06.550 align:start position:0% all are not really verifiable that means if<00:09:05.480> I<00:09:05.600> really<00:09:05.900> want<00:09:06.050> to<00:09:06.110> know<00:09:06.170> okay<00:09:06.380> what's 00:09:06.550 --> 00:09:06.560 align:start position:0% if I really want to know okay what's 00:09:06.560 --> 00:09:08.110 align:start position:0% if I really want to know okay what's going<00:09:06.830> on<00:09:06.950> is<00:09:07.130> there<00:09:07.310> some<00:09:07.460> computation<00:09:08.090> that 00:09:08.110 --> 00:09:08.120 align:start position:0% going on is there some computation that 00:09:08.120 --> 00:09:09.910 align:start position:0% going on is there some computation that happened<00:09:08.540> that<00:09:08.930> I<00:09:08.990> want<00:09:09.230> to<00:09:09.290> make<00:09:09.500> sure<00:09:09.530> that 00:09:09.910 --> 00:09:09.920 align:start position:0% happened that I want to make sure that 00:09:09.920 --> 00:09:12.160 align:start position:0% happened that I want to make sure that isn't<00:09:10.100> compromised<00:09:10.760> it's<00:09:11.390> really<00:09:11.810> really 00:09:12.160 --> 00:09:12.170 align:start position:0% isn't compromised it's really really 00:09:12.170 --> 00:09:14.140 align:start position:0% isn't compromised it's really really hard<00:09:12.320> to<00:09:12.410> do<00:09:12.590> so<00:09:12.830> so<00:09:13.310> one<00:09:13.520> in<00:09:13.610> this<00:09:13.730> context 00:09:14.140 --> 00:09:14.150 align:start position:0% hard to do so so one in this context 00:09:14.150 --> 00:09:17.640 align:start position:0% hard to do so so one in this context also<00:09:14.650> refer<00:09:15.650> to<00:09:15.860> an<00:09:15.920> interesting 00:09:17.640 --> 00:09:17.650 align:start position:0% also refer to an interesting 00:09:17.650 --> 00:09:19.900 align:start position:0% also refer to an interesting certification<00:09:18.650> program<00:09:19.040> from<00:09:19.610> the<00:09:19.760> Free 00:09:19.900 --> 00:09:19.910 align:start position:0% certification program from the Free 00:09:19.910 --> 00:09:23.020 align:start position:0% certification program from the Free Software<00:09:20.030> Foundation<00:09:20.380> who<00:09:21.730> identified<00:09:22.730> and 00:09:23.020 --> 00:09:23.030 align:start position:0% Software Foundation who identified and 00:09:23.030 --> 00:09:24.910 align:start position:0% Software Foundation who identified and they<00:09:23.180> basically<00:09:23.570> listed<00:09:24.050> a<00:09:24.080> lot<00:09:24.200> of<00:09:24.350> devices 00:09:24.910 --> 00:09:24.920 align:start position:0% they basically listed a lot of devices 00:09:24.920 --> 00:09:27.430 align:start position:0% they basically listed a lot of devices that<00:09:25.280> can<00:09:25.790> be<00:09:25.850> used<00:09:25.940> in<00:09:26.270> modern-day<00:09:26.900> hardware 00:09:27.430 --> 00:09:27.440 align:start position:0% that can be used in modern-day hardware 00:09:27.440 --> 00:09:30.190 align:start position:0% that can be used in modern-day hardware and<00:09:27.590> in<00:09:27.760> desktop<00:09:28.760> computers<00:09:29.240> that<00:09:29.750> are<00:09:29.810> not 00:09:30.190 --> 00:09:30.200 align:start position:0% and in desktop computers that are not 00:09:30.200 --> 00:09:32.110 align:start position:0% and in desktop computers that are not having<00:09:30.680> binary<00:09:31.100> blobs<00:09:31.370> that<00:09:31.610> means<00:09:31.820> you<00:09:31.970> can 00:09:32.110 --> 00:09:32.120 align:start position:0% having binary blobs that means you can 00:09:32.120 --> 00:09:34.420 align:start position:0% having binary blobs that means you can actually<00:09:32.380> verify<00:09:33.380> them<00:09:33.650> by<00:09:33.890> making<00:09:34.070> sure<00:09:34.280> that 00:09:34.420 --> 00:09:34.430 align:start position:0% actually verify them by making sure that 00:09:34.430 --> 00:09:35.800 align:start position:0% actually verify them by making sure that the<00:09:34.550> firmware<00:09:34.790> hasn't<00:09:35.180> been<00:09:35.300> compromised 00:09:35.800 --> 00:09:35.810 align:start position:0% the firmware hasn't been compromised 00:09:35.810 --> 00:09:38.350 align:start position:0% the firmware hasn't been compromised also<00:09:36.500> maybe<00:09:36.650> to<00:09:36.890> contextualise<00:09:37.400> limit<00:09:37.910> the 00:09:38.350 --> 00:09:38.360 align:start position:0% also maybe to contextualise limit the 00:09:38.360 --> 00:09:39.460 align:start position:0% also maybe to contextualise limit the Linux<00:09:38.630> kernel<00:09:38.750> as<00:09:38.900> a<00:09:38.930> lot<00:09:39.110> of<00:09:39.230> proprietary 00:09:39.460 --> 00:09:39.470 align:start position:0% Linux kernel as a lot of proprietary 00:09:39.470 --> 00:09:42.010 align:start position:0% Linux kernel as a lot of proprietary drivers<00:09:40.250> so<00:09:41.150> there's<00:09:41.510> also<00:09:41.690> the<00:09:41.870> little 00:09:42.010 --> 00:09:42.020 align:start position:0% drivers so there's also the little 00:09:42.020 --> 00:09:45.220 align:start position:0% drivers so there's also the little clearer<00:09:42.560> um<00:09:42.800> Fork<00:09:43.400> of<00:09:43.550> Linux<00:09:43.910> which<00:09:44.450> um<00:09:44.720> tries 00:09:45.220 --> 00:09:45.230 align:start position:0% clearer um Fork of Linux which um tries 00:09:45.230 --> 00:09:47.530 align:start position:0% clearer um Fork of Linux which um tries to<00:09:45.500> develop<00:09:45.950> in<00:09:46.610> a<00:09:46.730> way<00:09:46.760> the<00:09:47.000> whole<00:09:47.150> Linux 00:09:47.530 --> 00:09:47.540 align:start position:0% to develop in a way the whole Linux 00:09:47.540 --> 00:09:50.050 align:start position:0% to develop in a way the whole Linux kernel<00:09:47.900> so<00:09:48.380> I'm<00:09:48.650> usually<00:09:48.920> if<00:09:49.340> you<00:09:49.520> remove<00:09:49.850> all 00:09:50.050 --> 00:09:50.060 align:start position:0% kernel so I'm usually if you remove all 00:09:50.060 --> 00:09:51.640 align:start position:0% kernel so I'm usually if you remove all the<00:09:50.180> commits<00:09:50.480> from<00:09:50.750> leaders<00:09:51.080> table<00:09:51.290> arts<00:09:51.530> you 00:09:51.640 --> 00:09:51.650 align:start position:0% the commits from leaders table arts you 00:09:51.650 --> 00:09:53.740 align:start position:0% the commits from leaders table arts you are<00:09:52.160> almost<00:09:52.550> good<00:09:52.850> to<00:09:52.910> go<00:09:53.150> with<00:09:53.330> the<00:09:53.450> almost 00:09:53.740 --> 00:09:53.750 align:start position:0% are almost good to go with the almost 00:09:53.750 --> 00:09:57.130 align:start position:0% are almost good to go with the almost Libre<00:09:54.080> kernel<00:09:55.180> this<00:09:56.180> is<00:09:56.390> a<00:09:56.420> very<00:09:56.750> interesting 00:09:57.130 --> 00:09:57.140 align:start position:0% Libre kernel this is a very interesting 00:09:57.140 --> 00:09:59.560 align:start position:0% Libre kernel this is a very interesting piece<00:09:57.350> of<00:09:57.380> hardware<00:09:57.980> also<00:09:58.640> on<00:09:59.030> this<00:09:59.210> and<00:09:59.390> I<00:09:59.420> can 00:09:59.560 --> 00:09:59.570 align:start position:0% piece of hardware also on this and I can 00:09:59.570 --> 00:10:02.170 align:start position:0% piece of hardware also on this and I can strongly<00:09:59.840> suggest<00:10:00.230> any<00:10:00.670> crypto<00:10:01.670> on<00:10:01.910> a<00:10:01.940> case 00:10:02.170 --> 00:10:02.180 align:start position:0% strongly suggest any crypto on a case 00:10:02.180 --> 00:10:04.180 align:start position:0% strongly suggest any crypto on a case the<00:10:02.360> cypherpunks<00:10:02.660> on<00:10:03.080> this<00:10:03.230> device<00:10:03.470> it's<00:10:03.980> a 00:10:04.180 --> 00:10:04.190 align:start position:0% the cypherpunks on this device it's a 00:10:04.190 --> 00:10:06.640 align:start position:0% the cypherpunks on this device it's a it's<00:10:04.910> an<00:10:05.000> all<00:10:05.150> that<00:10:05.330> thing<00:10:05.600> but<00:10:05.780> it's<00:10:05.990> 200<00:10:06.500> and 00:10:06.640 --> 00:10:06.650 align:start position:0% it's an all that thing but it's 200 and 00:10:06.650 --> 00:10:08.890 align:start position:0% it's an all that thing but it's 200 and the<00:10:06.770> interesting<00:10:07.160> piece<00:10:07.520> or<00:10:08.450> the<00:10:08.570> interesting 00:10:08.890 --> 00:10:08.900 align:start position:0% the interesting piece or the interesting 00:10:08.900 --> 00:10:10.300 align:start position:0% the interesting piece or the interesting part<00:10:09.110> of<00:10:09.170> it<00:10:09.320> is<00:10:09.470> actually<00:10:09.740> that<00:10:09.830> you<00:10:09.950> can<00:10:10.100> use 00:10:10.300 --> 00:10:10.310 align:start position:0% part of it is actually that you can use 00:10:10.310 --> 00:10:12.790 align:start position:0% part of it is actually that you can use this<00:10:11.240> because<00:10:11.480> it's<00:10:11.750> verifiable<00:10:12.470> it<00:10:12.590> runs 00:10:12.790 --> 00:10:12.800 align:start position:0% this because it's verifiable it runs 00:10:12.800 --> 00:10:14.320 align:start position:0% this because it's verifiable it runs live<00:10:13.280> reports<00:10:13.700> you<00:10:13.850> can<00:10:13.970> make<00:10:14.120> sure<00:10:14.240> that 00:10:14.320 --> 00:10:14.330 align:start position:0% live reports you can make sure that 00:10:14.330 --> 00:10:17.290 align:start position:0% live reports you can make sure that there's<00:10:14.660> no<00:10:14.780> BIOS<00:10:15.470> backdoors<00:10:16.160> inside<00:10:16.490> you<00:10:17.090> can 00:10:17.290 --> 00:10:17.300 align:start position:0% there's no BIOS backdoors inside you can 00:10:17.300 --> 00:10:20.620 align:start position:0% there's no BIOS backdoors inside you can basically<00:10:17.780> run<00:10:18.520> it<00:10:19.520> has<00:10:19.700> not<00:10:20.000> no<00:10:20.300> inter 00:10:20.620 --> 00:10:20.630 align:start position:0% basically run it has not no inter 00:10:20.630 --> 00:10:22.360 align:start position:0% basically run it has not no inter management<00:10:21.050> engine<00:10:21.380> on<00:10:21.560> it<00:10:21.680> so<00:10:22.100> you<00:10:22.190> can 00:10:22.360 --> 00:10:22.370 align:start position:0% management engine on it so you can 00:10:22.370 --> 00:10:24.610 align:start position:0% management engine on it so you can basically<00:10:22.580> make<00:10:22.970> sure<00:10:23.000> that<00:10:23.390> in<00:10:24.020> a<00:10:24.170> way<00:10:24.350> you 00:10:24.610 --> 00:10:24.620 align:start position:0% basically make sure that in a way you 00:10:24.620 --> 00:10:26.650 align:start position:0% basically make sure that in a way you create<00:10:25.280> your<00:10:25.400> keys<00:10:25.700> and<00:10:26.030> if<00:10:26.150> you<00:10:26.240> use<00:10:26.360> it<00:10:26.480> in<00:10:26.570> a 00:10:26.650 --> 00:10:26.660 align:start position:0% create your keys and if you use it in a 00:10:26.660 --> 00:10:29.500 align:start position:0% create your keys and if you use it in a kind<00:10:26.870> of<00:10:26.960> an<00:10:27.220> offline<00:10:28.220> manner<00:10:28.850> you<00:10:29.180> can<00:10:29.210> even 00:10:29.500 --> 00:10:29.510 align:start position:0% kind of an offline manner you can even 00:10:29.510 --> 00:10:31.270 align:start position:0% kind of an offline manner you can even make<00:10:29.630> sure<00:10:29.780> that<00:10:29.930> your<00:10:30.890> keys<00:10:31.100> aren't 00:10:31.270 --> 00:10:31.280 align:start position:0% make sure that your keys aren't 00:10:31.280 --> 00:10:35.530 align:start position:0% make sure that your keys aren't compromised<00:10:31.850> but<00:10:32.570> it<00:10:32.960> comes<00:10:33.260> with<00:10:33.530> a<00:10:33.710> few<00:10:34.540> kind 00:10:35.530 --> 00:10:35.540 align:start position:0% compromised but it comes with a few kind 00:10:35.540 --> 00:10:37.630 align:start position:0% compromised but it comes with a few kind of<00:10:35.570> pitfalls<00:10:36.050> in<00:10:36.260> my<00:10:36.380> opinion<00:10:36.710> so<00:10:37.190> we<00:10:37.310> have<00:10:37.400> two 00:10:37.630 --> 00:10:37.640 align:start position:0% of pitfalls in my opinion so we have two 00:10:37.640 --> 00:10:39.040 align:start position:0% of pitfalls in my opinion so we have two problems<00:10:37.880> still<00:10:38.270> also<00:10:38.450> with<00:10:38.720> this<00:10:38.840> kind<00:10:39.020> of 00:10:39.040 --> 00:10:39.050 align:start position:0% problems still also with this kind of 00:10:39.050 --> 00:10:40.450 align:start position:0% problems still also with this kind of libera<00:10:39.320> hardened<00:10:39.620> with<00:10:39.800> this<00:10:39.920> old<00:10:40.130> vintage 00:10:40.450 --> 00:10:40.460 align:start position:0% libera hardened with this old vintage 00:10:40.460 --> 00:10:41.920 align:start position:0% libera hardened with this old vintage hardware<00:10:40.820> if<00:10:41.060> we<00:10:41.240> want<00:10:41.420> to<00:10:41.480> use<00:10:41.600> this<00:10:41.690> in<00:10:41.840> kind 00:10:41.920 --> 00:10:41.930 align:start position:0% hardware if we want to use this in kind 00:10:41.930 --> 00:10:43.690 align:start position:0% hardware if we want to use this in kind of<00:10:42.050> high<00:10:42.170> security<00:10:42.380> applications<00:10:43.130> we<00:10:43.670> have 00:10:43.690 --> 00:10:43.700 align:start position:0% of high security applications we have 00:10:43.700 --> 00:10:45.850 align:start position:0% of high security applications we have SSDs<00:10:44.300> which<00:10:44.540> are<00:10:44.720> a<00:10:44.960> problem<00:10:45.440> because<00:10:45.590> they 00:10:45.850 --> 00:10:45.860 align:start position:0% SSDs which are a problem because they 00:10:45.860 --> 00:10:48.790 align:start position:0% SSDs which are a problem because they again<00:10:46.400> impaired<00:10:47.120> another<00:10:47.620> processor<00:10:48.620> which 00:10:48.790 --> 00:10:48.800 align:start position:0% again impaired another processor which 00:10:48.800 --> 00:10:50.500 align:start position:0% again impaired another processor which could<00:10:49.040> be<00:10:49.220> potentially<00:10:49.700> compromised<00:10:50.240> and 00:10:50.500 --> 00:10:50.510 align:start position:0% could be potentially compromised and 00:10:50.510 --> 00:10:53.320 align:start position:0% could be potentially compromised and there<00:10:51.200> could<00:10:51.320> be<00:10:51.350> other<00:10:51.470> back<00:10:52.190> to<00:10:52.370> us<00:10:52.460> um<00:10:52.760> in 00:10:53.320 --> 00:10:53.330 align:start position:0% there could be other back to us um in 00:10:53.330 --> 00:10:55.870 align:start position:0% there could be other back to us um in the<00:10:53.450> CPUs<00:10:53.900> that<00:10:53.990> we<00:10:54.200> don't<00:10:54.380> know<00:10:54.500> about<00:10:54.880> which 00:10:55.870 --> 00:10:55.880 align:start position:0% the CPUs that we don't know about which 00:10:55.880 --> 00:10:58.650 align:start position:0% the CPUs that we don't know about which in<00:10:56.390> the<00:10:56.540> context<00:10:56.930> of<00:10:56.990> the<00:10:57.200> just<00:10:57.950> shown<00:10:58.130> device 00:10:58.650 --> 00:10:58.660 align:start position:0% in the context of the just shown device 00:10:58.660 --> 00:11:00.850 align:start position:0% in the context of the just shown device this<00:10:59.660> would<00:10:59.870> be<00:10:59.990> eliminated<00:11:00.170> because<00:11:00.530> it's<00:11:00.770> an 00:11:00.850 --> 00:11:00.860 align:start position:0% this would be eliminated because it's an 00:11:00.860 --> 00:11:03.460 align:start position:0% this would be eliminated because it's an old<00:11:01.070> vintage<00:11:01.280> device<00:11:01.730> it's<00:11:02.540> actually<00:11:02.840> I<00:11:03.080> would 00:11:03.460 --> 00:11:03.470 align:start position:0% old vintage device it's actually I would 00:11:03.470 --> 00:11:05.760 align:start position:0% old vintage device it's actually I would say<00:11:03.500> like<00:11:03.680> ten<00:11:03.860> years<00:11:03.980> old<00:11:04.160> or<00:11:04.310> something<00:11:04.640> so 00:11:05.760 --> 00:11:05.770 align:start position:0% say like ten years old or something so 00:11:05.770 --> 00:11:07.960 align:start position:0% say like ten years old or something so there's<00:11:06.770> a<00:11:06.830> few<00:11:06.950> attempts<00:11:07.370> to<00:11:07.490> solve<00:11:07.790> this 00:11:07.960 --> 00:11:07.970 align:start position:0% there's a few attempts to solve this 00:11:07.970 --> 00:11:09.370 align:start position:0% there's a few attempts to solve this problem<00:11:08.150> also<00:11:08.630> from<00:11:08.870> the<00:11:08.960> open<00:11:09.200> hardware 00:11:09.370 --> 00:11:09.380 align:start position:0% problem also from the open hardware 00:11:09.380 --> 00:11:13.990 align:start position:0% problem also from the open hardware movement<00:11:09.530> and<00:11:10.180> SSDs<00:11:11.180> are<00:11:11.600> the<00:11:12.380> best<00:11:12.880> kind<00:11:13.880> of 00:11:13.990 --> 00:11:14.000 align:start position:0% movement and SSDs are the best kind of 00:11:14.000 --> 00:11:16.420 align:start position:0% movement and SSDs are the best kind of place<00:11:14.360> where<00:11:14.600> to<00:11:14.780> put<00:11:14.960> your<00:11:15.080> implant 00:11:16.420 --> 00:11:16.430 align:start position:0% place where to put your implant 00:11:16.430 --> 00:11:17.890 align:start position:0% place where to put your implant in<00:11:16.700> case<00:11:17.060> you<00:11:17.210> want<00:11:17.390> to<00:11:17.420> actually<00:11:17.570> make<00:11:17.750> sure 00:11:17.890 --> 00:11:17.900 align:start position:0% in case you want to actually make sure 00:11:17.900 --> 00:11:19.750 align:start position:0% in case you want to actually make sure that<00:11:18.110> was<00:11:18.410> away<00:11:18.620> someone<00:11:18.980> so<00:11:19.400> this<00:11:19.580> is<00:11:19.670> the 00:11:19.750 --> 00:11:19.760 align:start position:0% that was away someone so this is the 00:11:19.760 --> 00:11:21.640 align:start position:0% that was away someone so this is the open<00:11:20.030> SST<00:11:20.360> project<00:11:20.810> it's<00:11:20.960> a<00:11:21.050> very<00:11:21.200> interesting 00:11:21.640 --> 00:11:21.650 align:start position:0% open SST project it's a very interesting 00:11:21.650 --> 00:11:23.920 align:start position:0% open SST project it's a very interesting project<00:11:22.280> because<00:11:22.310> it<00:11:22.580> also<00:11:22.760> educates<00:11:23.150> people 00:11:23.920 --> 00:11:23.930 align:start position:0% project because it also educates people 00:11:23.930 --> 00:11:25.980 align:start position:0% project because it also educates people on<00:11:24.080> how<00:11:24.290> SSD<00:11:24.830> controllers<00:11:25.280> function<00:11:25.730> and 00:11:25.980 --> 00:11:25.990 align:start position:0% on how SSD controllers function and 00:11:25.990 --> 00:11:32.350 align:start position:0% on how SSD controllers function and there's<00:11:26.990> another<00:11:27.640> newer<00:11:29.020> approach<00:11:30.020> to<00:11:31.360> SSD 00:11:32.350 --> 00:11:32.360 align:start position:0% there's another newer approach to SSD 00:11:32.360 --> 00:11:35.200 align:start position:0% there's another newer approach to SSD and<00:11:32.480> to<00:11:32.660> to<00:11:32.960> other<00:11:33.650> kind<00:11:34.610> of<00:11:34.700> verifiability 00:11:35.200 --> 00:11:35.210 align:start position:0% and to to other kind of verifiability 00:11:35.210 --> 00:11:37.210 align:start position:0% and to to other kind of verifiability parts<00:11:35.720> of<00:11:35.840> hardware<00:11:36.200> which<00:11:36.470> is<00:11:36.650> the<00:11:36.950> chips 00:11:37.210 --> 00:11:37.220 align:start position:0% parts of hardware which is the chips 00:11:37.220 --> 00:11:38.440 align:start position:0% parts of hardware which is the chips alliance<00:11:37.610> it's<00:11:37.730> a<00:11:37.790> common<00:11:38.060> harder<00:11:38.330> for 00:11:38.440 --> 00:11:38.450 align:start position:0% alliance it's a common harder for 00:11:38.450 --> 00:11:41.530 align:start position:0% alliance it's a common harder for interfaces<00:11:38.930> processes<00:11:39.320> and<00:11:39.440> systems<00:11:40.540> to 00:11:41.530 --> 00:11:41.540 align:start position:0% interfaces processes and systems to 00:11:41.540 --> 00:11:43.000 align:start position:0% interfaces processes and systems to interesting<00:11:42.020> projects<00:11:42.890> you<00:11:42.980> should 00:11:43.000 --> 00:11:43.010 align:start position:0% interesting projects you should 00:11:43.010 --> 00:11:46.150 align:start position:0% interesting projects you should definitely<00:11:43.520> take<00:11:43.670> a<00:11:43.730> look<00:11:43.910> look<00:11:44.270> at<00:11:44.800> so<00:11:45.800> I<00:11:45.830> want 00:11:46.150 --> 00:11:46.160 align:start position:0% definitely take a look look at so I want 00:11:46.160 --> 00:11:47.530 align:start position:0% definitely take a look look at so I want to<00:11:46.220> also<00:11:46.370> point<00:11:46.670> yet<00:11:46.940> the<00:11:47.030> common<00:11:47.180> hard<00:11:47.420> are<00:11:47.510> we 00:11:47.530 --> 00:11:47.540 align:start position:0% to also point yet the common hard are we 00:11:47.540 --> 00:11:50.560 align:start position:0% to also point yet the common hard are we using<00:11:47.870> in<00:11:48.110> day<00:11:48.920> to<00:11:48.980> day<00:11:49.100> crypto<00:11:49.550> activities<00:11:50.300> so 00:11:50.560 --> 00:11:50.570 align:start position:0% using in day to day crypto activities so 00:11:50.570 --> 00:11:52.450 align:start position:0% using in day to day crypto activities so in<00:11:51.140> this<00:11:51.230> context<00:11:51.650> I<00:11:51.680> want<00:11:51.860> to<00:11:51.920> also<00:11:52.040> refer<00:11:52.430> to 00:11:52.450 --> 00:11:52.460 align:start position:0% in this context I want to also refer to 00:11:52.460 --> 00:11:54.370 align:start position:0% in this context I want to also refer to a<00:11:52.640> small<00:11:53.060> exhibition<00:11:53.300> archive<00:11:53.900> which<00:11:54.050> is<00:11:54.200> like 00:11:54.370 --> 00:11:54.380 align:start position:0% a small exhibition archive which is like 00:11:54.380 --> 00:11:56.950 align:start position:0% a small exhibition archive which is like traveling<00:11:54.800> around<00:11:55.180> the<00:11:56.180> F<00:11:56.270> con<00:11:56.510> it's<00:11:56.690> called 00:11:56.950 --> 00:11:56.960 align:start position:0% traveling around the F con it's called 00:11:56.960 --> 00:11:59.170 align:start position:0% traveling around the F con it's called materiality<00:11:57.830> of<00:11:57.980> modern<00:11:58.400> cryptography<00:11:58.700> and 00:11:59.170 --> 00:11:59.180 align:start position:0% materiality of modern cryptography and 00:11:59.180 --> 00:12:02.310 align:start position:0% materiality of modern cryptography and it's<00:11:59.660> actually<00:12:00.050> a<00:12:00.860> selection<00:12:01.400> it's<00:12:01.730> a 00:12:02.310 --> 00:12:02.320 align:start position:0% it's actually a selection it's a 00:12:02.320 --> 00:12:04.380 align:start position:0% it's actually a selection it's a hardware<00:12:03.320> archive<00:12:03.680> that<00:12:03.710> we<00:12:03.980> are<00:12:04.070> collecting 00:12:04.380 --> 00:12:04.390 align:start position:0% hardware archive that we are collecting 00:12:04.390 --> 00:12:06.940 align:start position:0% hardware archive that we are collecting since<00:12:05.390> approximately<00:12:06.020> 10<00:12:06.200> years<00:12:06.470> which<00:12:06.680> are 00:12:06.940 --> 00:12:06.950 align:start position:0% since approximately 10 years which are 00:12:06.950 --> 00:12:08.260 align:start position:0% since approximately 10 years which are features<00:12:07.430> like<00:12:07.580> different<00:12:07.940> prototypes 00:12:08.260 --> 00:12:08.270 align:start position:0% features like different prototypes 00:12:08.270 --> 00:12:11.050 align:start position:0% features like different prototypes different<00:12:09.130> non<00:12:10.130> release<00:12:10.460> prototypes 00:12:11.050 --> 00:12:11.060 align:start position:0% different non release prototypes 00:12:11.060 --> 00:12:13.300 align:start position:0% different non release prototypes materiality<00:12:11.690> is<00:12:11.960> but<00:12:12.200> also<00:12:12.320> like<00:12:12.530> this<00:12:12.980> kind 00:12:13.300 --> 00:12:13.310 align:start position:0% materiality is but also like this kind 00:12:13.310 --> 00:12:17.560 align:start position:0% materiality is but also like this kind of<00:12:13.460> modified<00:12:15.160> it's<00:12:16.160> modified<00:12:16.490> dices<00:12:17.300> that<00:12:17.480> you 00:12:17.560 --> 00:12:17.570 align:start position:0% of modified it's modified dices that you 00:12:17.570 --> 00:12:22.750 align:start position:0% of modified it's modified dices that you see<00:12:17.750> in<00:12:17.810> the<00:12:17.930> right<00:12:18.410> top<00:12:18.670> which<00:12:19.670> are<00:12:19.880> all<00:12:21.760> kind 00:12:22.750 --> 00:12:22.760 align:start position:0% see in the right top which are all kind 00:12:22.760 --> 00:12:24.160 align:start position:0% see in the right top which are all kind of<00:12:22.880> explaining<00:12:23.330> different<00:12:23.510> security 00:12:24.160 --> 00:12:24.170 align:start position:0% of explaining different security 00:12:24.170 --> 00:12:26.200 align:start position:0% of explaining different security concepts<00:12:24.650> and<00:12:24.770> how<00:12:24.800> we<00:12:24.950> are<00:12:25.190> in<00:12:25.310> a<00:12:25.340> way<00:12:25.550> because 00:12:26.200 --> 00:12:26.210 align:start position:0% concepts and how we are in a way because 00:12:26.210 --> 00:12:28.150 align:start position:0% concepts and how we are in a way because we<00:12:26.300> don't<00:12:26.450> trust<00:12:26.600> Hardware<00:12:27.140> again<00:12:27.590> falling 00:12:28.150 --> 00:12:28.160 align:start position:0% we don't trust Hardware again falling 00:12:28.160 --> 00:12:30.640 align:start position:0% we don't trust Hardware again falling back<00:12:28.310> to<00:12:28.460> this<00:12:28.550> kind<00:12:28.790> of<00:12:28.940> age<00:12:29.840> before<00:12:30.110> micro 00:12:30.640 --> 00:12:30.650 align:start position:0% back to this kind of age before micro 00:12:30.650 --> 00:12:33.400 align:start position:0% back to this kind of age before micro computing<00:12:31.190> so<00:12:31.640> I'm<00:12:31.970> strongly<00:12:32.900> suggesting<00:12:33.350> you 00:12:33.400 --> 00:12:33.410 align:start position:0% computing so I'm strongly suggesting you 00:12:33.410 --> 00:12:34.870 align:start position:0% computing so I'm strongly suggesting you take<00:12:33.590> a<00:12:33.620> look<00:12:33.770> at<00:12:33.920> this<00:12:34.040> also<00:12:34.280> this<00:12:34.430> is<00:12:34.580> part<00:12:34.790> of 00:12:34.870 --> 00:12:34.880 align:start position:0% take a look at this also this is part of 00:12:34.880 --> 00:12:36.400 align:start position:0% take a look at this also this is part of the<00:12:35.000> open<00:12:35.210> hardware<00:12:35.360> dialog<00:12:35.870> so<00:12:36.020> we're<00:12:36.170> trying 00:12:36.400 --> 00:12:36.410 align:start position:0% the open hardware dialog so we're trying 00:12:36.410 --> 00:12:40.840 align:start position:0% the open hardware dialog so we're trying to<00:12:36.560> figure<00:12:37.220> out<00:12:37.340> and<00:12:38.200> how<00:12:39.200> can<00:12:39.950> we<00:12:40.070> explain<00:12:40.430> and 00:12:40.840 --> 00:12:40.850 align:start position:0% to figure out and how can we explain and 00:12:40.850 --> 00:12:43.360 align:start position:0% to figure out and how can we explain and educate<00:12:40.970> more<00:12:41.450> about<00:12:41.690> hardware<00:12:42.190> so<00:12:43.190> but 00:12:43.360 --> 00:12:43.370 align:start position:0% educate more about hardware so but 00:12:43.370 --> 00:12:44.770 align:start position:0% educate more about hardware so but coming<00:12:43.610> back<00:12:43.640> to<00:12:43.790> this<00:12:44.000> kind<00:12:44.510> of<00:12:44.600> day-to-day 00:12:44.770 --> 00:12:44.780 align:start position:0% coming back to this kind of day-to-day 00:12:44.780 --> 00:12:47.800 align:start position:0% coming back to this kind of day-to-day crypto<00:12:45.770> hardware<00:12:46.100> so<00:12:46.250> of<00:12:46.730> course<00:12:47.030> a<00:12:47.300> lot<00:12:47.720> of 00:12:47.800 --> 00:12:47.810 align:start position:0% crypto hardware so of course a lot of 00:12:47.810 --> 00:12:50.830 align:start position:0% crypto hardware so of course a lot of people<00:12:48.050> know<00:12:48.170> crypto<00:12:48.910> other<00:12:49.910> wallets<00:12:50.330> a<00:12:50.540> lot 00:12:50.830 --> 00:12:50.840 align:start position:0% people know crypto other wallets a lot 00:12:50.840 --> 00:12:52.510 align:start position:0% people know crypto other wallets a lot of<00:12:50.900> people<00:12:51.080> use<00:12:51.200> Hardware<00:12:51.620> wallets<00:12:51.950> these<00:12:52.370> are 00:12:52.510 --> 00:12:52.520 align:start position:0% of people use Hardware wallets these are 00:12:52.520 --> 00:12:54.520 align:start position:0% of people use Hardware wallets these are trium<00:12:53.000> quite<00:12:53.480> common<00:12:53.840> other<00:12:54.050> while<00:12:54.260> it's<00:12:54.380> out 00:12:54.520 --> 00:12:54.530 align:start position:0% trium quite common other while it's out 00:12:54.530 --> 00:12:55.750 align:start position:0% trium quite common other while it's out there<00:12:54.680> with<00:12:54.830> a<00:12:54.890> very<00:12:54.920> different<00:12:55.520> concept 00:12:55.750 --> 00:12:55.760 align:start position:0% there with a very different concept 00:12:55.760 --> 00:12:57.250 align:start position:0% there with a very different concept behind<00:12:56.120> them<00:12:56.450> also<00:12:56.720> from<00:12:56.930> a<00:12:56.990> harder 00:12:57.250 --> 00:12:57.260 align:start position:0% behind them also from a harder 00:12:57.260 --> 00:12:58.660 align:start position:0% behind them also from a harder perspective<00:12:57.770> so<00:12:57.920> we<00:12:57.950> have<00:12:58.130> on<00:12:58.250> the<00:12:58.310> left<00:12:58.490> side 00:12:58.660 --> 00:12:58.670 align:start position:0% perspective so we have on the left side 00:12:58.670 --> 00:13:00.430 align:start position:0% perspective so we have on the left side the<00:12:58.820> tracer<00:12:59.090> which<00:12:59.750> is<00:12:59.870> an<00:12:59.960> open<00:13:00.260> source 00:13:00.430 --> 00:13:00.440 align:start position:0% the tracer which is an open source 00:13:00.440 --> 00:13:02.530 align:start position:0% the tracer which is an open source hardware<00:13:00.710> which<00:13:01.070> means<00:13:01.310> it's<00:13:01.460> verifiable<00:13:01.910> but 00:13:02.530 --> 00:13:02.540 align:start position:0% hardware which means it's verifiable but 00:13:02.540 --> 00:13:03.790 align:start position:0% hardware which means it's verifiable but here<00:13:02.750> you<00:13:02.840> also<00:13:02.990> see<00:13:03.320> that<00:13:03.440> it's<00:13:03.590> very 00:13:03.790 --> 00:13:03.800 align:start position:0% here you also see that it's very 00:13:03.800 --> 00:13:05.920 align:start position:0% here you also see that it's very interesting<00:13:04.100> because<00:13:04.400> while<00:13:05.060> we<00:13:05.630> have<00:13:05.750> the 00:13:05.920 --> 00:13:05.930 align:start position:0% interesting because while we have the 00:13:05.930 --> 00:13:08.220 align:start position:0% interesting because while we have the specifications<00:13:06.590> and<00:13:06.740> everything<00:13:07.100> available 00:13:08.220 --> 00:13:08.230 align:start position:0% specifications and everything available 00:13:08.230 --> 00:13:10.660 align:start position:0% specifications and everything available parts<00:13:09.230> or<00:13:09.440> the<00:13:09.470> components<00:13:10.160> of<00:13:10.310> the<00:13:10.400> open 00:13:10.660 --> 00:13:10.670 align:start position:0% parts or the components of the open 00:13:10.670 --> 00:13:12.520 align:start position:0% parts or the components of the open hardware<00:13:10.910> are<00:13:11.180> not<00:13:11.480> verifiable<00:13:12.230> at<00:13:12.440> all 00:13:12.520 --> 00:13:12.530 align:start position:0% hardware are not verifiable at all 00:13:12.530 --> 00:13:14.320 align:start position:0% hardware are not verifiable at all because<00:13:12.770> if<00:13:12.890> the<00:13:12.980> trust<00:13:13.270> producer<00:13:14.270> the 00:13:14.320 --> 00:13:14.330 align:start position:0% because if the trust producer the 00:13:14.330 --> 00:13:16.870 align:start position:0% because if the trust producer the manufacturer<00:13:14.810> that<00:13:14.990> this<00:13:15.170> that<00:13:15.500> is<00:13:15.710> that<00:13:16.280> the 00:13:16.870 --> 00:13:16.880 align:start position:0% manufacturer that this that is that the 00:13:16.880 --> 00:13:18.880 align:start position:0% manufacturer that this that is that the components<00:13:17.330> are<00:13:17.360> compromised<00:13:17.990> so<00:13:18.230> we<00:13:18.710> can 00:13:18.880 --> 00:13:18.890 align:start position:0% components are compromised so we can 00:13:18.890 --> 00:13:20.800 align:start position:0% components are compromised so we can verify<00:13:19.100> the<00:13:19.430> treasure<00:13:19.820> the<00:13:20.270> most<00:13:20.540> we<00:13:20.720> can 00:13:20.800 --> 00:13:20.810 align:start position:0% verify the treasure the most we can 00:13:20.810 --> 00:13:24.130 align:start position:0% verify the treasure the most we can verify<00:13:21.020> a<00:13:21.530> hardware<00:13:22.430> wallet<00:13:23.030> out<00:13:23.210> there<00:13:23.450> but 00:13:24.130 --> 00:13:24.140 align:start position:0% verify a hardware wallet out there but 00:13:24.140 --> 00:13:25.450 align:start position:0% verify a hardware wallet out there but that<00:13:24.680> doesn't<00:13:24.950> mean<00:13:25.040> it's<00:13:25.160> the<00:13:25.220> cure 00:13:25.450 --> 00:13:25.460 align:start position:0% that doesn't mean it's the cure 00:13:25.460 --> 00:13:26.770 align:start position:0% that doesn't mean it's the cure necessarily<00:13:26.060> so<00:13:26.210> you<00:13:26.270> have<00:13:26.390> to<00:13:26.510> make<00:13:26.660> sure 00:13:26.770 --> 00:13:26.780 align:start position:0% necessarily so you have to make sure 00:13:26.780 --> 00:13:28.900 align:start position:0% necessarily so you have to make sure that<00:13:26.930> you<00:13:27.020> secure<00:13:27.470> it<00:13:27.560> yourself<00:13:27.950> on<00:13:28.130> in<00:13:28.790> the 00:13:28.900 --> 00:13:28.910 align:start position:0% that you secure it yourself on in the 00:13:28.910 --> 00:13:29.769 align:start position:0% that you secure it yourself on in the middle<00:13:29.120> you<00:13:29.180> see<00:13:29.210> the<00:13:29.360> bit 00:13:29.769 --> 00:13:29.779 align:start position:0% middle you see the bit 00:13:29.779 --> 00:13:32.590 align:start position:0% middle you see the bit some<00:13:30.220> kind<00:13:31.220> of<00:13:31.310> a<00:13:31.339> different<00:13:31.639> concept<00:13:32.209> it's 00:13:32.590 --> 00:13:32.600 align:start position:0% some kind of a different concept it's 00:13:32.600 --> 00:13:33.879 align:start position:0% some kind of a different concept it's partly<00:13:32.930> open<00:13:33.290> which<00:13:33.439> means<00:13:33.649> it<00:13:33.740> runs 00:13:33.879 --> 00:13:33.889 align:start position:0% partly open which means it runs 00:13:33.889 --> 00:13:35.650 align:start position:0% partly open which means it runs open-source<00:13:34.430> software<00:13:34.639> but<00:13:35.329> uses<00:13:35.629> the 00:13:35.650 --> 00:13:35.660 align:start position:0% open-source software but uses the 00:13:35.660 --> 00:13:37.119 align:start position:0% open-source software but uses the hardware<00:13:36.050> security<00:13:36.170> module<00:13:36.769> so<00:13:36.889> you<00:13:36.949> have<00:13:37.040> to 00:13:37.119 --> 00:13:37.129 align:start position:0% hardware security module so you have to 00:13:37.129 --> 00:13:38.530 align:start position:0% hardware security module so you have to trust<00:13:37.370> the<00:13:37.730> manufacturer<00:13:38.209> of<00:13:38.240> the<00:13:38.329> harbor 00:13:38.530 --> 00:13:38.540 align:start position:0% trust the manufacturer of the harbor 00:13:38.540 --> 00:13:40.929 align:start position:0% trust the manufacturer of the harbor security<00:13:38.930> model<00:13:39.170> a<00:13:39.379> module<00:13:39.949> that<00:13:39.980> it<00:13:40.730> is<00:13:40.819> not 00:13:40.929 --> 00:13:40.939 align:start position:0% security model a module that it is not 00:13:40.939 --> 00:13:42.910 align:start position:0% security model a module that it is not compromised<00:13:41.449> and<00:13:42.350> then<00:13:42.470> we<00:13:42.560> have<00:13:42.680> the<00:13:42.740> ledger 00:13:42.910 --> 00:13:42.920 align:start position:0% compromised and then we have the ledger 00:13:42.920 --> 00:13:44.230 align:start position:0% compromised and then we have the ledger on<00:13:43.310> the<00:13:43.399> right-hand<00:13:43.759> side<00:13:43.819> which<00:13:44.089> is 00:13:44.230 --> 00:13:44.240 align:start position:0% on the right-hand side which is 00:13:44.240 --> 00:13:46.720 align:start position:0% on the right-hand side which is completely<00:13:44.600> closed<00:13:45.199> source<00:13:45.439> so<00:13:45.860> here<00:13:46.040> just<00:13:46.639> an 00:13:46.720 --> 00:13:46.730 align:start position:0% completely closed source so here just an 00:13:46.730 --> 00:13:49.900 align:start position:0% completely closed source so here just an example<00:13:46.999> if<00:13:47.209> your<00:13:47.740> kind<00:13:48.740> of<00:13:48.889> the<00:13:49.069> verifying 00:13:49.900 --> 00:13:49.910 align:start position:0% example if your kind of the verifying 00:13:49.910 --> 00:13:52.119 align:start position:0% example if your kind of the verifying type<00:13:50.180> you<00:13:50.689> would<00:13:50.839> actually<00:13:51.379> be<00:13:51.559> able<00:13:51.709> to 00:13:52.119 --> 00:13:52.129 align:start position:0% type you would actually be able to 00:13:52.129 --> 00:13:53.769 align:start position:0% type you would actually be able to create<00:13:52.399> your<00:13:52.550> own<00:13:52.610> treasure<00:13:52.970> hardware<00:13:53.600> and 00:13:53.769 --> 00:13:53.779 align:start position:0% create your own treasure hardware and 00:13:53.779 --> 00:13:55.960 align:start position:0% create your own treasure hardware and then<00:13:53.959> load<00:13:54.499> the<00:13:54.649> firmware<00:13:54.860> on<00:13:55.069> it<00:13:55.249> and<00:13:55.430> run<00:13:55.850> the 00:13:55.960 --> 00:13:55.970 align:start position:0% then load the firmware on it and run the 00:13:55.970 --> 00:13:56.759 align:start position:0% then load the firmware on it and run the firmware 00:13:56.759 --> 00:13:56.769 align:start position:0% firmware 00:13:56.769 --> 00:13:59.439 align:start position:0% firmware here's<00:13:57.769> an<00:13:57.860> example<00:13:58.100> of<00:13:58.519> a<00:13:58.670> hardware<00:13:59.300> based 00:13:59.439 --> 00:13:59.449 align:start position:0% here's an example of a hardware based 00:13:59.449 --> 00:14:00.910 align:start position:0% here's an example of a hardware based project<00:13:59.839> that<00:13:59.959> there<00:14:00.410> was<00:14:00.499> a<00:14:00.529> talk<00:14:00.769> yesterday 00:14:00.910 --> 00:14:00.920 align:start position:0% project that there was a talk yesterday 00:14:00.920 --> 00:14:04.150 align:start position:0% project that there was a talk yesterday I<00:14:01.399> guess<00:14:01.720> the<00:14:02.720> status<00:14:03.170> key<00:14:03.379> card<00:14:03.649> which<00:14:03.980> is<00:14:04.129> a 00:14:04.150 --> 00:14:04.160 align:start position:0% I guess the status key card which is a 00:14:04.160 --> 00:14:06.759 align:start position:0% I guess the status key card which is a Java<00:14:04.490> card<00:14:04.759> based<00:14:04.999> how<00:14:05.629> the<00:14:05.689> solution<00:14:06.230> which 00:14:06.759 --> 00:14:06.769 align:start position:0% Java card based how the solution which 00:14:06.769 --> 00:14:08.199 align:start position:0% Java card based how the solution which is<00:14:06.980> basically<00:14:07.249> an<00:14:07.370> open<00:14:07.459> platform<00:14:07.730> develop 00:14:08.199 --> 00:14:08.209 align:start position:0% is basically an open platform develop 00:14:08.209 --> 00:14:10.150 align:start position:0% is basically an open platform develop your<00:14:08.360> own<00:14:08.420> workflows<00:14:08.930> it<00:14:09.410> might<00:14:09.559> be<00:14:09.709> also<00:14:09.949> an 00:14:10.150 --> 00:14:10.160 align:start position:0% your own workflows it might be also an 00:14:10.160 --> 00:14:12.519 align:start position:0% your own workflows it might be also an interesting<00:14:10.370> aspect<00:14:11.240> but<00:14:11.839> it's<00:14:12.019> it's<00:14:12.319> also 00:14:12.519 --> 00:14:12.529 align:start position:0% interesting aspect but it's it's also 00:14:12.529 --> 00:14:15.009 align:start position:0% interesting aspect but it's it's also closed<00:14:12.920> its<00:14:13.129> Java<00:14:13.339> card<00:14:13.579> it's<00:14:13.699> oracle<00:14:14.089> so 00:14:15.009 --> 00:14:15.019 align:start position:0% closed its Java card it's oracle so 00:14:15.019 --> 00:14:18.009 align:start position:0% closed its Java card it's oracle so another<00:14:15.350> element<00:14:16.040> you<00:14:16.670> came<00:14:16.910> across<00:14:17.420> possibly 00:14:18.009 --> 00:14:18.019 align:start position:0% another element you came across possibly 00:14:18.019 --> 00:14:20.049 align:start position:0% another element you came across possibly is<00:14:18.350> having<00:14:18.740> a<00:14:18.829> random<00:14:19.189> number<00:14:19.519> generators 00:14:20.049 --> 00:14:20.059 align:start position:0% is having a random number generators 00:14:20.059 --> 00:14:22.420 align:start position:0% is having a random number generators there's<00:14:20.389> a<00:14:20.480> lot<00:14:20.629> of<00:14:20.749> time<00:14:20.930> but<00:14:21.050> I<00:14:21.139> made<00:14:21.319> a<00:14:21.860> few 00:14:22.420 --> 00:14:22.430 align:start position:0% there's a lot of time but I made a few 00:14:22.430 --> 00:14:24.699 align:start position:0% there's a lot of time but I made a few screenshots<00:14:23.269> here<00:14:23.540> of<00:14:23.689> nice<00:14:24.019> ones<00:14:24.290> is<00:14:24.499> the 00:14:24.699 --> 00:14:24.709 align:start position:0% screenshots here of nice ones is the 00:14:24.709 --> 00:14:26.019 align:start position:0% screenshots here of nice ones is the tiffer<00:14:25.129> it<00:14:25.339> might<00:14:25.519> have<00:14:25.610> been<00:14:25.730> a<00:14:25.819> really 00:14:26.019 --> 00:14:26.029 align:start position:0% tiffer it might have been a really 00:14:26.029 --> 00:14:28.449 align:start position:0% tiffer it might have been a really beautiful<00:14:26.499> crafted<00:14:27.499> device<00:14:27.769> and<00:14:28.009> here's<00:14:28.220> the 00:14:28.449 --> 00:14:28.459 align:start position:0% beautiful crafted device and here's the 00:14:28.459 --> 00:14:31.210 align:start position:0% beautiful crafted device and here's the artist<00:14:29.240> made<00:14:29.389> from<00:14:29.600> a<00:14:29.779> more<00:14:30.319> Libre<00:14:30.709> device<00:14:31.009> so 00:14:31.210 --> 00:14:31.220 align:start position:0% artist made from a more Libre device so 00:14:31.220 --> 00:14:34.600 align:start position:0% artist made from a more Libre device so this<00:14:31.339> also<00:14:31.579> is<00:14:32.480> these<00:14:33.470> are<00:14:33.680> common<00:14:34.009> devices<00:14:34.279> to 00:14:34.600 --> 00:14:34.610 align:start position:0% this also is these are common devices to 00:14:34.610 --> 00:14:36.579 align:start position:0% this also is these are common devices to generate<00:14:34.639> entropy<00:14:35.509> and<00:14:35.689> randomness<00:14:36.050> in<00:14:36.350> order 00:14:36.579 --> 00:14:36.589 align:start position:0% generate entropy and randomness in order 00:14:36.589 --> 00:14:39.490 align:start position:0% generate entropy and randomness in order for<00:14:36.740> you<00:14:36.800> to<00:14:36.829> create<00:14:37.329> unsafe<00:14:38.329> keys<00:14:38.689> of<00:14:39.170> course 00:14:39.490 --> 00:14:39.500 align:start position:0% for you to create unsafe keys of course 00:14:39.500 --> 00:14:40.960 align:start position:0% for you to create unsafe keys of course there's<00:14:39.740> also<00:14:39.889> hardware<00:14:40.339> tokens<00:14:40.699> and<00:14:40.819> there's 00:14:40.960 --> 00:14:40.970 align:start position:0% there's also hardware tokens and there's 00:14:40.970 --> 00:14:42.400 align:start position:0% there's also hardware tokens and there's a<00:14:41.029> lot<00:14:41.209> of<00:14:41.300> them<00:14:41.449> because<00:14:41.689> they<00:14:41.779> exist<00:14:41.899> since<00:14:42.259> a 00:14:42.400 --> 00:14:42.410 align:start position:0% a lot of them because they exist since a 00:14:42.410 --> 00:14:44.499 align:start position:0% a lot of them because they exist since a long<00:14:42.559> time<00:14:42.620> I<00:14:43.100> just<00:14:43.430> made<00:14:44.029> a<00:14:44.059> few<00:14:44.209> screenshots 00:14:44.499 --> 00:14:44.509 align:start position:0% long time I just made a few screenshots 00:14:44.509 --> 00:14:46.629 align:start position:0% long time I just made a few screenshots of<00:14:44.689> a<00:14:44.779> few<00:14:44.990> of<00:14:45.079> them<00:14:45.259> and<00:14:45.470> these<00:14:46.339> are<00:14:46.490> very 00:14:46.629 --> 00:14:46.639 align:start position:0% of a few of them and these are very 00:14:46.639 --> 00:14:48.460 align:start position:0% of a few of them and these are very common<00:14:46.970> devices<00:14:47.209> to<00:14:47.420> identify<00:14:47.899> yourself<00:14:48.019> and 00:14:48.460 --> 00:14:48.470 align:start position:0% common devices to identify yourself and 00:14:48.470 --> 00:14:51.670 align:start position:0% common devices to identify yourself and to<00:14:48.559> do<00:14:49.160> all<00:14:49.339> sorts<00:14:49.699> of<00:14:49.730> security<00:14:50.680> protocols 00:14:51.670 --> 00:14:51.680 align:start position:0% to do all sorts of security protocols 00:14:51.680 --> 00:14:54.389 align:start position:0% to do all sorts of security protocols and<00:14:51.949> workflows<00:14:52.610> and<00:14:52.910> there<00:14:53.420> is<00:14:53.540> even<00:14:53.870> more 00:14:54.389 --> 00:14:54.399 align:start position:0% and workflows and there is even more 00:14:54.399 --> 00:14:57.879 align:start position:0% and workflows and there is even more open<00:14:55.480> elements<00:14:56.480> than<00:14:57.350> the<00:14:57.439> ones<00:14:57.620> that<00:14:57.740> I<00:14:57.800> was 00:14:57.879 --> 00:14:57.889 align:start position:0% open elements than the ones that I was 00:14:57.889 --> 00:14:59.379 align:start position:0% open elements than the ones that I was showing<00:14:58.129> here<00:14:58.459> is<00:14:58.519> for<00:14:58.639> example<00:14:58.970> the<00:14:59.029> solo 00:14:59.379 --> 00:14:59.389 align:start position:0% showing here is for example the solo 00:14:59.389 --> 00:15:02.049 align:start position:0% showing here is for example the solo dolo<00:15:00.110> and<00:15:00.470> form<00:15:00.709> or<00:15:00.889> a<00:15:01.040> series<00:15:01.459> which<00:15:01.639> is<00:15:01.670> which 00:15:02.049 --> 00:15:02.059 align:start position:0% dolo and form or a series which is which 00:15:02.059 --> 00:15:04.210 align:start position:0% dolo and form or a series which is which started<00:15:02.389> as<00:15:02.480> a<00:15:02.509> kind<00:15:02.689> of<00:15:02.779> an<00:15:02.899> open<00:15:03.050> open<00:15:03.980> source 00:15:04.210 --> 00:15:04.220 align:start position:0% started as a kind of an open open source 00:15:04.220 --> 00:15:08.230 align:start position:0% started as a kind of an open open source project<00:15:05.000> it's<00:15:05.509> also<00:15:06.759> certified<00:15:07.759> by<00:15:08.180> the 00:15:08.230 --> 00:15:08.240 align:start position:0% project it's also certified by the 00:15:08.240 --> 00:15:10.600 align:start position:0% project it's also certified by the ashram<00:15:08.689> and<00:15:09.620> this<00:15:10.100> is<00:15:10.220> also<00:15:10.370> an<00:15:10.519> interesting 00:15:10.600 --> 00:15:10.610 align:start position:0% ashram and this is also an interesting 00:15:10.610 --> 00:15:13.480 align:start position:0% ashram and this is also an interesting hardware<00:15:11.300> this<00:15:11.629> is<00:15:11.750> the<00:15:11.839> neutral<00:15:12.019> key<00:15:12.490> it's 00:15:13.480 --> 00:15:13.490 align:start position:0% hardware this is the neutral key it's 00:15:13.490 --> 00:15:15.549 align:start position:0% hardware this is the neutral key it's kind<00:15:13.819> of<00:15:13.850> a<00:15:13.939> multi-purpose<00:15:14.420> or<00:15:14.929> cryptography 00:15:15.549 --> 00:15:15.559 align:start position:0% kind of a multi-purpose or cryptography 00:15:15.559 --> 00:15:17.530 align:start position:0% kind of a multi-purpose or cryptography hardware<00:15:15.920> you<00:15:16.519> might<00:15:16.699> have<00:15:16.879> come<00:15:17.029> across<00:15:17.059> this 00:15:17.530 --> 00:15:17.540 align:start position:0% hardware you might have come across this 00:15:17.540 --> 00:15:19.569 align:start position:0% hardware you might have come across this because<00:15:17.809> purism<00:15:18.199> delivers<00:15:19.129> this<00:15:19.309> with<00:15:19.459> the 00:15:19.569 --> 00:15:19.579 align:start position:0% because purism delivers this with the 00:15:19.579 --> 00:15:21.519 align:start position:0% because purism delivers this with the purism<00:15:19.910> laptops<00:15:20.420> in<00:15:20.809> order<00:15:21.050> to<00:15:21.139> verify<00:15:21.259> that 00:15:21.519 --> 00:15:21.529 align:start position:0% purism laptops in order to verify that 00:15:21.529 --> 00:15:22.900 align:start position:0% purism laptops in order to verify that your<00:15:21.920> supply<00:15:22.339> chain<00:15:22.370> hasn't<00:15:22.699> been 00:15:22.900 --> 00:15:22.910 align:start position:0% your supply chain hasn't been 00:15:22.910 --> 00:15:25.150 align:start position:0% your supply chain hasn't been compromised<00:15:23.449> so<00:15:23.600> sending<00:15:23.959> you<00:15:24.079> this<00:15:24.230> device 00:15:25.150 --> 00:15:25.160 align:start position:0% compromised so sending you this device 00:15:25.160 --> 00:15:26.470 align:start position:0% compromised so sending you this device on<00:15:25.309> the<00:15:25.370> left-hand<00:15:25.730> side<00:15:25.790> in<00:15:26.029> a<00:15:26.120> different 00:15:26.470 --> 00:15:26.480 align:start position:0% on the left-hand side in a different 00:15:26.480 --> 00:15:27.910 align:start position:0% on the left-hand side in a different parcels<00:15:26.689> so<00:15:26.990> you<00:15:27.079> can<00:15:27.230> actually<00:15:27.439> check<00:15:27.589> ok<00:15:27.860> is 00:15:27.910 --> 00:15:27.920 align:start position:0% parcels so you can actually check ok is 00:15:27.920 --> 00:15:32.079 align:start position:0% parcels so you can actually check ok is my<00:15:28.100> buyers<00:15:28.309> compromised<00:15:28.939> or<00:15:29.120> not<00:15:30.069> so<00:15:31.069> all<00:15:31.879> the 00:15:32.079 --> 00:15:32.089 align:start position:0% my buyers compromised or not so all the 00:15:32.089 --> 00:15:33.970 align:start position:0% my buyers compromised or not so all the things<00:15:32.209> I've<00:15:32.420> shown<00:15:32.449> you<00:15:32.839> are<00:15:33.499> not<00:15:33.740> really 00:15:33.970 --> 00:15:33.980 align:start position:0% things I've shown you are not really 00:15:33.980 --> 00:15:36.730 align:start position:0% things I've shown you are not really verifiable<00:15:34.699> or<00:15:34.850> at<00:15:35.300> least<00:15:35.540> only<00:15:35.899> verifiable 00:15:36.730 --> 00:15:36.740 align:start position:0% verifiable or at least only verifiable 00:15:36.740 --> 00:15:38.379 align:start position:0% verifiable or at least only verifiable to<00:15:36.860> some<00:15:37.009> point<00:15:37.279> and<00:15:37.579> we're<00:15:37.850> using<00:15:38.029> them<00:15:38.240> on<00:15:38.329> a 00:15:38.379 --> 00:15:38.389 align:start position:0% to some point and we're using them on a 00:15:38.389 --> 00:15:41.439 align:start position:0% to some point and we're using them on a daily<00:15:38.629> basis<00:15:39.019> so<00:15:39.370> what<00:15:40.370> can<00:15:40.790> we<00:15:40.850> do<00:15:41.029> about<00:15:41.149> that 00:15:41.439 --> 00:15:41.449 align:start position:0% daily basis so what can we do about that 00:15:41.449 --> 00:15:43.540 align:start position:0% daily basis so what can we do about that I<00:15:41.689> want<00:15:42.439> to<00:15:42.500> briefly<00:15:42.620> also<00:15:42.889> go<00:15:43.100> into<00:15:43.220> the 00:15:43.540 --> 00:15:43.550 align:start position:0% I want to briefly also go into the 00:15:43.550 --> 00:15:45.430 align:start position:0% I want to briefly also go into the models<00:15:44.240> I<00:15:44.330> was<00:15:44.450> referring<00:15:44.750> to<00:15:44.900> there<00:15:45.200> are 00:15:45.430 --> 00:15:45.440 align:start position:0% models I was referring to there are 00:15:45.440 --> 00:15:47.530 align:start position:0% models I was referring to there are parts<00:15:46.070> of<00:15:46.190> all<00:15:46.460> these<00:15:46.640> kind<00:15:46.880> of<00:15:46.940> devices<00:15:47.120> or 00:15:47.530 --> 00:15:47.540 align:start position:0% parts of all these kind of devices or 00:15:47.540 --> 00:15:50.260 align:start position:0% parts of all these kind of devices or partly<00:15:48.490> parts<00:15:49.490> of<00:15:49.580> these<00:15:49.730> devices<00:15:49.970> I<00:15:50.150> was 00:15:50.260 --> 00:15:50.270 align:start position:0% partly parts of these devices I was 00:15:50.270 --> 00:15:51.790 align:start position:0% partly parts of these devices I was showing<00:15:50.480> which<00:15:50.960> are<00:15:51.110> having<00:15:51.290> security 00:15:51.790 --> 00:15:51.800 align:start position:0% showing which are having security 00:15:51.800 --> 00:15:53.920 align:start position:0% showing which are having security modules<00:15:52.160> to<00:15:52.760> briefly<00:15:53.090> explain<00:15:53.330> what<00:15:53.540> they<00:15:53.900> are 00:15:53.920 --> 00:15:53.930 align:start position:0% modules to briefly explain what they are 00:15:53.930 --> 00:15:56.440 align:start position:0% modules to briefly explain what they are so<00:15:54.470> there<00:15:54.620> are<00:15:54.710> physical<00:15:54.920> physical<00:15:55.580> computing 00:15:56.440 --> 00:15:56.450 align:start position:0% so there are physical physical computing 00:15:56.450 --> 00:15:58.270 align:start position:0% so there are physical physical computing device<00:15:56.770> safeguarding<00:15:57.770> and<00:15:57.800> managing<00:15:58.130> digital 00:15:58.270 --> 00:15:58.280 align:start position:0% device safeguarding and managing digital 00:15:58.280 --> 00:16:01.660 align:start position:0% device safeguarding and managing digital keys<00:15:58.990> so<00:15:59.990> we<00:16:00.890> need<00:16:01.070> them<00:16:01.190> for<00:16:01.310> strong<00:16:01.520> it 00:16:01.660 --> 00:16:01.670 align:start position:0% keys so we need them for strong it 00:16:01.670 --> 00:16:03.580 align:start position:0% keys so we need them for strong it authentication<00:16:02.330> crypto<00:16:02.630> processing<00:16:03.140> they 00:16:03.580 --> 00:16:03.590 align:start position:0% authentication crypto processing they 00:16:03.590 --> 00:16:05.470 align:start position:0% authentication crypto processing they usually<00:16:03.890> in<00:16:03.950> a<00:16:04.010> hardware<00:16:04.310> wallet<00:16:04.610> such<00:16:05.270> as<00:16:05.390> the 00:16:05.470 --> 00:16:05.480 align:start position:0% usually in a hardware wallet such as the 00:16:05.480 --> 00:16:06.970 align:start position:0% usually in a hardware wallet such as the legend<00:16:05.840> bit<00:16:05.990> box<00:16:06.260> but<00:16:06.560> they're<00:16:06.710> also<00:16:06.830> in<00:16:06.950> the 00:16:06.970 --> 00:16:06.980 align:start position:0% legend bit box but they're also in the 00:16:06.980 --> 00:16:09.460 align:start position:0% legend bit box but they're also in the Java<00:16:07.190> card<00:16:07.520> status<00:16:08.330> key<00:16:08.630> card<00:16:08.870> we<00:16:09.140> see<00:16:09.290> them<00:16:09.410> in 00:16:09.460 --> 00:16:09.470 align:start position:0% Java card status key card we see them in 00:16:09.470 --> 00:16:11.770 align:start position:0% Java card status key card we see them in the<00:16:09.530> neutral<00:16:09.890> key<00:16:10.070> in<00:16:10.400> mobile<00:16:11.090> phones<00:16:11.270> and<00:16:11.480> RT 00:16:11.770 --> 00:16:11.780 align:start position:0% the neutral key in mobile phones and RT 00:16:11.780 --> 00:16:14.020 align:start position:0% the neutral key in mobile phones and RT devices<00:16:12.340> and<00:16:13.340> then<00:16:13.460> on<00:16:13.550> the<00:16:13.640> other<00:16:13.760> hand<00:16:13.940> we 00:16:14.020 --> 00:16:14.030 align:start position:0% devices and then on the other hand we 00:16:14.030 --> 00:16:15.990 align:start position:0% devices and then on the other hand we have<00:16:14.120> trusted<00:16:14.420> execution<00:16:14.630> environments 00:16:15.990 --> 00:16:16.000 align:start position:0% have trusted execution environments 00:16:16.000 --> 00:16:19.690 align:start position:0% have trusted execution environments which<00:16:17.000> are<00:16:17.210> isolated<00:16:18.700> execution 00:16:19.690 --> 00:16:19.700 align:start position:0% which are isolated execution 00:16:19.700 --> 00:16:21.820 align:start position:0% which are isolated execution environments<00:16:20.240> waken<00:16:20.870> to<00:16:20.900> secure<00:16:21.260> processing 00:16:21.820 --> 00:16:21.830 align:start position:0% environments waken to secure processing 00:16:21.830 --> 00:16:23.770 align:start position:0% environments waken to secure processing where<00:16:21.980> you<00:16:22.280> can<00:16:22.460> do<00:16:22.580> untempered<00:16:22.970> processing 00:16:23.770 --> 00:16:23.780 align:start position:0% where you can do untempered processing 00:16:23.780 --> 00:16:26.410 align:start position:0% where you can do untempered processing we<00:16:24.320> have<00:16:24.620> a<00:16:25.250> few<00:16:25.760> of<00:16:25.880> them<00:16:26.030> listed<00:16:26.270> here 00:16:26.410 --> 00:16:26.420 align:start position:0% we have a few of them listed here 00:16:26.420 --> 00:16:28.060 align:start position:0% we have a few of them listed here there's<00:16:26.780> the<00:16:26.900> AMD<00:16:27.200> secure<00:16:27.560> execution 00:16:28.060 --> 00:16:28.070 align:start position:0% there's the AMD secure execution 00:16:28.070 --> 00:16:30.670 align:start position:0% there's the AMD secure execution environment<00:16:28.550> armed<00:16:29.090> trusts<00:16:29.570> on<00:16:29.750> Apple<00:16:30.380> secure 00:16:30.670 --> 00:16:30.680 align:start position:0% environment armed trusts on Apple secure 00:16:30.680 --> 00:16:33.400 align:start position:0% environment armed trusts on Apple secure Enclave<00:16:30.820> Intel<00:16:31.820> SGX<00:16:31.970> and<00:16:32.480> others<00:16:32.750> just<00:16:33.290> to 00:16:33.400 --> 00:16:33.410 align:start position:0% Enclave Intel SGX and others just to 00:16:33.410 --> 00:16:34.960 align:start position:0% Enclave Intel SGX and others just to give<00:16:33.560> you<00:16:33.650> an<00:16:33.770> example<00:16:34.160> of<00:16:34.340> the<00:16:34.460> Apple<00:16:34.730> secure 00:16:34.960 --> 00:16:34.970 align:start position:0% give you an example of the Apple secure 00:16:34.970 --> 00:16:37.840 align:start position:0% give you an example of the Apple secure Enclave<00:16:35.090> um<00:16:35.570> usually<00:16:36.200> nobody<00:16:37.040> knows<00:16:37.370> what's 00:16:37.840 --> 00:16:37.850 align:start position:0% Enclave um usually nobody knows what's 00:16:37.850 --> 00:16:39.160 align:start position:0% Enclave um usually nobody knows what's going<00:16:37.940> on<00:16:38.180> so<00:16:38.240> there<00:16:38.510> has<00:16:38.600> been<00:16:38.630> a<00:16:38.750> lot<00:16:38.900> of<00:16:38.930> like 00:16:39.160 --> 00:16:39.170 align:start position:0% going on so there has been a lot of like 00:16:39.170 --> 00:16:40.360 align:start position:0% going on so there has been a lot of like reverse<00:16:39.440> engineering<00:16:39.860> going<00:16:40.040> on<00:16:40.220> until 00:16:40.360 --> 00:16:40.370 align:start position:0% reverse engineering going on until 00:16:40.370 --> 00:16:41.950 align:start position:0% reverse engineering going on until people<00:16:40.610> know<00:16:40.820> ok<00:16:41.060> what's<00:16:41.270> what's<00:16:41.570> happening 00:16:41.950 --> 00:16:41.960 align:start position:0% people know ok what's what's happening 00:16:41.960 --> 00:16:44.170 align:start position:0% people know ok what's what's happening what<00:16:42.170> what's<00:16:42.470> actually<00:16:43.030> existing<00:16:44.030> they're 00:16:44.170 --> 00:16:44.180 align:start position:0% what what's actually existing they're 00:16:44.180 --> 00:16:46.720 align:start position:0% what what's actually existing they're like<00:16:44.300> whoo-hoo<00:16:44.870> you<00:16:45.620> can't<00:16:46.010> really<00:16:46.190> access<00:16:46.340> it 00:16:46.720 --> 00:16:46.730 align:start position:0% like whoo-hoo you can't really access it 00:16:46.730 --> 00:16:48.850 align:start position:0% like whoo-hoo you can't really access it without<00:16:46.910> like<00:16:47.210> being<00:16:47.270> Apple<00:16:47.870> up<00:16:47.990> without<00:16:48.620> like 00:16:48.850 --> 00:16:48.860 align:start position:0% without like being Apple up without like 00:16:48.860 --> 00:16:51.460 align:start position:0% without like being Apple up without like signing<00:16:49.190> a<00:16:49.280> ton<00:16:49.850> of<00:16:49.880> NDA's<00:16:50.300> so<00:16:50.990> all<00:16:51.200> of<00:16:51.320> them 00:16:51.460 --> 00:16:51.470 align:start position:0% signing a ton of NDA's so all of them 00:16:51.470 --> 00:16:53.470 align:start position:0% signing a ton of NDA's so all of them are<00:16:51.500> sometimes<00:16:52.460> not<00:16:52.580> documented<00:16:53.210> you<00:16:53.300> don't 00:16:53.470 --> 00:16:53.480 align:start position:0% are sometimes not documented you don't 00:16:53.480 --> 00:16:55.060 align:start position:0% are sometimes not documented you don't know<00:16:53.570> what's<00:16:53.750> going<00:16:53.930> on<00:16:54.080> they're<00:16:54.740> not<00:16:54.770> really 00:16:55.060 --> 00:16:55.070 align:start position:0% know what's going on they're not really 00:16:55.070 --> 00:16:57.970 align:start position:0% know what's going on they're not really verifiable<00:16:55.760> for<00:16:56.000> for<00:16:56.870> you<00:16:57.020> so<00:16:57.410> you<00:16:57.470> trust<00:16:57.890> the 00:16:57.970 --> 00:16:57.980 align:start position:0% verifiable for for you so you trust the 00:16:57.980 --> 00:16:59.170 align:start position:0% verifiable for for you so you trust the third<00:16:58.160> party<00:16:58.520> in<00:16:58.580> the<00:16:58.670> whole<00:16:58.820> security 00:16:59.170 --> 00:16:59.180 align:start position:0% third party in the whole security 00:16:59.180 --> 00:17:02.500 align:start position:0% third party in the whole security concept<00:16:59.810> and<00:16:59.960> some<00:17:00.770> of<00:17:00.920> them<00:17:01.130> if<00:17:01.850> not<00:17:01.910> all<00:17:02.180> will 00:17:02.500 --> 00:17:02.510 align:start position:0% concept and some of them if not all will 00:17:02.510 --> 00:17:04.180 align:start position:0% concept and some of them if not all will be<00:17:02.630> headed<00:17:02.930> in<00:17:02.990> the<00:17:03.110> future<00:17:03.500> I<00:17:03.620> mean<00:17:03.830> most<00:17:04.040> of 00:17:04.180 --> 00:17:04.190 align:start position:0% be headed in the future I mean most of 00:17:04.190 --> 00:17:05.800 align:start position:0% be headed in the future I mean most of them<00:17:04.310> are<00:17:04.490> already<00:17:04.610> we<00:17:04.970> saw<00:17:05.330> a<00:17:05.360> spectrum 00:17:05.800 --> 00:17:05.810 align:start position:0% them are already we saw a spectrum 00:17:05.810 --> 00:17:07.540 align:start position:0% them are already we saw a spectrum marathon<00:17:06.170> we<00:17:06.290> saw<00:17:06.410> a<00:17:06.440> lot<00:17:06.620> of<00:17:06.650> existing 00:17:07.540 --> 00:17:07.550 align:start position:0% marathon we saw a lot of existing 00:17:07.550 --> 00:17:09.090 align:start position:0% marathon we saw a lot of existing exploits<00:17:07.910> out<00:17:08.120> there<00:17:08.330> we<00:17:08.480> saw<00:17:08.630> a<00:17:08.660> lot<00:17:08.839> of 00:17:09.090 --> 00:17:09.100 align:start position:0% exploits out there we saw a lot of 00:17:09.100 --> 00:17:11.800 align:start position:0% exploits out there we saw a lot of attempts<00:17:10.100> to<00:17:10.160> to<00:17:10.850> break<00:17:11.030> all<00:17:11.240> these<00:17:11.360> devices 00:17:11.800 --> 00:17:11.810 align:start position:0% attempts to to break all these devices 00:17:11.810 --> 00:17:14.829 align:start position:0% attempts to to break all these devices and<00:17:11.990> it<00:17:12.170> will<00:17:12.320> be<00:17:12.470> hacked<00:17:12.680> so<00:17:12.980> I<00:17:13.490> want<00:17:14.209> to<00:17:14.330> show 00:17:14.829 --> 00:17:14.839 align:start position:0% and it will be hacked so I want to show 00:17:14.839 --> 00:17:16.750 align:start position:0% and it will be hacked so I want to show one<00:17:15.170> example<00:17:15.200> where<00:17:15.800> this<00:17:15.980> could<00:17:16.160> be<00:17:16.310> actually 00:17:16.750 --> 00:17:16.760 align:start position:0% one example where this could be actually 00:17:16.760 --> 00:17:19.840 align:start position:0% one example where this could be actually in<00:17:17.630> the<00:17:17.780> future<00:17:18.140> changing<00:17:18.709> and<00:17:18.950> why<00:17:19.550> we're<00:17:19.760> not 00:17:19.840 --> 00:17:19.850 align:start position:0% in the future changing and why we're not 00:17:19.850 --> 00:17:22.240 align:start position:0% in the future changing and why we're not still<00:17:20.089> the<00:17:20.240> edge<00:17:20.360> still<00:17:20.660> wanna<00:17:21.130> make<00:17:22.130> the 00:17:22.240 --> 00:17:22.250 align:start position:0% still the edge still wanna make the 00:17:22.250 --> 00:17:23.890 align:start position:0% still the edge still wanna make the point<00:17:22.520> that<00:17:22.640> open<00:17:23.060> silicon<00:17:23.450> can<00:17:23.660> in<00:17:23.750> this 00:17:23.890 --> 00:17:23.900 align:start position:0% point that open silicon can in this 00:17:23.900 --> 00:17:26.380 align:start position:0% point that open silicon can in this context<00:17:24.770> solve<00:17:25.370> this<00:17:25.580> security<00:17:26.030> nayad<00:17:26.240> matter 00:17:26.380 --> 00:17:26.390 align:start position:0% context solve this security nayad matter 00:17:26.390 --> 00:17:27.250 align:start position:0% context solve this security nayad matter that<00:17:26.480> we're<00:17:26.600> facing<00:17:26.720> with<00:17:26.959> all<00:17:27.140> these 00:17:27.250 --> 00:17:27.260 align:start position:0% that we're facing with all these 00:17:27.260 --> 00:17:29.650 align:start position:0% that we're facing with all these Hardware<00:17:27.680> pieces<00:17:27.860> and<00:17:28.220> it<00:17:28.940> could<00:17:29.240> also<00:17:29.390> make 00:17:29.650 --> 00:17:29.660 align:start position:0% Hardware pieces and it could also make 00:17:29.660 --> 00:17:32.560 align:start position:0% Hardware pieces and it could also make our<00:17:29.810> harder<00:17:30.110> verifiable<00:17:30.830> so<00:17:31.130> here<00:17:31.580> is<00:17:31.850> very 00:17:32.560 --> 00:17:32.570 align:start position:0% our harder verifiable so here is very 00:17:32.570 --> 00:17:34.180 align:start position:0% our harder verifiable so here is very interesting<00:17:33.230> product<00:17:33.440> I<00:17:33.620> want<00:17:33.770> to<00:17:33.890> point<00:17:34.070> that 00:17:34.180 --> 00:17:34.190 align:start position:0% interesting product I want to point that 00:17:34.190 --> 00:17:36.970 align:start position:0% interesting product I want to point that it's<00:17:34.790> the<00:17:34.940> risk<00:17:35.120> 5<00:17:35.420> it's<00:17:35.870> an<00:17:36.620> open-source 00:17:36.970 --> 00:17:36.980 align:start position:0% it's the risk 5 it's an open-source 00:17:36.980 --> 00:17:39.700 align:start position:0% it's the risk 5 it's an open-source harder<00:17:37.430> instruction<00:17:37.910> set<00:17:38.090> architecture<00:17:38.780> and 00:17:39.700 --> 00:17:39.710 align:start position:0% harder instruction set architecture and 00:17:39.710 --> 00:17:41.350 align:start position:0% harder instruction set architecture and on<00:17:39.890> the<00:17:39.980> left<00:17:40.160> on<00:17:40.610> the<00:17:40.730> right<00:17:40.760> hand<00:17:41.060> side<00:17:41.120> you 00:17:41.350 --> 00:17:41.360 align:start position:0% on the left on the right hand side you 00:17:41.360 --> 00:17:44.800 align:start position:0% on the left on the right hand side you see<00:17:41.570> the<00:17:41.690> freedom<00:17:42.080> III<00:17:42.740> 10<00:17:43.300> SOC<00:17:44.300> which<00:17:44.630> is<00:17:44.720> the 00:17:44.800 --> 00:17:44.810 align:start position:0% see the freedom III 10 SOC which is the 00:17:44.810 --> 00:17:46.870 align:start position:0% see the freedom III 10 SOC which is the first<00:17:45.080> risk<00:17:45.320> 5<00:17:45.590> chip<00:17:45.860> our<00:17:46.070> produce<00:17:46.370> was 00:17:46.870 --> 00:17:46.880 align:start position:0% first risk 5 chip our produce was 00:17:46.880 --> 00:17:49.360 align:start position:0% first risk 5 chip our produce was produced<00:17:47.360> by<00:17:47.600> c5<00:17:48.170> and<00:17:48.500> there<00:17:49.070> are<00:17:49.130> more<00:17:49.310> of 00:17:49.360 --> 00:17:49.370 align:start position:0% produced by c5 and there are more of 00:17:49.370 --> 00:17:51.670 align:start position:0% produced by c5 and there are more of them<00:17:49.640> out<00:17:49.760> now<00:17:50.270> so<00:17:51.050> basically<00:17:51.230> what's 00:17:51.670 --> 00:17:51.680 align:start position:0% them out now so basically what's 00:17:51.680 --> 00:17:53.350 align:start position:0% them out now so basically what's interesting<00:17:51.920> about<00:17:52.160> these<00:17:52.430> things<00:17:52.670> is<00:17:53.150> there 00:17:53.350 --> 00:17:53.360 align:start position:0% interesting about these things is there 00:17:53.360 --> 00:17:56.300 align:start position:0% interesting about these things is there are<00:17:53.390> already<00:17:53.840> existing<00:17:54.910> replacements<00:17:55.910> in<00:17:56.090> the 00:17:56.300 --> 00:17:56.310 align:start position:0% are already existing replacements in the 00:17:56.310 --> 00:17:59.270 align:start position:0% are already existing replacements in the element<00:17:56.700> that<00:17:57.150> would<00:17:57.420> replace<00:17:57.720> HSM<00:17:58.500> STIs<00:17:58.860> and 00:17:59.270 --> 00:17:59.280 align:start position:0% element that would replace HSM STIs and 00:17:59.280 --> 00:18:01.550 align:start position:0% element that would replace HSM STIs and so<00:17:59.430> on<00:17:59.550> so<00:18:00.120> I<00:18:00.180> want<00:18:00.390> to<00:18:00.450> in<00:18:00.840> this<00:18:00.990> context<00:18:01.320> point 00:18:01.550 --> 00:18:01.560 align:start position:0% so on so I want to in this context point 00:18:01.560 --> 00:18:03.410 align:start position:0% so on so I want to in this context point to<00:18:01.710> two<00:18:02.000> interesting<00:18:03.000> projects<00:18:03.270> which<00:18:03.390> I 00:18:03.410 --> 00:18:03.420 align:start position:0% to two interesting projects which I 00:18:03.420 --> 00:18:05.060 align:start position:0% to two interesting projects which I found<00:18:03.810> interesting<00:18:04.230> and<00:18:04.620> which<00:18:04.770> are<00:18:04.890> heavily 00:18:05.060 --> 00:18:05.070 align:start position:0% found interesting and which are heavily 00:18:05.070 --> 00:18:07.370 align:start position:0% found interesting and which are heavily worked<00:18:05.460> upon<00:18:05.640> so<00:18:06.390> one<00:18:06.570> is<00:18:06.690> the<00:18:06.810> sanctum<00:18:07.260> the 00:18:07.370 --> 00:18:07.380 align:start position:0% worked upon so one is the sanctum the 00:18:07.380 --> 00:18:08.630 align:start position:0% worked upon so one is the sanctum the minimum<00:18:07.710> hardware<00:18:07.800> extensions<00:18:08.340> for<00:18:08.460> strong 00:18:08.630 --> 00:18:08.640 align:start position:0% minimum hardware extensions for strong 00:18:08.640 --> 00:18:10.190 align:start position:0% minimum hardware extensions for strong software<00:18:09.000> as<00:18:09.090> elation<00:18:09.480> there's<00:18:09.840> a<00:18:09.900> very<00:18:10.110> nice 00:18:10.190 --> 00:18:10.200 align:start position:0% software as elation there's a very nice 00:18:10.200 --> 00:18:12.230 align:start position:0% software as elation there's a very nice paper<00:18:10.410> from<00:18:10.680> Causton<00:18:11.010> a<00:18:11.040> doll<00:18:11.250> from<00:18:11.430> 2016<00:18:12.030> in 00:18:12.230 --> 00:18:12.240 align:start position:0% paper from Causton a doll from 2016 in 00:18:12.240 --> 00:18:14.090 align:start position:0% paper from Causton a doll from 2016 in case<00:18:12.420> you're<00:18:12.570> interested<00:18:12.720> and<00:18:13.170> their<00:18:13.800> offers 00:18:14.090 --> 00:18:14.100 align:start position:0% case you're interested and their offers 00:18:14.100 --> 00:18:15.890 align:start position:0% case you're interested and their offers simple<00:18:14.310> security<00:18:14.730> analysis<00:18:15.240> 10's<00:18:15.540> checks 00:18:15.890 --> 00:18:15.900 align:start position:0% simple security analysis 10's checks 00:18:15.900 --> 00:18:19.280 align:start position:0% simple security analysis 10's checks which<00:18:16.080> means<00:18:16.320> like<00:18:16.500> also<00:18:17.370> from<00:18:18.290> auditing 00:18:19.280 --> 00:18:19.290 align:start position:0% which means like also from auditing 00:18:19.290 --> 00:18:22.640 align:start position:0% which means like also from auditing perspective<00:18:19.770> it<00:18:19.890> gets<00:18:20.400> easier<00:18:21.350> because<00:18:22.350> it<00:18:22.560> is 00:18:22.640 --> 00:18:22.650 align:start position:0% perspective it gets easier because it is 00:18:22.650 --> 00:18:24.260 align:start position:0% perspective it gets easier because it is lower<00:18:22.800> complexity<00:18:23.340> and<00:18:23.580> this<00:18:23.790> can<00:18:24.000> is 00:18:24.260 --> 00:18:24.270 align:start position:0% lower complexity and this can is 00:18:24.270 --> 00:18:25.970 align:start position:0% lower complexity and this can is approach<00:18:24.570> of<00:18:24.750> lower<00:18:24.900> complexity<00:18:25.440> in<00:18:25.620> hardware 00:18:25.970 --> 00:18:25.980 align:start position:0% approach of lower complexity in hardware 00:18:25.980 --> 00:18:27.920 align:start position:0% approach of lower complexity in hardware is<00:18:26.610> a<00:18:26.670> very<00:18:26.940> interesting<00:18:27.210> approach<00:18:27.480> him<00:18:27.810> up 00:18:27.920 --> 00:18:27.930 align:start position:0% is a very interesting approach him up 00:18:27.930 --> 00:18:29.630 align:start position:0% is a very interesting approach him up you<00:18:28.110> know<00:18:28.140> I<00:18:28.290> think<00:18:28.500> we<00:18:28.620> will<00:18:29.160> be<00:18:29.250> getting<00:18:29.430> than 00:18:29.630 --> 00:18:29.640 align:start position:0% you know I think we will be getting than 00:18:29.640 --> 00:18:31.940 align:start position:0% you know I think we will be getting than a<00:18:29.670> few<00:18:29.940> years<00:18:30.180> and<00:18:30.450> these<00:18:31.110> specific<00:18:31.350> arm 00:18:31.940 --> 00:18:31.950 align:start position:0% a few years and these specific arm 00:18:31.950 --> 00:18:33.530 align:start position:0% a few years and these specific arm solution<00:18:32.370> targets<00:18:32.700> are<00:18:32.790> rocket<00:18:33.090> risk<00:18:33.330> five 00:18:33.530 --> 00:18:33.540 align:start position:0% solution targets are rocket risk five 00:18:33.540 --> 00:18:36.020 align:start position:0% solution targets are rocket risk five core<00:18:33.870> and<00:18:34.140> you<00:18:34.890> can<00:18:35.040> already<00:18:35.190> test<00:18:35.850> this 00:18:36.020 --> 00:18:36.030 align:start position:0% core and you can already test this 00:18:36.030 --> 00:18:38.570 align:start position:0% core and you can already test this online<00:18:36.240> but<00:18:37.170> maybe<00:18:37.320> a<00:18:37.410> more<00:18:37.650> easy<00:18:37.860> starting 00:18:38.570 --> 00:18:38.580 align:start position:0% online but maybe a more easy starting 00:18:38.580 --> 00:18:40.700 align:start position:0% online but maybe a more easy starting point<00:18:38.820> to<00:18:38.970> get<00:18:39.090> are<00:18:39.360> working<00:18:39.900> with<00:18:40.080> risk<00:18:40.320> 5<00:18:40.560> is 00:18:40.700 --> 00:18:40.710 align:start position:0% point to get are working with risk 5 is 00:18:40.710 --> 00:18:43.430 align:start position:0% point to get are working with risk 5 is the<00:18:40.830> Keystone<00:18:41.250> project<00:18:41.630> the<00:18:42.630> open<00:18:42.870> framework 00:18:43.430 --> 00:18:43.440 align:start position:0% the Keystone project the open framework 00:18:43.440 --> 00:18:44.930 align:start position:0% the Keystone project the open framework for<00:18:43.650> architecting<00:18:44.340> trusted<00:18:44.730> execution 00:18:44.930 --> 00:18:44.940 align:start position:0% for architecting trusted execution 00:18:44.940 --> 00:18:47.060 align:start position:0% for architecting trusted execution environments<00:18:45.690> which<00:18:45.900> is<00:18:46.080> very<00:18:46.830> interesting 00:18:47.060 --> 00:18:47.070 align:start position:0% environments which is very interesting 00:18:47.070 --> 00:18:50.660 align:start position:0% environments which is very interesting because<00:18:47.370> in<00:18:48.060> my<00:18:48.240> opinion<00:18:49.370> this<00:18:50.370> is<00:18:50.490> already 00:18:50.660 --> 00:18:50.670 align:start position:0% because in my opinion this is already 00:18:50.670 --> 00:18:51.950 align:start position:0% because in my opinion this is already very<00:18:50.790> far<00:18:51.210> and<00:18:51.510> there's<00:18:51.690> a<00:18:51.750> lot<00:18:51.870> of 00:18:51.950 --> 00:18:51.960 align:start position:0% very far and there's a lot of 00:18:51.960 --> 00:18:53.690 align:start position:0% very far and there's a lot of documentation<00:18:52.410> out<00:18:52.710> then<00:18:52.920> you<00:18:53.040> can<00:18:53.220> you<00:18:53.670> can 00:18:53.690 --> 00:18:53.700 align:start position:0% documentation out then you can you can 00:18:53.700 --> 00:18:56.390 align:start position:0% documentation out then you can you can get<00:18:54.660> this<00:18:54.780> going<00:18:55.620> in<00:18:55.740> your<00:18:55.800> workflow<00:18:56.130> very 00:18:56.390 --> 00:18:56.400 align:start position:0% get this going in your workflow very 00:18:56.400 --> 00:18:58.700 align:start position:0% get this going in your workflow very very<00:18:56.610> fast<00:18:56.880> so<00:18:57.150> in<00:18:57.660> my<00:18:57.780> opinion<00:18:57.870> risk<00:18:58.320> 5<00:18:58.530> is<00:18:58.680> a 00:18:58.700 --> 00:18:58.710 align:start position:0% very fast so in my opinion risk 5 is a 00:18:58.710 --> 00:19:01.820 align:start position:0% very fast so in my opinion risk 5 is a very<00:18:58.950> interesting<00:19:00.020> movement<00:19:01.020> or<00:19:01.410> a<00:19:01.470> really 00:19:01.820 --> 00:19:01.830 align:start position:0% very interesting movement or a really 00:19:01.830 --> 00:19:03.230 align:start position:0% very interesting movement or a really interesting<00:19:02.070> step<00:19:02.490> in<00:19:02.700> the<00:19:02.790> future<00:19:03.090> where<00:19:03.210> we 00:19:03.230 --> 00:19:03.240 align:start position:0% interesting step in the future where we 00:19:03.240 --> 00:19:04.610 align:start position:0% interesting step in the future where we will<00:19:03.450> see<00:19:03.600> that<00:19:03.690> open<00:19:04.020> silicon<00:19:04.410> can 00:19:04.610 --> 00:19:04.620 align:start position:0% will see that open silicon can 00:19:04.620 --> 00:19:07.310 align:start position:0% will see that open silicon can potentially<00:19:05.370> solve<00:19:06.090> our<00:19:06.360> security<00:19:06.900> now<00:19:07.020> as<00:19:07.200> we 00:19:07.310 --> 00:19:07.320 align:start position:0% potentially solve our security now as we 00:19:07.320 --> 00:19:09.890 align:start position:0% potentially solve our security now as we are<00:19:07.410> facing<00:19:07.770> with<00:19:07.890> current<00:19:08.220> day<00:19:08.910> hardware<00:19:09.390> but 00:19:09.890 --> 00:19:09.900 align:start position:0% are facing with current day hardware but 00:19:09.900 --> 00:19:12.350 align:start position:0% are facing with current day hardware but also<00:19:09.930> there's<00:19:10.590> other<00:19:10.770> approaches<00:19:11.310> so<00:19:11.490> there's 00:19:12.350 --> 00:19:12.360 align:start position:0% also there's other approaches so there's 00:19:12.360 --> 00:19:14.900 align:start position:0% also there's other approaches so there's for<00:19:12.570> example<00:19:12.960> the<00:19:13.050> vintage<00:19:13.380> approach<00:19:14.160> this<00:19:14.790> is 00:19:14.900 --> 00:19:14.910 align:start position:0% for example the vintage approach this is 00:19:14.910 --> 00:19:18.320 align:start position:0% for example the vintage approach this is maybe<00:19:15.150> not<00:19:15.510> so<00:19:16.140> common<00:19:16.590> approach<00:19:16.890> but<00:19:17.460> there's 00:19:18.320 --> 00:19:18.330 align:start position:0% maybe not so common approach but there's 00:19:18.330 --> 00:19:20.720 align:start position:0% maybe not so common approach but there's I'm<00:19:18.630> already<00:19:18.960> a<00:19:19.220> community<00:19:20.220> out<00:19:20.370> there<00:19:20.550> which 00:19:20.720 --> 00:19:20.730 align:start position:0% I'm already a community out there which 00:19:20.730 --> 00:19:22.730 align:start position:0% I'm already a community out there which is<00:19:20.850> looking<00:19:21.060> at<00:19:21.240> vintage<00:19:21.930> hardware<00:19:22.320> and<00:19:22.560> like 00:19:22.730 --> 00:19:22.740 align:start position:0% is looking at vintage hardware and like 00:19:22.740 --> 00:19:25.340 align:start position:0% is looking at vintage hardware and like completely<00:19:23.720> uncontrollable<00:19:24.720> or<00:19:25.230> like 00:19:25.340 --> 00:19:25.350 align:start position:0% completely uncontrollable or like 00:19:25.350 --> 00:19:27.620 align:start position:0% completely uncontrollable or like verifiable<00:19:25.920> Hardware<00:19:26.280> because<00:19:26.430> it<00:19:26.700> it<00:19:27.270> is<00:19:27.390> old 00:19:27.620 --> 00:19:27.630 align:start position:0% verifiable Hardware because it it is old 00:19:27.630 --> 00:19:29.960 align:start position:0% verifiable Hardware because it it is old and<00:19:27.840> you<00:19:27.930> can<00:19:28.110> not<00:19:28.800> so<00:19:29.070> easy<00:19:29.250> tamper<00:19:29.670> with<00:19:29.820> it 00:19:29.960 --> 00:19:29.970 align:start position:0% and you can not so easy tamper with it 00:19:29.970 --> 00:19:33.410 align:start position:0% and you can not so easy tamper with it there's<00:19:30.510> also<00:19:31.230> very<00:19:31.530> interesting<00:19:32.420> context 00:19:33.410 --> 00:19:33.420 align:start position:0% there's also very interesting context 00:19:33.420 --> 00:19:36.350 align:start position:0% there's also very interesting context and<00:19:34.460> project<00:19:35.460> I<00:19:35.520> have<00:19:35.640> been<00:19:35.670> referring<00:19:36.060> to<00:19:36.270> am 00:19:36.350 --> 00:19:36.360 align:start position:0% and project I have been referring to am 00:19:36.360 --> 00:19:40.250 align:start position:0% and project I have been referring to am a<00:19:36.480> talk<00:19:36.690> at<00:19:36.870> HTTP<00:19:37.500> or<00:19:37.800> I<00:19:39.020> would<00:19:40.020> strongly 00:19:40.250 --> 00:19:40.260 align:start position:0% a talk at HTTP or I would strongly 00:19:40.260 --> 00:19:41.810 align:start position:0% a talk at HTTP or I would strongly recommend<00:19:40.380> you<00:19:40.830> also<00:19:41.010> listen<00:19:41.220> to<00:19:41.370> this<00:19:41.550> talk 00:19:41.810 --> 00:19:41.820 align:start position:0% recommend you also listen to this talk 00:19:41.820 --> 00:19:44.570 align:start position:0% recommend you also listen to this talk and<00:19:42.570> well<00:19:42.990> potentially<00:19:43.860> vintage<00:19:44.220> hardware 00:19:44.570 --> 00:19:44.580 align:start position:0% and well potentially vintage hardware 00:19:44.580 --> 00:19:48.650 align:start position:0% and well potentially vintage hardware can<00:19:45.090> also<00:19:45.300> help<00:19:45.600> disarm<00:19:46.230> nuclear<00:19:46.820> warheads<00:19:47.820> in 00:19:48.650 --> 00:19:48.660 align:start position:0% can also help disarm nuclear warheads in 00:19:48.660 --> 00:19:49.880 align:start position:0% can also help disarm nuclear warheads in the<00:19:48.810> long<00:19:48.960> run<00:19:49.140> well<00:19:49.320> because<00:19:49.590> there<00:19:49.770> you<00:19:49.860> have 00:19:49.880 --> 00:19:49.890 align:start position:0% the long run well because there you have 00:19:49.890 --> 00:19:51.860 align:start position:0% the long run well because there you have a<00:19:50.010> really<00:19:50.490> really<00:19:50.640> complicated<00:19:51.270> trust<00:19:51.510> setup 00:19:51.860 --> 00:19:51.870 align:start position:0% a really really complicated trust setup 00:19:51.870 --> 00:19:55.730 align:start position:0% a really really complicated trust setup but<00:19:52.860> in<00:19:53.070> conclusion<00:19:53.250> and<00:19:53.810> this<00:19:54.810> is<00:19:55.320> actually 00:19:55.730 --> 00:19:55.740 align:start position:0% but in conclusion and this is actually 00:19:55.740 --> 00:19:59.240 align:start position:0% but in conclusion and this is actually already<00:19:55.890> end<00:19:56.280> of<00:19:56.370> my<00:19:56.490> talk<00:19:57.620> current<00:19:58.620> Hardware 00:19:59.240 --> 00:19:59.250 align:start position:0% already end of my talk current Hardware 00:19:59.250 --> 00:20:01.310 align:start position:0% already end of my talk current Hardware harder<00:19:59.850> almost<00:20:00.120> impossible<00:20:00.630> to<00:20:00.720> verify<00:20:00.840> this 00:20:01.310 --> 00:20:01.320 align:start position:0% harder almost impossible to verify this 00:20:01.320 --> 00:20:03.740 align:start position:0% harder almost impossible to verify this is<00:20:01.410> a<00:20:01.440> problem<00:20:01.860> we<00:20:01.980> trusted<00:20:02.460> parties<00:20:02.940> with<00:20:03.540> on 00:20:03.740 --> 00:20:03.750 align:start position:0% is a problem we trusted parties with on 00:20:03.750 --> 00:20:06.260 align:start position:0% is a problem we trusted parties with on the<00:20:03.900> example<00:20:04.320> of<00:20:04.350> the<00:20:04.410> HSMs<00:20:04.980> on<00:20:05.220> a<00:20:05.250> TEM<00:20:05.880> modern 00:20:06.260 --> 00:20:06.270 align:start position:0% the example of the HSMs on a TEM modern 00:20:06.270 --> 00:20:08.190 align:start position:0% the example of the HSMs on a TEM modern day 00:20:08.190 --> 00:20:08.200 align:start position:0% day 00:20:08.200 --> 00:20:11.919 align:start position:0% day cpu's<00:20:09.200> so<00:20:09.769> they<00:20:10.159> are<00:20:10.249> not<00:20:10.340> zero<00:20:10.639> trust<00:20:10.940> so<00:20:11.779> we 00:20:11.919 --> 00:20:11.929 align:start position:0% cpu's so they are not zero trust so we 00:20:11.929 --> 00:20:13.989 align:start position:0% cpu's so they are not zero trust so we need<00:20:12.049> in<00:20:12.200> my<00:20:12.289> opinion<00:20:12.649> more<00:20:12.830> open<00:20:13.190> hardware<00:20:13.489> to 00:20:13.989 --> 00:20:13.999 align:start position:0% need in my opinion more open hardware to 00:20:13.999 --> 00:20:17.169 align:start position:0% need in my opinion more open hardware to verify<00:20:14.559> and<00:20:15.559> to<00:20:15.710> be<00:20:15.830> able<00:20:15.919> to<00:20:16.129> verify<00:20:16.309> and<00:20:16.820> for 00:20:17.169 --> 00:20:17.179 align:start position:0% verify and to be able to verify and for 00:20:17.179 --> 00:20:19.180 align:start position:0% verify and to be able to verify and for education<00:20:17.539> so<00:20:17.929> in<00:20:18.019> order<00:20:18.350> if<00:20:18.590> this<00:20:18.859> digital 00:20:19.180 --> 00:20:19.190 align:start position:0% education so in order if this digital 00:20:19.190 --> 00:20:21.219 align:start position:0% education so in order if this digital winter<00:20:19.489> coming<00:20:19.669> we<00:20:19.879> need<00:20:20.059> to<00:20:20.179> be<00:20:20.299> able<00:20:20.419> to<00:20:20.690> know 00:20:21.219 --> 00:20:21.229 align:start position:0% winter coming we need to be able to know 00:20:21.229 --> 00:20:23.619 align:start position:0% winter coming we need to be able to know how<00:20:21.619> to<00:20:21.679> repurpose<00:20:22.239> devices<00:20:23.239> we<00:20:23.359> need<00:20:23.509> to 00:20:23.619 --> 00:20:23.629 align:start position:0% how to repurpose devices we need to 00:20:23.629 --> 00:20:25.570 align:start position:0% how to repurpose devices we need to understand<00:20:24.139> and<00:20:24.409> to<00:20:24.799> educate<00:20:25.129> other<00:20:25.279> people 00:20:25.570 --> 00:20:25.580 align:start position:0% understand and to educate other people 00:20:25.580 --> 00:20:28.029 align:start position:0% understand and to educate other people we<00:20:25.669> need<00:20:25.820> to<00:20:25.940> know<00:20:26.059> how<00:20:26.779> these<00:20:26.929> functions<00:20:27.409> in 00:20:28.029 --> 00:20:28.039 align:start position:0% we need to know how these functions in 00:20:28.039 --> 00:20:30.070 align:start position:0% we need to know how these functions in my<00:20:28.249> opinion<00:20:28.669> on<00:20:29.269> the<00:20:29.419> example<00:20:29.840> of<00:20:29.960> the 00:20:30.070 --> 00:20:30.080 align:start position:0% my opinion on the example of the 00:20:30.080 --> 00:20:31.749 align:start position:0% my opinion on the example of the verifiable<00:20:30.559> delay<00:20:30.799> functions<00:20:31.279> the<00:20:31.429> vdf 00:20:31.749 --> 00:20:31.759 align:start position:0% verifiable delay functions the vdf 00:20:31.759 --> 00:20:34.419 align:start position:0% verifiable delay functions the vdf Alliance<00:20:32.600> project<00:20:33.049> this<00:20:33.919> is<00:20:34.070> a<00:20:34.100> very<00:20:34.279> good 00:20:34.419 --> 00:20:34.429 align:start position:0% Alliance project this is a very good 00:20:34.429 --> 00:20:35.799 align:start position:0% Alliance project this is a very good example<00:20:34.519> because<00:20:34.970> this<00:20:35.059> is<00:20:35.179> a<00:20:35.210> project<00:20:35.570> where 00:20:35.799 --> 00:20:35.809 align:start position:0% example because this is a project where 00:20:35.809 --> 00:20:37.359 align:start position:0% example because this is a project where you<00:20:35.929> need<00:20:36.169> open<00:20:36.529> hardware<00:20:36.769> my<00:20:37.009> opinion 00:20:37.359 --> 00:20:37.369 align:start position:0% you need open hardware my opinion 00:20:37.369 --> 00:20:39.789 align:start position:0% you need open hardware my opinion because<00:20:37.729> um<00:20:38.080> it's<00:20:39.080> a<00:20:39.139> mapping<00:20:39.350> in<00:20:39.529> the<00:20:39.590> past 00:20:39.789 --> 00:20:39.799 align:start position:0% because um it's a mapping in the past 00:20:39.799 --> 00:20:42.779 align:start position:0% because um it's a mapping in the past best<00:20:40.129> practice<00:20:40.460> example<00:20:40.999> if<00:20:41.749> you<00:20:41.960> realize<00:20:42.349> the 00:20:42.779 --> 00:20:42.789 align:start position:0% best practice example if you realize the 00:20:42.789 --> 00:20:44.919 align:start position:0% best practice example if you realize the verifiable<00:20:43.789> delay<00:20:44.029> fighters<00:20:44.479> with<00:20:44.659> open 00:20:44.919 --> 00:20:44.929 align:start position:0% verifiable delay fighters with open 00:20:44.929 --> 00:20:47.049 align:start position:0% verifiable delay fighters with open hardware<00:20:45.200> it<00:20:45.799> ensures<00:20:46.099> fair<00:20:46.460> access<00:20:46.609> to<00:20:46.970> the 00:20:47.049 --> 00:20:47.059 align:start position:0% hardware it ensures fair access to the 00:20:47.059 --> 00:20:49.629 align:start position:0% hardware it ensures fair access to the fastest<00:20:47.450> implementations<00:20:48.139> so<00:20:48.349> you<00:20:48.919> can<00:20:49.099> also 00:20:49.629 --> 00:20:49.639 align:start position:0% fastest implementations so you can also 00:20:49.639 --> 00:20:52.619 align:start position:0% fastest implementations so you can also look<00:20:49.879> at<00:20:50.059> open<00:20:50.479> hardware<00:20:50.869> as<00:20:50.960> a<00:20:50.989> kind<00:20:51.259> of 00:20:52.619 --> 00:20:52.629 align:start position:0% look at open hardware as a kind of 00:20:52.629 --> 00:20:57.549 align:start position:0% look at open hardware as a kind of approach<00:20:53.629> to<00:20:53.950> create<00:20:54.970> equilibrium<00:20:56.169> so<00:20:57.169> in<00:20:57.440> my 00:20:57.549 --> 00:20:57.559 align:start position:0% approach to create equilibrium so in my 00:20:57.559 --> 00:20:59.440 align:start position:0% approach to create equilibrium so in my opinion<00:20:57.679> risk<00:20:58.039> 5<00:20:58.220> can<00:20:58.429> change<00:20:58.700> the<00:20:58.849> game<00:20:58.999> but 00:20:59.440 --> 00:20:59.450 align:start position:0% opinion risk 5 can change the game but 00:20:59.450 --> 00:21:01.089 align:start position:0% opinion risk 5 can change the game but only<00:20:59.599> also<00:21:00.109> if<00:21:00.200> we<00:21:00.379> make<00:21:00.559> sure<00:21:00.710> that<00:21:00.830> there<00:21:01.009> are 00:21:01.089 --> 00:21:01.099 align:start position:0% only also if we make sure that there are 00:21:01.099 --> 00:21:02.560 align:start position:0% only also if we make sure that there are enough<00:21:01.129> course<00:21:01.609> with<00:21:01.849> open<00:21:02.179> licenses 00:21:02.560 --> 00:21:02.570 align:start position:0% enough course with open licenses 00:21:02.570 --> 00:21:04.899 align:start position:0% enough course with open licenses available<00:21:02.690> so<00:21:03.109> there's<00:21:03.259> a<00:21:03.289> lot<00:21:03.470> of<00:21:03.909> existing 00:21:04.899 --> 00:21:04.909 align:start position:0% available so there's a lot of existing 00:21:04.909 --> 00:21:06.549 align:start position:0% available so there's a lot of existing implementations<00:21:05.720> of<00:21:05.809> the<00:21:05.929> risk<00:21:06.109> 5<00:21:06.289> course 00:21:06.549 --> 00:21:06.559 align:start position:0% implementations of the risk 5 course 00:21:06.559 --> 00:21:08.680 align:start position:0% implementations of the risk 5 course which<00:21:06.769> are<00:21:06.950> with<00:21:07.309> closed<00:21:07.580> software<00:21:08.539> with 00:21:08.680 --> 00:21:08.690 align:start position:0% which are with closed software with 00:21:08.690 --> 00:21:11.349 align:start position:0% which are with closed software with closed<00:21:09.169> licenses<00:21:09.679> so<00:21:10.220> I'm<00:21:10.429> strongly<00:21:10.940> I'm 00:21:11.349 --> 00:21:11.359 align:start position:0% closed licenses so I'm strongly I'm 00:21:11.359 --> 00:21:13.479 align:start position:0% closed licenses so I'm strongly I'm suggesting<00:21:11.989> we<00:21:12.379> look<00:21:12.499> at<00:21:12.679> and<00:21:13.070> we<00:21:13.190> make<00:21:13.340> sure 00:21:13.479 --> 00:21:13.489 align:start position:0% suggesting we look at and we make sure 00:21:13.489 --> 00:21:15.099 align:start position:0% suggesting we look at and we make sure that<00:21:13.639> there<00:21:13.789> are<00:21:13.879> enough<00:21:13.999> really<00:21:14.720> open 00:21:15.099 --> 00:21:15.109 align:start position:0% that there are enough really open 00:21:15.109 --> 00:21:17.139 align:start position:0% that there are enough really open licenses<00:21:15.979> available<00:21:16.070> for<00:21:16.489> this<00:21:16.580> cause<00:21:16.820> such 00:21:17.139 --> 00:21:17.149 align:start position:0% licenses available for this cause such 00:21:17.149 --> 00:21:19.149 align:start position:0% licenses available for this cause such as<00:21:17.269> the<00:21:17.389> glue<00:21:17.539> license<00:21:17.989> so<00:21:18.739> you<00:21:18.830> can<00:21:18.979> follow 00:21:19.149 --> 00:21:19.159 align:start position:0% as the glue license so you can follow 00:21:19.159 --> 00:21:21.369 align:start position:0% as the glue license so you can follow further<00:21:19.729> on<00:21:19.970> all<00:21:20.149> the<00:21:20.269> other<00:21:20.450> open<00:21:21.139> hardware 00:21:21.369 --> 00:21:21.379 align:start position:0% further on all the other open hardware 00:21:21.379 --> 00:21:23.710 align:start position:0% further on all the other open hardware talks<00:21:21.679> at<00:21:21.889> the<00:21:22.070> open<00:21:22.820> how<00:21:22.940> the<00:21:22.999> amount<00:21:23.239> cited 00:21:23.710 --> 00:21:23.720 align:start position:0% talks at the open how the amount cited 00:21:23.720 --> 00:21:27.489 align:start position:0% talks at the open how the amount cited Oh<00:21:23.899> hm<00:21:24.320> aqua<00:21:24.739> org<00:21:24.979> and<00:21:25.190> you<00:21:26.090> can<00:21:26.269> also<00:21:26.509> get<00:21:27.379> in 00:21:27.489 --> 00:21:27.499 align:start position:0% Oh hm aqua org and you can also get in 00:21:27.499 --> 00:21:29.379 align:start position:0% Oh hm aqua org and you can also get in contact<00:21:27.710> with<00:21:27.859> discuss<00:21:28.159> further<00:21:28.399> at<00:21:29.239> the 00:21:29.379 --> 00:21:29.389 align:start position:0% contact with discuss further at the 00:21:29.389 --> 00:21:30.849 align:start position:0% contact with discuss further at the right<00:21:29.539> at<00:21:29.690> east<00:21:29.899> side<00:21:30.049> or<00:21:30.259> you<00:21:30.379> can<00:21:30.409> visit<00:21:30.769> us 00:21:30.849 --> 00:21:30.859 align:start position:0% right at east side or you can visit us 00:21:30.859 --> 00:21:33.190 align:start position:0% right at east side or you can visit us today<00:21:31.159> at<00:21:31.429> 4<00:21:32.179> we<00:21:32.570> have<00:21:32.690> a<00:21:32.720> small<00:21:32.989> get-together 00:21:33.190 --> 00:21:33.200 align:start position:0% today at 4 we have a small get-together 00:21:33.200 --> 00:21:35.289 align:start position:0% today at 4 we have a small get-together together<00:21:33.649> with<00:21:33.799> trained<00:21:34.039> security<00:21:34.190> at<00:21:34.909> the 00:21:35.289 --> 00:21:35.299 align:start position:0% together with trained security at the 00:21:35.299 --> 00:21:37.869 align:start position:0% together with trained security at the elsewhere<00:21:35.659> exhibition<00:21:36.169> in<00:21:36.409> the<00:21:37.099> third<00:21:37.669> floor 00:21:37.869 --> 00:21:37.879 align:start position:0% elsewhere exhibition in the third floor 00:21:37.879 --> 00:21:42.030 align:start position:0% elsewhere exhibition in the third floor thank<00:21:38.840> you<00:21:38.899> very<00:21:39.019> much 00:21:42.030 --> 00:21:42.040 align:start position:0% 00:21:42.040 --> 00:21:50.300 align:start position:0% [Applause] 00:21:50.300 --> 00:21:50.310 align:start position:0% 00:21:50.310 --> 00:21:52.370 align:start position:0% you