1
00:00:05,460 --> 00:00:11,180
Welcome to Space Security Challenge 2020, HackASAT, the final event.

2
00:00:11,180 --> 00:00:20,100
As the democratization of space opens up a new frontier for exploration and innovation, we see new cybersecurity vulnerabilities emerging.

3
00:00:21,020 --> 00:00:32,740
The Space Security Challenge is designed to inspire the world's top cybersecurity talent to develop the skills necessary to secure this last frontier of cybersecurity, space.

4
00:00:32,940 --> 00:00:35,720
And already we've made a ton of progress.

5
00:00:35,720 --> 00:00:37,240
I'll catch you up.

6
00:00:37,280 --> 00:00:46,880
This spring we hosted over 2,000 teams who worked their way through a set of foundational space cybersecurity challenges in our HackASAT qualification round.

7
00:00:46,880 --> 00:00:51,300
Now, eight finalist teams are stepping up to the ultimate challenge.

8
00:00:51,300 --> 00:00:54,060
They are hacking a satellite.

9
00:01:00,640 --> 00:01:06,220
Welcome to the first of two daily recaps for the Space Security Challenge 2020 or HackASAT.

10
00:01:06,220 --> 00:01:08,660
I'm still your host, Jordan Wines.

11
00:01:09,320 --> 00:01:16,920
As our eight teams have been vying for a share of a $100,000 prize pool, we're going to check in and summarize the status of the day.

12
00:01:16,920 --> 00:01:21,860
Of course, they also received $15,000 just to get here as a finalist.

13
00:01:22,020 --> 00:01:24,200
The competition for that was fierce.

14
00:01:24,200 --> 00:01:29,840
Our finalists beat out over 2,000 other teams made up of over 6,000 other competitors.

15
00:01:30,100 --> 00:01:41,420
Of course, the biggest prize of all might not even be the money or even the friends we made along the way, but the bragging rights for your code to be selected to take an actual photograph of the moon from a satellite in space.

16
00:01:41,680 --> 00:01:50,300
While this event was originally planned to be in person during DEF CON in the aerospace village, the global pandemic has caused us to reimagine the event experience.

17
00:01:50,380 --> 00:01:57,600
The result is an immersive 3D environment where you can stay up to date with the competition while learning all about space security and the event itself.

18
00:01:57,600 --> 00:02:01,740
You can connect with other spectators and even play games and add to our graffiti wall.

19
00:02:01,840 --> 00:02:08,760
So if you aren't already watching this from our immersive 3D environment, check it out at virtual.hackasat.com.

20
00:02:09,080 --> 00:02:16,260
As prior DEF CON attendees, some of you are very familiar with the many flavors of contests that test your hacking skills.

21
00:02:16,260 --> 00:02:19,160
But for others, we realize this is a whole new world.

22
00:02:19,160 --> 00:02:25,800
There are many types of hacking contests and Hackasat falls into the category of Capture the Flag or CTF.

23
00:02:28,650 --> 00:02:33,010
Remember the game you played as a kid with flags hidden in opponent's terrain?

24
00:02:33,010 --> 00:02:37,090
Now imagine the field or code and the flags are secret data.

25
00:02:37,090 --> 00:02:43,470
Players exploit security flaws to capture the flags while at the same time defending their networks from opposing teams.

26
00:02:43,470 --> 00:02:48,670
These Capture the Flag CTF events are as diverse as the teams that play them.

27
00:02:48,770 --> 00:02:53,430
This is a global competitive community with thousands of players and global rankings.

28
00:02:53,430 --> 00:02:58,330
It's been a part of the origin story for a great many prominent security experts.

29
00:02:58,350 --> 00:03:00,790
So what do these hacking games look like?

30
00:03:00,790 --> 00:03:06,530
CTFs can be either in-person or online and usually take place over a weekend or other short period.

31
00:03:06,530 --> 00:03:11,230
They often have a qualification round that determines who gets to participate in the finals.

32
00:03:11,230 --> 00:03:21,650
CTFs are sometimes themed around a specific domain like space for Hackasat, but more commonly they are not specialized and include a wide variety of different types of challenges.

33
00:03:21,710 --> 00:03:31,050
The most common types of CTFs include Jeopardy CTFs, sometimes called Red Team CTFs, are named for their use of the classic game board as a scoreboard.

34
00:03:31,050 --> 00:03:32,690
These are more offensive focused.

35
00:03:32,690 --> 00:03:41,010
Each team is given infrastructure to attack and the number of successful attacks, the difficulty, or the speed at which they succeed is factored into their score.

36
00:03:41,010 --> 00:03:47,850
Attack Defense, A-D, or Full Spectrum CTFs, which are closer to the original game you might have played as a kid.

37
00:03:47,850 --> 00:03:54,510
Each team has a server or set of servers to defend and must attack other teams while also protecting their own infrastructure.

38
00:03:54,510 --> 00:04:02,650
Key of the Hill style CTFs are Full Spectrum CTFs in which teams score points by gaining and maintaining control of individual systems.

39
00:04:02,750 --> 00:04:07,850
And finally, the less common Blue Team Exercises, which are primarily defensive events.

40
00:04:07,850 --> 00:04:14,310
Game organizers host an environment and often a professional team of attackers to test the participants defensive skills.

41
00:04:14,310 --> 00:04:17,190
These are more common in the high school and collegiate level.

42
00:04:17,290 --> 00:04:18,430
How do you win?

43
00:04:18,550 --> 00:04:25,110
Even though the goal of the CTFs are to find and exploit vulnerabilities in computer systems, fair play is essential.

44
00:04:25,170 --> 00:04:30,670
There are lots of ways to win, but to get the respect of your peers, you need to have good technical solutions.

45
00:04:30,710 --> 00:04:37,650
Nobody is impressed if you use a network flood to knock the scoreboard offline, and those kinds of shenanigans will get you shunned quickly.

46
00:04:37,650 --> 00:04:45,280
The best CTF players have built specialized tools, practice within their domains, and include domain experts in many aspects of security.

47
00:04:46,290 --> 00:04:47,330
Why CTF?

48
00:04:47,330 --> 00:04:55,530
At their core, CTF challenges are a way for hackers to build community and demonstrate and hone their skills with other equally skilled people.

49
00:04:55,530 --> 00:05:03,250
Competitions are also a chance to experience the joy of learning about a new programming language or a new piece of technology hackers haven't used before.

50
00:05:03,250 --> 00:05:10,390
Capture the Flag challenges have also been used to help train cybersecurity teams and to get new hackers interested in security research.

51
00:05:10,390 --> 00:05:16,490
Some companies even use competitions similar to CTFs to recruit and vet potential candidates for employment.

52
00:05:16,490 --> 00:05:23,110
And CTFs have had real-world impact, with competitors finding actual security flaws in contest infrastructure.

53
00:05:23,110 --> 00:05:28,690
Their solutions, while not counting towards winning the game, are often implemented in a real-world context.

54
00:05:29,090 --> 00:05:40,450
With HackASAT, we have a CTF game designed to raise awareness about cybersecurity issues in space and help researchers develop specific skills and domain knowledge they'll need to help secure this new frontier.

55
00:05:40,770 --> 00:05:47,670
But as many of the players during our Qualls round found out, there are a lot of problems unique to the environments outside our atmosphere.

56
00:05:47,670 --> 00:05:54,870
To learn more about hacking in space, check out our Space Talk videos that explain some of the most interesting space-specific challenges.

57
00:05:56,010 --> 00:06:04,050
For more on CTFs and other hacking and space-related topics, go to the research room in the virtual environment or check out the related YouTube playlist.

58
00:06:04,190 --> 00:06:07,830
Okay, let's go ahead and recap the whole day so far.

59
00:06:13,880 --> 00:06:24,000
The game has actually been underway for one hour now, and our team's first challenge has been to regain control of the ground station that they'll be using to communicate with their Flatsats.

60
00:06:24,000 --> 00:06:31,720
In fact, just before this broadcast went live, we received word that this challenge was actually solved by Team Samurai.

61
00:06:31,960 --> 00:06:33,400
Congratulations to them!

62
00:06:33,400 --> 00:06:39,880
Right after our last update ended with only a Samurai solve, several other teams came in with solutions for Challenge Zero.

63
00:06:40,060 --> 00:06:44,640
PFS and Solarwine were solvers 2 and 3 on that challenge.

64
00:06:44,980 --> 00:06:51,340
After those two teams scored on Challenge Zero , every other team was eventually able to solve Challenge Zero over the next several hours.

65
00:06:51,340 --> 00:06:55,740
Taking a look at the scoreboard so far, we've had an eventful last hour.

66
00:06:55,740 --> 00:07:00,120
Our teams continue to make progress, with four teams now having solved Challenge One.

67
00:07:00,200 --> 00:07:07,180
Unfortunately, the window of time after first solve has expired, and the remaining four teams were given a solution with no points.

68
00:07:07,240 --> 00:07:15,340
PFS and Colon Can Into Space were joined by 1553 and 1064 Seabred with solutions for Challenge One.

69
00:07:15,480 --> 00:07:25,080
Now, this was going to be where I signed off with this update, but as we were live, PFS actually jumped up on the scoreboard yet again, solving Challenge Two.

70
00:07:30,870 --> 00:07:34,790
You may have noticed that first blood overlay and sound effect in that summary.

71
00:07:34,790 --> 00:07:45,350
While it was originally used in Unreal Tournament to indicate a kill, the phrase and even sometimes the sound effects are often used in CTF competitions to indicate the first team to solve a particular challenge.

72
00:07:46,330 --> 00:08:04,110
The challenges that teams have solved so far include a which required exploiting an insecure web application to steal credentials for the ground station controller, and then using that Cosmos ground station, the teams had to restore communication with their flatsets as they were tumbling and not communicating well.

73
00:08:04,270 --> 00:08:15,070
The Challenge One involved connecting to the ground station, turning up the power, turning down the bandwidth, which is very much a real-world troubleshooting step.

74
00:08:15,190 --> 00:08:23,310
Next, the teams have to restore proper orientation control over their flatset, but only one team so far has managed to accomplish this feat.

75
00:08:23,330 --> 00:08:27,110
That brings us to what's happened in the last two hours of the competition.

76
00:08:27,270 --> 00:08:30,050
Most teams are now working on two or three challenges.

77
00:08:30,250 --> 00:08:33,770
The on-orbit challenge, Challenge Two, and Challenge Three.

78
00:08:36,030 --> 00:08:41,030
PFS has been pulling away to a healthy lead that is going to be hard to catch up to tomorrow.

79
00:08:41,050 --> 00:08:43,470
Hard, but definitely not impossible.

80
00:08:43,750 --> 00:08:50,250
All it takes is for them to get stuck in a problem and be passed in turn, much like they did to Samurai at the start of the game.

81
00:08:51,190 --> 00:09:02,610
It's also interesting to note that PFS, which is actually short for Pwn First Search, and Pulling Can Into Space, are number one and number two on the leaderboard, are two of the smallest teams in the competition.

82
00:09:02,970 --> 00:09:11,770
Having a large team is sometimes an advantage, but it definitely comes with logistical issues, and in this case, where the challenges are serial in nature, it isn't always helpful.

83
00:09:12,090 --> 00:09:15,970
Let's take a look again at the PFS team bio.

84
00:09:44,920 --> 00:09:50,960
If you were here with us live, you might remember that right in the middle of teams working on their challenges at around 12 p.m.

85
00:09:50,960 --> 00:09:56,440
Pacific, all teams had to stop what they were doing and shift focus to the on-orbit challenge.

86
00:09:57,400 --> 00:10:00,620
Stop everything and look up.

87
00:10:00,920 --> 00:10:04,440
Starting now, teams shift to the on-orbit challenge.

88
00:10:04,520 --> 00:10:08,820
Their primary goal is to capture a picture of the moon using this satellite.

89
00:10:09,460 --> 00:10:15,240
Competitors will have access to the two-line element of the vehicle and the camera's foresight vector.

90
00:10:15,640 --> 00:10:22,900
Each team is tasked with creating a mission plan that transitions a satellite from a tumbling state to one where it points the camera at the moon.

91
00:10:23,500 --> 00:10:28,960
The team will reach a successful status once their resulting mission plan meets key criteria.

92
00:10:29,340 --> 00:10:34,580
One , the commands are generated in the correct order and are within the specified period.

93
00:10:34,580 --> 00:10:39,280
Two, the image capture angle of the moon is within specifications.

94
00:10:40,080 --> 00:10:48,420
Three, the team's negative z-axis is pointed as close to the earth's center as possible without affecting the camera to moon pointing error.

95
00:10:48,760 --> 00:10:54,060
The teams are given a command dictionary with the format for submitting the commands and parameters.

96
00:10:54,080 --> 00:10:56,380
The rest is up to them.

97
00:10:59,260 --> 00:11:04,820
Of course, while PFS is currently in the lead, they still have a critical problem to solve.

98
00:11:04,900 --> 00:11:07,300
Specifically, the on-orbit challenge.

99
00:11:07,300 --> 00:11:18,580
While Pullin' Cannon to Space is only nipping at their heels at number two on the scoreboard, they are critically not only the first team with an attempted solution to their on-orbit challenge, but the first with an accepted solution.

100
00:11:18,920 --> 00:11:32,480
That would mean that they would be able to pass PFS if PFS is not able to actually solve because, again, that is a pass-fail challenge and it will be critical to see what happens in the last few minutes of gameplay today as well as tomorrow in the on-orbit challenge.

101
00:11:32,760 --> 00:11:48,360
Now that the day is wrapping up, hopefully some of the organizers have a little bit more time, so we're going to see if we can bring into video chat Vito Genovese, who many of you may recognize from his time as a member of LegitBS, the team that organized the DEF CON CTF for five years prior to the current organizers,

102
00:11:48,360 --> 00:11:49,640
The Order of the Overflow.

103
00:11:49,760 --> 00:11:55,080
Vito is also currently with Chromulence, the creators of the flatsats and many of the challenges in HackASAP.

104
00:11:55,140 --> 00:11:56,420
Vito, can you hear me?

105
00:11:56,420 --> 00:11:57,040
Are you there?

106
00:11:57,700 --> 00:11:58,700
Yes, loud and clear.

107
00:11:58,700 --> 00:11:59,460
Good evening.

108
00:11:59,580 --> 00:12:00,140
Excellent.

109
00:12:00,140 --> 00:12:01,060
Glad we got you.

110
00:12:01,060 --> 00:12:01,820
Thanks for stopping by.

111
00:12:01,820 --> 00:12:06,420
I know you guys have been very, very busy kind of manning the systems and talking to the teams.

112
00:12:06,420 --> 00:12:08,300
How's the game going so far?

113
00:12:09,000 --> 00:12:10,120
It's been going.

114
00:12:10,240 --> 00:12:12,640
We've kind of had some, you know, rough times today.

115
00:12:12,640 --> 00:12:23,900
The flatsats are, you know, small run hardware, which always has issues, but we're super, super thankful the teams are being patient with us and they're putting up a good fight and making really, really good progress in the game.

116
00:12:24,100 --> 00:12:25,980
Is this pacing what you expected?

117
00:12:26,000 --> 00:12:29,720
Sorry, is this pacing what you expected speaking of like how they're kind of doing?

118
00:12:29,720 --> 00:12:33,960
Is this about where you thought they would be or you wanted them to be or how does this fit with your expectations?

119
00:12:34,740 --> 00:12:37,700
It's really hard to set expectations for these games.

120
00:12:37,700 --> 00:12:40,260
A lot of it is, you know, throwing stuff around.

121
00:12:40,260 --> 00:12:43,520
We can't even be in the same room doodling on a whiteboard while we do it.

122
00:12:43,700 --> 00:12:50,180
So, you know, the expectations are not necessarily what's been happening, but we'll survive.

123
00:12:50,180 --> 00:12:54,800
It's a difficult game and, you know, we'll see what happens tomorrow.

124
00:12:55,120 --> 00:13:00,400
And I mean, it does seem like that if they're made good progress up to here, they could have been a lot further behind.

125
00:13:00,400 --> 00:13:04,300
It would be nice to see them maybe a challenge ahead, but this is certainly within reach, right?

126
00:13:04,300 --> 00:13:07,240
Like there's nothing kind of too crazy about what they have remaining.

127
00:13:07,380 --> 00:13:11,260
This could be doable and we know these are good teams that are capable of more, it seems like, right?

128
00:13:12,120 --> 00:13:13,440
Right, yeah, absolutely.

129
00:13:13,760 --> 00:13:20,640
The, you know, challenges zero, challenges one, they're hard challenges and the teams that took time on them, they still took time on them.

130
00:13:20,640 --> 00:13:22,980
They did make progress and they did get through eventually.

131
00:13:23,340 --> 00:13:28,220
It's, you know, admirable work and it's, you know, it's a difficult time for everybody involved.

132
00:13:28,580 --> 00:13:33,440
Now, do you miss actually being in Vegas and going to DEF CON or you actually kind of prefer being remote?

133
00:13:33,440 --> 00:13:34,800
What's your take on that?

134
00:13:34,800 --> 00:13:36,920
Oh, I absolutely miss it.

135
00:13:37,180 --> 00:13:42,580
You know, my favorite restaurant in Vegas, I miss, or my favorite restaurants, plural in Vegas, I miss that.

136
00:13:42,580 --> 00:13:43,960
I miss seeing my friends.

137
00:13:43,960 --> 00:13:54,660
I miss wearing my, you know, special DEF CON shoes, which are behind me on the shelf there, not in frame yet, but, you know, it's better than getting really, really sick, I guess.

138
00:13:55,320 --> 00:13:59,680
Given the alternative, yeah, we're all kind of doing what we can and should there.

139
00:13:59,680 --> 00:14:07,700
In fact, even you were originally supposed to be on stream with me and we just thought for safety reasons that we would do this via Zoom and we'd be able to work it out that way.

140
00:14:07,700 --> 00:14:10,180
So thanks for doing that.

141
00:14:10,180 --> 00:14:17,100
Tell me a little bit more about the rationale behind the scoring algorithm and the game design, this decay and the kind of the grace window.

142
00:14:17,100 --> 00:14:20,740
What design constraints went into that decision?

143
00:14:21,500 --> 00:14:25,840
Okay, so the main design constraint with this is it's a very linear catch-the-flag game.

144
00:14:26,800 --> 00:14:34,840
So what has to happen is we're trying to get teams to take over this or regain control of this, you know, tumbling satellite lost in space.

145
00:14:34,940 --> 00:14:37,300
And that is a complicated operation.

146
00:14:37,620 --> 00:14:45,860
And instead of just having, you know, one single, you know, you get this chunk of points if you win the game, we split it up into different little gates that teams have to pass through.

147
00:14:46,060 --> 00:14:51,520
So, you know, challenge zero or the first gate is getting control of a machine in the ground station.

148
00:14:51,680 --> 00:14:56,060
Challenge one after that is being able to actually talk and receive messages with the satellite.

149
00:14:56,200 --> 00:15:02,120
So we had to split this up in order to keep, you know, make the game actually have points before you get to the end.

150
00:15:02,460 --> 00:15:11,520
And at the same time, in order to make the points actually meaningful, we wanted to make sure there was some time pressure for teams to go quickly and make progress throughout the whole weekend.

151
00:15:11,720 --> 00:15:14,440
So we have this kind of decay system implemented.

152
00:15:14,640 --> 00:15:17,740
So each challenge is worth a fixed number of points at the beginning.

153
00:15:17,780 --> 00:15:22,580
And as soon as the team solves it the first time, the clock starts ticking.

154
00:15:22,580 --> 00:15:28,000
So within that first 30 minutes, anybody else who solves that challenge is also going to get the full points.

155
00:15:28,000 --> 00:15:29,760
For challenge zero, that would be 50 points.

156
00:15:29,760 --> 00:15:33,540
For challenge two or for challenge one, that was 200 points.

157
00:15:33,620 --> 00:15:42,220
Beyond that, after that first 30 minutes, we have another two-hour interval where that point amount starts gradually ticking down towards zero.

158
00:15:42,660 --> 00:15:45,100
Once it's hit zero, we don't award points for it.

159
00:15:45,100 --> 00:15:50,440
And at that point, it also means that we share hints to, you know, nudge teams along to get them to the next phase of the competition.

160
00:15:51,060 --> 00:16:05,720
And that's one of the advantages, I think, is that, you know, a team, if they happen to get stuck on one particular problem in a serial event in particular, there's just not much you can do in fairness to the other teams in terms of, you know, kind of you don't want to give a team a hint just because they're behind because that actually hurts them.

161
00:16:05,720 --> 00:16:11,640
But by having the score drop off at a point which they have to be done or else they're just given a hint, well, then they've lost all the points for it.

162
00:16:11,640 --> 00:16:15,420
And so, it keeps them up with the game while not punishing the teams that do well.

163
00:16:15,420 --> 00:16:17,120
So, that makes a lot of sense.

164
00:16:17,120 --> 00:16:19,940
If you had a favorite challenge, what's the number?

165
00:16:19,940 --> 00:16:24,100
And if it's one we haven't seen yet, like, no spoilers, of course, but what do you like best?

166
00:16:24,800 --> 00:16:31,980
So, it's honestly, for me, it's probably challenge one, which is kind of where the game starts to diverge from a normal Capture the Flag contest.

167
00:16:31,980 --> 00:16:36,940
With Challenge Zero, we had a web app that teams had to, I think, determine a cookie secret in.

168
00:16:37,180 --> 00:16:37,760
And that's very...

169
00:16:41,060 --> 00:16:43,440
Challenge one is where we start to diverge.

170
00:16:43,720 --> 00:16:59,820
That's where we have to, once we've gotten into the ground station and are able to talk to the, you know, satellite control system, Cosmos, that's where teams have to figure out how to turn telemetry on on the satellite because it's not, you know, just another machine on the network with an IP address.

171
00:16:59,820 --> 00:17:09,560
And where teams have to figure out how to tell the satellite's radio to configure itself in a way that it's actually functional for the rest of the game, for sending messages back and forth.

172
00:17:09,560 --> 00:17:18,420
I saw a great quote go over the team communication channel from the organizers that said, these are not like traditional network devices.

173
00:17:18,420 --> 00:17:31,680
And if you think sending, you know, two requests a second, you know, will get you more reliability the way you would in a normal network, that may be counterproductive here, which I thought was a great kind of nod towards the, yeah, there's some different constraints and different concerns that maybe,

174
00:17:31,680 --> 00:17:36,440
you know, are not the folks first instincts are accurate on, given the environment.

175
00:17:36,440 --> 00:17:37,840
So that makes a lot of sense.

176
00:17:38,400 --> 00:17:39,400
Yeah, absolutely.

177
00:17:39,400 --> 00:17:43,300
It's a satellite is in some senses, it is, you know, still a computer.

178
00:17:43,520 --> 00:17:48,680
But the problem is, is it's a computer that costs millions and millions of dollars to, you know, install.

179
00:17:48,680 --> 00:17:50,380
And it costs, you know, billions of...

180
00:17:52,220 --> 00:17:55,260
No, I think we might have lost you a little bit there for some network.

181
00:17:56,420 --> 00:18:01,160
Oh, it costs, you know, millions to, you know, put it in place in the first place.

182
00:18:01,160 --> 00:18:04,680
And it costs billions to send somebody up there to push a button to restart it.

183
00:18:05,180 --> 00:18:08,820
Beyond that, it's, you know, a computer that you only talk to an RF.

184
00:18:08,940 --> 00:18:13,400
And it's moving in a way that whenever you can see it, you can probably talk to it.

185
00:18:13,400 --> 00:18:17,200
But there's a lot of time from any given ground station where you can't see it at all.

186
00:18:17,360 --> 00:18:19,860
And that's a very unique challenge.

187
00:18:21,060 --> 00:18:25,620
Vito, thank you very much for both your work on the game and for taking some time to talk to us tonight.

188
00:18:25,620 --> 00:18:31,880
Look forward to seeing how teams do tomorrow and look forward to talking to some more as we see their progress.

189
00:18:32,520 --> 00:18:33,160
Excellent.

190
00:18:33,160 --> 00:18:33,500
Thanks.

191
00:18:33,500 --> 00:18:34,380
Take care.

192
00:18:34,480 --> 00:18:35,460
Take care.

193
00:18:36,180 --> 00:18:41,620
That's it for this first day of the Space Security Challenge 2020 or HackASet final event.

194
00:18:41,620 --> 00:18:52,220
Overnight, we'll be taking our FlatSats offline so they can get a good rest, aka have their batteries charged, and so the competition organizers can recharge their batteries , aka have a good night's rest.

195
00:18:52,220 --> 00:19:00,060
Of course, in addition to sleep, the teams will need to continue working on some of the components in between game shutdown and game start tomorrow morning at 7 a.m.

196
00:19:00,060 --> 00:19:01,120
Pacific and 10 a.m.

197
00:19:01,120 --> 00:19:01,680
Eastern.

198
00:19:01,740 --> 00:19:06,520
They've actually been given a firmware image that will help them for the upcoming Challenge 3.

199
00:19:07,180 --> 00:19:08,960
Thanks for spending your day with us.

200
00:19:08,960 --> 00:19:14,800
Make sure to check out the rest of what's happening at DEF CON, the Aerospace Village, and our Aerospace Workshops.

201
00:19:14,800 --> 00:19:17,720
And I look forward to seeing you all tomorrow morning at 9 a.m.

202
00:19:17,720 --> 00:19:18,700
Pacific, 12 p.m.

203
00:19:18,700 --> 00:19:20,460
Eastern for our next game update.