[00:17.420 --> 00:22.480] Hey, everybody. Welcome. We're going to get started. If you would take your seats. [00:27.500 --> 00:35.520] Awesome. So, before the actual event you came here to hear about and learn more about and watch happen, [00:35.520 --> 00:40.420] I'm going to do a brief introduction. My name is Steve Leszczynski. Spanky also works. [00:40.420 --> 00:48.140] And I am part of the Aerospace Village. So, we are so happy, proud, you name it, [00:48.140 --> 00:55.520] the fact that we have this village. You all are here. You all are also here because you want to see HackASAT. [00:55.520 --> 01:01.580] It's our fifth year, but we've been partnered with them from the very first DEF CON in 2019 [01:01.580 --> 01:06.800] where we came together as the Aviation Village. The idea grew and now we're the fourth year [01:06.800 --> 01:12.540] and being able to team up with them and, again, having you all come in and see what's happening. [01:12.540 --> 01:17.200] So, please take time. Obviously, take a look at HackASAT. Come by the village. [01:17.200 --> 01:22.500] You got questions? The blue shirts can help you out. But, man, really glad to see this happening [01:22.500 --> 01:28.140] and excited for you all and all the hard work. So, I will pass it off to a fellow, Steve, and you're in good hands. [01:35.520 --> 01:39.640] What's up, everybody? How are we doing today? Awesome. [01:41.900 --> 01:46.940] So, Steve, thank you for that. Appreciate it. We certainly appreciate our partnership here with the Aerospace Village. [01:47.760 --> 01:53.000] Already, since our 9 o'clock start time, we've had two scores on the board in HackASAT 4. [01:53.000 --> 01:56.620] Jordan Wines, our CTF expert, is going to talk to you more about it in a few minutes. [01:56.620 --> 02:03.520] But we were a little bit on pins and needles with a real satellite in the air because this is the first ever CTF in outer space. [02:03.620 --> 02:10.020] But we've made it through that uncertainty and, hopefully, we keep progressing positively throughout the next two days. [02:10.620 --> 02:18.140] So, again, I'm Steve from the Air Force. And a lot of people have asked me, like, why is the Department of the Air Force, [02:18.140 --> 02:22.540] which includes the U.S. Space Force, doing something like hacking a satellite? [02:23.020 --> 02:27.120] And, I mean, it seems like a simple answer to me because we've been on this journey for four years. [02:27.120 --> 02:34.440] But at the end of the day, we wanted to raise the public's awareness, the security researchers' awareness, [02:34.440 --> 02:40.320] and the space experts' awareness to the fact that we care about the security of our space systems. [02:40.380 --> 02:45.260] Certainly, we do as a government, just like every other government, but also for our everyday life. [02:45.260 --> 02:52.960] I mean, what we're doing here today, how a lot of us got here today, all integral to space, working 100% and flawlessly. [02:52.960 --> 03:00.200] And it's super hard. This is why our slogan this year is, practice is over. We have, space is hard, labeled all of our videos. [03:00.200 --> 03:05.980] And the reason for that is because it truly is hard. And a lot of things go wrong, and we're not impacted. [03:05.980 --> 03:11.940] But if they go really wrong because of not enough foresight or not enough forethought into the designs of these systems, [03:11.940 --> 03:15.420] we all sort of are going to be impacted in a negative manner. [03:15.460 --> 03:19.300] So that's what we really wanted to do, is raise awareness with respect to that. [03:19.300 --> 03:22.320] But we also knew that there was some fun to be had. [03:22.480 --> 03:27.480] Everyone was asking, like, when's the Air Force going to do something that's fun instead of just being boring? [03:27.560 --> 03:30.720] So we just said, all right, well, can we do some something in outer space? [03:30.720 --> 03:35.340] Super hard at first, because no one wanted to let us use their satellites, as you probably can imagine. [03:35.340 --> 03:43.880] So what we did is we slowly, we called it the design-build-break sort of methodology of how we eventually developed our Moonlighter satelliter [03:44.540 --> 03:50.260] and launched it, which we'll have one of our Space Force representatives come up and discuss a little bit of the intricacies about it. [03:50.260 --> 03:54.420] We have a real-life replica of it, so the thing flying in outer space right now is that. [03:54.620 --> 03:55.960] It's just a replica. [03:56.480 --> 04:03.800] And we're also going to talk about some game explainers, as well as sort of recap some of our quals and how that went down. [04:03.800 --> 04:05.860] And then what you can see here today. [04:05.860 --> 04:07.780] So there's the history wall over here. [04:07.780 --> 04:08.920] We have what we call a museum. [04:08.920 --> 04:09.840] We have posters. [04:10.000 --> 04:11.540] So please come check it out. [04:11.540 --> 04:22.960] I hope that we've done our job, which is raising the public's awareness of how space systems need to be resilient for the globe to rise, just like the old saying is, a rising tide raises all boats. [04:22.960 --> 04:24.120] So we want to do that. [04:24.120 --> 04:26.800] We want to just come up together, because we all need space. [04:27.180 --> 04:29.980] So with that said, I'm going to show you a history video. [04:30.160 --> 04:32.360] And then some of our other team members are going to come up. [04:32.360 --> 04:41.000] Like I said, Jordan, we have our whole cast of characters that are going to come up and give you some details, along with what you can see around the corner here for the rest of the day and tomorrow. [04:41.260 --> 04:47.840] And also, noon on Sunday, the schedule is all out on the Aerospace Village website, as well as hackasad.com. [04:47.840 --> 04:50.200] We're going to announce the winners. [04:50.520 --> 04:55.080] So there's some intricacies, which Jordan's going to get into, of why we can't score everything right away. [04:55.080 --> 04:57.540] So Sunday, we're going to unveil everything right here. [04:57.540 --> 04:58.900] So it's going to be pretty exciting. [04:58.900 --> 05:02.380] And we might have a special guest potentially do the announcements. [05:02.380 --> 05:07.160] So with that, I'm going to hit the video, and then Rachel's going to come up. [05:13.420 --> 05:16.500] The problem is really quite simple. [05:16.500 --> 05:22.200] Find the best path to get from point A to point B. [05:22.200 --> 05:29.940] The United States Air Force and Space Force had an idea to host a space-based CTF to advance space cybersecurity. [05:29.940 --> 05:33.300] While many were sure it couldn't or shouldn't be done, [05:33.300 --> 05:39.680] in 2020, they launched HackASAT, an educational effort and capture-the-flag style hacking competition. [05:39.680 --> 05:43.420] HackASAT is designed to inspire the global security researcher community [05:43.420 --> 05:50.540] to develop the interest and skills necessary to reduce vulnerabilities and build more secure space systems. [05:50.540 --> 05:52.480] Education has been central. [05:52.480 --> 05:55.140] From testing the public with an open hacking challenge, [05:55.140 --> 05:59.220] to a tough qualification round introducing space-relevant topics and skills, [05:59.220 --> 06:04.380] to a set of hands-on workshops in the virtual aerospace village at DEFCON SafeMode, [06:04.380 --> 06:08.120] to a whole library of resources on space and hacking, [06:08.120 --> 06:13.780] we developed FlatSAT hardware and challenges to give security researchers access and experience [06:13.780 --> 06:17.000] to space technologies they wouldn't have otherwise. [06:17.000 --> 06:22.420] It all led to a fierce final CTF competition for the top eight teams from QWALS, [06:22.420 --> 06:28.480] and the source code for all QWALS and final challenges are available on GitHub for the community to keep learning. [06:28.480 --> 06:32.240] As HackASAT 1 ended, planning started for HackASAT 2. [06:32.240 --> 06:38.980] We enhanced the HackASAT FlatSAT and assembled a new digital twin to support even more realistic space challenges. [06:38.980 --> 06:45.240] The qualification round took place in June 2021, with the top eight teams making it to the final event. [06:45.240 --> 06:50.740] HackASAT brought a full slate of talks and workshops about space security to DEFCON 29, [06:50.740 --> 06:55.260] and the virtual final CTF took place in December 2021. [06:55.260 --> 07:01.480] Challenges were still based on the FlatSAT, but now teams could test their commands within the digital twin simulation. [07:01.480 --> 07:08.200] And again, the source code from QWALS and finals challenges are available on GitHub through our Players Corner page. [07:08.460 --> 07:15.660] As HackASAT 2 ended, planning started for HackASAT 3, and development was already well underway for Moonlighter, [07:15.840 --> 07:19.760] a 3U CubeSat dedicated to furthering space cybersecurity. [07:19.900 --> 07:22.780] Its first mission would be to host HackASAT 4. [07:22.780 --> 07:28.260] We developed the digital twin-based final event to mirror the actual Moonlighter satellite. [07:28.260 --> 07:35.180] And with help from astrophysicist Dr. Hakim Oluseyi, we built an online educational experience for the public to plan, [07:35.180 --> 07:40.000] build, and test their very own 3U CubeSat, just like Moonlighter. [07:40.000 --> 07:43.720] HackASAT 3 QWALS took place virtually in May 2022. [07:43.720 --> 07:49.100] In August, the HackASAT team brought space-relevant talks to Aerospace Village at DEFCON 30. [07:49.100 --> 07:58.860] The finals took place in October of 2022, with 8 teams working through 12 challenges over 23 hours in this attack-defense style CTF. [07:58.860 --> 08:03.220] And again, source code from QWALS and final challenges are available on GitHub. [08:03.660 --> 08:08.640] As Moonlighter moved from design to the build stage, the team went deep into HackASAT 4 planning. [08:08.640 --> 08:15.240] A space-focused CTF is hard to build and play. An on-orbit CTF is even harder, and it's never been done before. [08:15.240 --> 08:27.660] Our qualification round took place April 2023. Moonlighter launched on June 5th and deployed from the International Space Station on July 6th and is now in low Earth orbit. [08:27.740 --> 08:34.720] This is its first mission. Practice is over. The HackASAT 4 final event has begun. [08:36.080 --> 08:40.980] A huge congratulations to the Moonlighter team. Stay in touch and best of luck with operations. [08:48.070 --> 08:52.330] Okay, great. Hi, everybody. I'm Rachel Mann from the Air Force Research Lab. [08:52.330 --> 08:59.110] So just a little bit more background as far as how we got where we are today to have a live event with you all. [08:59.130 --> 09:05.030] So a qualification was held over April Fool's weekend. That was not intentional, but it was April Fool's weekend. [09:05.330 --> 09:08.770] Thank you to anybody that's in here that did compete in that. [09:08.770 --> 09:16.250] We, of course, cannot have a great final event with all the participants that we have here today without a really successful qualification event. [09:16.250 --> 09:21.950] And so this year, over the two-day, 30-hour period, we did a Jeopardy-style competition. [09:21.950 --> 09:27.390] We did have over 700 teams. Over 58 countries are represented across those teams. [09:27.410 --> 09:33.050] We did have 28 challenges with one left unsolved, which I think is kudos to our challenge development team. [09:33.050 --> 09:37.450] We keep things interesting and make it fun but challenging. [09:37.450 --> 09:42.130] So the top eight teams this year were able to get $10,000 in cash prizes. [09:42.130 --> 09:48.510] You will notice a change from this year to last year is that we only brought five teams to finals today. [09:48.550 --> 09:52.790] Of course, why did we have to make that change after doing it that way for three years? [09:52.790 --> 09:55.770] It is, of course, because of the satellite that's in orbit. [09:55.770 --> 10:07.430] To keep this game interesting, to keep it fun, challenging, but still fair, we felt that bringing five teams to finals was the best way to encourage the use of the satellite [10:07.430 --> 10:12.910] without any unfairness, any issues with the satellite, and teams not being able to use it. [10:12.910 --> 10:17.150] Five was kind of our prime number versus the eight that we've done in years past. [10:17.150 --> 10:20.290] So that was intentional. It did take a lot of thinking on our part. [10:20.330 --> 10:26.310] The decision, of course, was not made quickly, but I think we're happy with the way that we are going forward. [10:26.310 --> 10:28.270] And so far, so good. [10:30.570 --> 10:31.370] Kevin. [10:31.370 --> 10:41.370] All right. Good morning, everyone. I'm Captain Kevin Burnett from the U.S. Space Force. [10:41.370 --> 10:44.730] I'm one of the Space System Command sponsors for this program. [10:44.790 --> 10:52.130] Like Steve had mentioned, when this program was originally starting out, we wanted to see if we can get someone to let us use their satellite and let y'all hack it. [10:52.130 --> 10:54.070] We were met with a resounding no. [10:54.070 --> 10:58.410] So we decided to start building up our very own satellite, never say never. [10:58.410 --> 11:04.830] So it took us a little under two years from start to finish, which is really fast for satellite development. [11:04.830 --> 11:12.950] But earlier this year, in April, we delivered the Moonlighter space vehicle after it was all finished up to the integrator. [11:12.950 --> 11:20.910] So space integrators are the ones in charge of making sure that your vehicle or your space vehicle will fit onto the launch vehicle itself. [11:20.910 --> 11:29.710] And so in June of this year, it was attached to the SpaceX 28 rocket, which was a commercial resupply mission to the ISS. [11:29.710 --> 11:34.370] So it was taking food, water, resources, science missions, upgrades to the ISS. [11:34.950 --> 11:37.430] And it didn't really take long to get there. [11:37.430 --> 11:44.590] But it hung out on the ISS for about a month before an astronaut went and loaded it onto the airlock system. [11:44.590 --> 11:50.170] And then a robotic arm went and grabbed the satellite and essentially just pointed it out and shot it off into orbit. [11:50.170 --> 11:52.610] And we have some cool footage of that as well. [11:52.910 --> 11:57.970] So like I said, Moonlighter, this is a full-scale model of it, a one-for-one model. [11:57.970 --> 12:03.330] So it's pretty small. It's what's called a 3U CubeSat, which is how they measure smaller satellites. [12:03.330 --> 12:06.090] So it's about 30 centimeters by 10 by 10. [12:06.370 --> 12:11.750] But as our computers and everything gets smaller but still more powerful, this does as well. [12:11.750 --> 12:19.290] So it has all the stuff that's on a satellite, because it is a satellite, and it has its solar panels right now unfolded. [12:19.290 --> 12:22.150] But I think we have some cool footage to show you as well. [12:22.150 --> 12:29.830] These are some different angles. That middle one is just a picture of the solar panels in a stowed position. [12:29.830 --> 12:37.850] So once you get it released from the ISS, after a while you're able to get those opened up just to make sure your battery life lasts a little bit longer. [12:38.290 --> 12:48.050] And also we have amazing displays over in the next room as well in our contest area, and a lot more people to answer more in-depth questions. [12:48.940 --> 12:56.490] So again, for liftoff, we launched June 5th aboard the SpaceX Commercial Resupply Mission bound for the ISS. [13:01.260 --> 13:02.940] Thank you, NASA. [13:08.940 --> 13:13.110] So there it is in Florida at the Kennedy Space Center. [13:20.920 --> 13:21.970] Liftoff. [13:23.880 --> 13:27.880] And liftoff of CRS-28, go Falcon, go Dragon. [13:42.510 --> 13:45.590] About two minutes, 40 seconds after you have separation. [13:49.160 --> 13:53.040] And then it goes and docks onto the International Space Station. [13:53.040 --> 13:56.380] So space is hard, as Steve Colenso had mentioned. [13:56.700 --> 14:01.680] One of the main reasons is coordinating, working with your launch provider and getting it in space. [14:01.680 --> 14:06.480] I'm sure you've all heard of space launches getting scrubbed due to weather or technical difficulties. [14:06.480 --> 14:07.600] Well, the same thing happened to us. [14:07.600 --> 14:12.660] We had a lot of our team there at the beginning waiting for a launch, only for it to be aborted very shortly after. [14:12.800 --> 14:16.380] And so we came back the next day, but some people had to go home, and it got scrubbed again. [14:16.380 --> 14:18.480] And we waited the next day, but then we had success. [14:18.480 --> 14:23.120] So we were able to have some boots on the ground and get some good footage of that as well. [14:23.120 --> 14:29.180] But just the coordination with space vehicles, although space is much more proliferated than it was even a year ago, [14:29.180 --> 14:38.260] you still obviously run into those issues, because the price is too high for you to take any risks that are not negotiable by waiting just one other day. [14:38.260 --> 14:44.640] But we also have some cool footage of when the Moonlighter vehicle was deployed from the International Space Station. [14:44.640 --> 14:47.720] Because a lot of the times your rocket will take you directly into your orbit, [14:47.720 --> 14:52.620] but like I said, this is a unique opportunity to get Moonlighter into the orbit that we needed it to be. [14:52.620 --> 14:55.660] So again, it was about a month later that we deployed from the ISS. [14:59.160 --> 15:01.200] Follow along closely, because it's about to shoot. [15:01.200 --> 15:04.540] 3, 2, 1, mark. [15:06.020 --> 15:06.960] There it goes. [15:09.940 --> 15:13.220] And it tracks it a little bit. You'll be able to see it, I think, in the top left corner. [15:13.220 --> 15:14.320] Yep, there it is. [15:16.420 --> 15:17.740] There's real footage. [15:18.100 --> 15:19.500] The Earth is round. [15:19.560 --> 15:20.940] There it is, the curvature. [15:21.820 --> 15:22.860] There's the ISS. [15:22.860 --> 15:26.100] So it took a selfie, so you can tell that it also came off the ISS. [15:27.700 --> 15:31.240] It also shows you how fast Moonlighter really is going around Earth. [15:31.240 --> 15:37.760] So things in LEO at that specific orbit rotate around the entire Earth in only an hour and a half. [15:37.760 --> 15:45.560] So it's moving at 17,000 plus or minus 100 miles per hour, about 5 miles per second. [15:47.660 --> 15:52.640] And later on, we'll get into more details about why that makes it challenging, [15:52.640 --> 15:56.460] but also more fun for our ground stations to contact Moonlighter. [15:56.460 --> 16:00.780] Congratulations to the Moonlighter team. Stay in touch and good luck with the operations. [16:01.080 --> 16:06.100] But it's real. We're up there now, on orbit, as we speak, it's still going over. [16:06.360 --> 16:11.300] Moonlighter has a shelf life of about a year and a half before gravity eventually pulls it down [16:11.300 --> 16:14.120] and it fizzles off into a shooting star. [16:15.740 --> 16:19.260] So you're probably wondering, though, how we're able to even do a CTF, [16:19.260 --> 16:23.840] not just on the ground, but on space, on a space vehicle that's going so fast. [16:23.840 --> 16:26.880] And so here's a video that will help shed some light on that. [16:44.980 --> 18:56.800] To meet the great challenges of our age, here on Earth and beyond the Earth, in space. [18:56.800 --> 19:03.260] Good morning, everyone. I'm Jordan Wines, or Cyphertex, and I'm the sort of CTF sideline reporter for HackASAT. [19:03.260 --> 19:06.900] By day, I work on a reverse engineering tool called Binary Ninja, [19:06.900 --> 19:10.600] and then at night, I play Capture the Flags, or commentate them, talk about them, [19:10.600 --> 19:15.180] and I've been lucky to be part of HackASAT now for about four years. [19:15.400 --> 19:18.380] I kind of want to talk a little bit, first, how many people here know what a Capture the Flag is? [19:18.380 --> 19:21.780] I assume most people do, you're here in the room, but just, you know, [19:21.780 --> 19:24.600] the idea is that you're hacking systems in a legal manner, [19:24.600 --> 19:28.860] and the flags are usually just kind of code, or proof, or triggers, or something that you've shown [19:28.860 --> 19:31.380] you've violated some security kind of principle. [19:31.380 --> 19:35.020] So in the Capture the Flag community, we have a couple of different styles of events. [19:35.020 --> 19:39.200] We have ones that are called attack defense, which is what's happening over at DEFCON CTF right now, [19:39.200 --> 19:42.440] just over the way, where there are 12 teams there attacking each other [19:42.440 --> 19:44.660] while they're defending against their same system. [19:44.660 --> 19:47.500] And we've done that, for example, last year at HackASAT, [19:47.900 --> 19:50.160] there have been teams, each with their own infrastructure, [19:50.160 --> 19:53.240] that everyone else was attacking and defending at the same time. [19:53.320 --> 19:57.720] We tried to get the Space Force and Air Force to let us launch five satellites, [19:57.720 --> 20:00.440] and unfortunately, there wasn't budget, apparently, for that. [20:00.440 --> 20:05.840] So we've got one flat sat that's up in space with Moonlighter right now. [20:05.920 --> 20:11.880] And so this year, in the fourth year, the final event is not going to be this attack defense kind of competition. [20:11.880 --> 20:19.760] It has more of what we call either a Jeopardy style, or a red team CTF, where it's pure attack. [20:19.760 --> 20:22.560] So each team is just trying to attack, and solve, and score, [20:22.560 --> 20:26.340] and they're working their way through the different challenges to get their points. [20:26.340 --> 20:29.500] As mentioned in the game explainer, there's no SLA, [20:29.500 --> 20:32.860] so obviously in a commercial environment, SLA is service level agreement. [20:32.860 --> 20:34.600] It's just, did you keep your servers up? [20:34.640 --> 20:38.380] Because it's pretty boring when you play a CTF and you just turn the server off. [20:38.560 --> 20:45.180] You're secure, ta-da, and so most CTFs will require you to maintain the services that you're running [20:45.180 --> 20:48.060] for other people to attack, but again, since we're not doing attack defense, [20:48.060 --> 20:49.740] that's less of a concern this year. [20:49.780 --> 20:52.380] In years past, for example, teams had to worry about battery life, [20:52.380 --> 20:54.640] and actually maintain their satellite themselves. [20:54.960 --> 20:58.180] We didn't want to let them mess that up this year on a real satellite, right? [20:58.180 --> 21:01.460] So there's one satellite, it's being maintained, the operations, the battery level, [21:01.460 --> 21:04.700] all that's being maintained by the game, the satellite operations teams, [21:04.700 --> 21:07.200] and so they're kind of managing that part of it. [21:07.200 --> 21:10.580] But the cool part is, this is the first capture the flag in space. [21:10.580 --> 21:13.700] There is code that is running on that satellite from our teams [21:13.700 --> 21:16.140] that's going to be solving these challenges. [21:16.140 --> 21:18.940] So let's talk a little bit about what the game infrastructure kind of looks like. [21:19.520 --> 21:25.080] We've got this kind of overall picture here of, it's a little bit small there, [21:25.080 --> 21:27.460] but on the bottom left, though, you can see there's our five teams [21:27.460 --> 21:32.060] that are starting here on the ground floor in Vegas. [21:32.100 --> 21:33.380] It's also really nice, by the way. [21:33.380 --> 21:35.860] We've been playing this now for, this is the fourth year we've had this event. [21:35.860 --> 21:38.220] This is the first time we could see the teams face-to-face. [21:38.240 --> 21:39.280] So that's actually really cool. [21:39.280 --> 21:41.840] We're really excited to finally be able to meet people. [21:42.060 --> 21:43.780] It was the beginning of the pandemic when it first hit, [21:43.780 --> 21:46.220] and we switched from planning to come to DEF CON, [21:46.220 --> 21:48.920] planning to do this event in person, to having to do it all virtually. [21:48.920 --> 21:51.000] So it's great to kind of finally be here. [21:51.000 --> 21:54.160] So we've got those five teams, and again, as Rachel mentioned, [21:54.160 --> 21:57.240] you can't have like eight teams competing for a very small number [21:57.240 --> 21:59.240] of kind of like satellite communication windows, [21:59.240 --> 22:02.680] so we've pared down the final set of teams to these teams. [22:02.680 --> 22:04.760] It also meant that if they qualified for DEF CON CTF, [22:04.760 --> 22:06.940] they didn't have to decide if they were going to split their team [22:06.940 --> 22:08.540] or if they were going to do both at the same time, [22:08.540 --> 22:10.560] if there were fewer teams in the finals. [22:11.100 --> 22:13.260] They're talking to this tasking API. [22:13.260 --> 22:16.060] This tasking interface API is just an HTTP interface [22:16.060 --> 22:18.240] that they can now submit their code to, right? [22:18.240 --> 22:21.180] So every operation that they send, they package up, [22:21.180 --> 22:24.480] they send to this API, and that can include commands, [22:24.480 --> 22:26.720] it can include requests for telemetry, [22:26.720 --> 22:27.900] include a scripting interface. [22:27.900 --> 22:32.200] There's all these operations that they can do using that API. [22:32.200 --> 22:33.880] That goes into a validation step. [22:33.880 --> 22:36.220] So the game infrastructure people do some amount of validation [22:36.220 --> 22:38.220] to make sure this stuff is well-formed, [22:38.220 --> 22:40.620] it's not going to cause anything super crazy to happen. [22:40.620 --> 22:42.320] Like, there is hacking, and that's intentional, [22:42.320 --> 22:45.540] but there's also things that could maybe be a bad idea to do. [22:45.540 --> 22:48.900] And so there's some, like, does it pass sort of, [22:48.900 --> 22:49.780] like, is it well-formed data? [22:49.780 --> 22:52.220] Is it going to actually do something like construct, [22:52.220 --> 22:54.260] or is it actually going to do the task that they're trying to do? [22:54.380 --> 22:56.640] Well, we don't tell them for sure if they're going to solve it or not, [22:56.640 --> 22:59.600] but we at least can validate the structure of the requests. [22:59.740 --> 23:01.220] That goes to the command scheduler. [23:01.220 --> 23:03.740] And between the command scheduler there, then, and the ground network, [23:03.740 --> 23:07.780] that's actually, it goes off to a commercial satellite operations company [23:07.780 --> 23:10.420] that has ground stations throughout the world. [23:10.420 --> 23:12.660] And so there's four different ground stations in use. [23:12.740 --> 23:15.720] You'll see that this ground network kind of has that little L-shaped bend [23:15.720 --> 23:17.500] because there's these two phases [23:17.500 --> 23:20.040] that the ground station's going to be activated in, right? [23:20.040 --> 23:22.660] On the uplink request, when the code gets, [23:22.660 --> 23:26.220] when the requests get uploaded to the server, [23:26.220 --> 23:27.880] see, I'm so used to playing with the CTF, [23:27.880 --> 23:29.360] to the satellite, right? [23:29.360 --> 23:32.620] When the code gets uploaded to it, that's going to happen during that uplink. [23:32.780 --> 23:34.460] And then it's going to have the next, [23:34.460 --> 23:37.620] between the next windows of communication, [23:38.020 --> 23:39.400] the code's going to be running, right? [23:39.400 --> 23:41.760] So the payloads are all going to be running on the satellite [23:42.320 --> 23:45.340] as the teams each try to solve their challenges. [23:45.340 --> 23:47.900] You can see then on the bottom right there, [23:47.900 --> 23:49.800] Moonletter itself has a lot of components [23:49.800 --> 23:52.120] that are typical of a satellite, right? [23:52.120 --> 23:54.400] It's got an imager, it's got GPS, [23:54.400 --> 23:56.500] it's got ADCS, [23:56.500 --> 23:58.360] it's attitude, oh, I always forget, [23:58.360 --> 24:01.780] attitude determination control system. [24:01.780 --> 24:03.900] See? This is why we had the space people around. [24:03.900 --> 24:05.820] I'm just the CTF guy. [24:06.220 --> 24:08.480] And that's essentially the orienting, right? [24:08.480 --> 24:11.340] It's the ability to, like, move and locate where are you [24:11.340 --> 24:13.600] and position, well, sorry, [24:13.600 --> 24:15.800] move is the thing I have to be careful of saying, right? [24:15.800 --> 24:18.000] Because there is no propulsion on this. [24:18.000 --> 24:20.740] These little flatsats are just floating around, [24:20.740 --> 24:22.480] they have the solar panels for, like, [24:22.480 --> 24:23.840] maintaining their onboard systems, [24:23.840 --> 24:26.060] and they have some gyroscopic orientation. [24:26.120 --> 24:28.560] So they have these, like, I guess they're similar to flywheels, [24:28.560 --> 24:30.060] at least as I understand, they can kind of, like, [24:30.060 --> 24:33.440] use to, like, orient and move it in 3D space [24:33.440 --> 24:35.100] so they can change the axes, [24:35.100 --> 24:36.380] but they're just pointing, right? [24:36.380 --> 24:37.920] Which makes sense if you've got that imager [24:37.920 --> 24:39.860] and you want to be able to take a picture of something, [24:39.860 --> 24:41.520] well, you have to aim at what you're pointing at. [24:41.520 --> 24:44.080] So that's how they do that with that ADCS system. [24:44.080 --> 24:45.860] So these are, again, all kind of typical components [24:47.220 --> 24:50.340] of many satellites, commercial and otherwise. [24:50.700 --> 24:53.460] And so it executes the commands, [24:53.460 --> 24:56.320] it's going to run through each team's requests, [24:56.320 --> 24:57.920] and then that data is going to come back down [24:57.920 --> 24:59.820] through the ground station network. [24:59.820 --> 25:01.960] And you notice that we showed that as a different satellite dish [25:01.960 --> 25:03.700] because these are different windows, right? [25:03.700 --> 25:05.520] You don't, like, you upload your request [25:05.520 --> 25:06.840] and then you have to wait until the next window [25:06.840 --> 25:09.240] before you get the results as they come back down. [25:09.240 --> 25:11.460] And that telemetry data, the results that come back, [25:11.460 --> 25:12.700] if there's code that they ran, [25:12.700 --> 25:14.400] and the teams are going to get all that information, [25:14.400 --> 25:16.900] and the data comes back over there. [25:18.960 --> 25:22.740] There are nine challenges, [25:22.740 --> 25:25.380] two of which happened on the ground station, [25:25.380 --> 25:28.800] and seven of which happened in space, right? [25:28.800 --> 25:31.460] So the majority of the game is actually happening [25:31.460 --> 25:33.500] on code that runs on Moonlighter. [25:33.500 --> 25:35.480] So they've got to, like, run their payloads, [25:35.480 --> 25:36.720] they've got to get that up in space. [25:36.720 --> 25:38.400] This is what this is actually going to look like. [25:38.400 --> 25:39.760] These communication windows [25:39.760 --> 25:43.140] that teams are actually sending their request to [25:43.140 --> 25:44.960] throughout these two weekends. [25:45.060 --> 25:46.640] And this is really important to point out [25:46.640 --> 25:48.900] that we didn't even know, as the sort of organizers [25:48.900 --> 25:51.480] in putting this on, exactly what these communication windows [25:51.480 --> 25:52.240] were going to look like [25:52.240 --> 25:54.740] until just about the week before the event, right? [25:54.740 --> 25:56.060] So it's really the last minute [25:56.060 --> 25:58.560] because you're waiting for the... [25:58.560 --> 26:00.480] Again, I don't understand the space physics [26:00.480 --> 26:02.460] or how it exactly works, but you actually don't necessarily know [26:02.460 --> 26:04.420] exactly where your orbit's going to be [26:04.420 --> 26:07.960] at exactly what time at a far enough out period. [26:07.960 --> 26:09.640] And so we had to kind of figure out [26:10.140 --> 26:11.780] where we could talk to it, even. [26:11.780 --> 26:13.840] And it impacted how you design challenges. [26:13.840 --> 26:15.780] Do you have, for example, one challenge [26:15.780 --> 26:17.360] that gates another challenge or not? [26:17.360 --> 26:19.880] Is something you would normally design and do a capture-the-flag? [26:19.900 --> 26:21.260] But we had to build that in with... [26:21.260 --> 26:23.560] Again, you'll notice there's very few contact windows [26:23.560 --> 26:25.300] on the next day, for example. [26:25.300 --> 26:27.520] So tomorrow, there's just very few opportunities [26:27.520 --> 26:29.200] to talk to the FlatSat. [26:29.200 --> 26:31.400] And so they've got a lot of opportunities today, [26:31.400 --> 26:33.640] they've got overnight, and then we've got tomorrow [26:34.320 --> 26:35.780] Each one of these windows, if you look, [26:35.780 --> 26:37.440] there's sort of like door frame or window [26:37.440 --> 26:39.700] is the window, right? The little white arch. [26:40.060 --> 26:41.440] And that's just showing, that's the period of time [26:41.440 --> 26:43.040] where we're able to uplink and downlink data [26:43.040 --> 26:45.060] from the satellite. [26:45.120 --> 26:47.380] Well, triangle is indicating that the teams [26:47.380 --> 26:49.900] have to have all of their requests queued in [26:49.900 --> 26:51.940] to be validated to go to the command queue [26:52.440 --> 26:53.920] before that window itself, right? [26:53.920 --> 26:56.220] So there's like a hard cutoff, the teams have to have everything in. [26:56.300 --> 26:57.600] Then we have the communication window. [26:57.600 --> 26:59.700] Then it goes off and executes the payloads [26:59.700 --> 27:01.660] and we get the results back in the next window. [27:01.660 --> 27:03.020] If all goes to plan. [27:03.020 --> 27:04.580] There's a lot of things that can happen. [27:04.580 --> 27:06.840] Actually, overnight last night, when the game [27:07.460 --> 27:08.920] competition team was running tests, [27:08.920 --> 27:10.580] they actually had some windows that were corrupted [27:10.580 --> 27:11.940] because of RF interference. [27:11.940 --> 27:14.860] It just happens that you don't get a good command window [27:14.860 --> 27:16.300] because of who knows what [27:17.840 --> 27:19.800] interrupted the communication link. [27:19.800 --> 27:21.520] And so this is, again, we're talking about [27:21.520 --> 27:23.580] space is hard, there's just all these real world [27:23.580 --> 27:26.060] concerns that can come in and impact [27:27.100 --> 27:28.820] how the communications happen [27:28.820 --> 27:30.360] and how much availability you have. [27:30.360 --> 27:31.460] So this is really, you know, [27:31.460 --> 27:33.820] it's a lot to kind of fit into this [27:34.660 --> 27:37.040] weekend competition, capture the flag style event. [27:37.240 --> 27:38.200] You'll see that the [27:38.200 --> 27:40.460] red line there on the bottom that shows [27:40.460 --> 27:42.320] up tomorrow and kind of overnight, [27:42.760 --> 27:44.240] that's actually where they're going to be doing [27:44.240 --> 27:45.860] the pointing and imaging missions, right? [27:47.900 --> 27:48.620] Because the [27:48.620 --> 27:50.640] flat set isn't always sort of engaged [27:50.640 --> 27:52.300] in terms of moving, actually the default state is [27:52.300 --> 27:54.260] kind of a tumble. It's only when you need to [27:54.260 --> 27:55.880] activate it and use it and point it [27:55.880 --> 27:58.520] and use the orientation [27:58.520 --> 28:01.000] mechanisms that it's kind of under control. [28:01.100 --> 28:02.580] And so there's this window that [28:02.580 --> 28:04.560] occurs kind of overnight where those [28:04.560 --> 28:06.680] imaging tasks, again, there's some of these challenges [28:06.680 --> 28:08.180] that they're going to have to do involve pointing [28:09.400 --> 28:10.680] the flat set and taking [28:10.680 --> 28:12.420] pictures of particular locations. [28:12.880 --> 28:14.720] There's even a fun one where they're [28:14.720 --> 28:16.480] required to take a picture at a location [28:16.480 --> 28:18.780] that's actually off limits, which I think is [28:18.780 --> 28:19.960] super cool. [28:20.280 --> 28:22.480] Off limits being just arbitrary locations. [28:22.480 --> 28:24.700] I mean, we'll see if they try to take pictures [28:24.700 --> 28:27.020] of some secret things, [28:27.020 --> 28:28.900] but the resolution of the camera is not [28:28.900 --> 28:31.080] particularly good, so I don't think [28:31.080 --> 28:32.740] we have to worry too much about that. [28:32.820 --> 28:34.960] So again, the game ends from the player's perspective [28:34.960 --> 28:36.960] in terms of the commands they're sending tomorrow [28:36.960 --> 28:39.440] at about 6pm, right, and there's that last window. [28:39.700 --> 28:41.020] But then there are several more there [28:41.020 --> 28:42.960] and even overnight where we're waiting [28:42.960 --> 28:44.920] for more data to come back. It's possible, again, [28:44.920 --> 28:46.960] that some of the windows we don't get the full [28:46.960 --> 28:48.940] downloads or maybe there's a lot of data backed up [28:48.940 --> 28:50.900] and we're waiting for it to all download, and so it's going to [28:50.900 --> 28:52.840] take a little bit, and this is why we say come back [28:52.840 --> 28:55.080] on Sunday and we'll get the [28:55.080 --> 28:56.340] full kind of update [28:57.060 --> 28:58.260] of what's happened [28:58.900 --> 29:00.520] as we've been able to kind of tally up [29:00.520 --> 29:02.560] and see how teams did. [29:03.400 --> 29:05.120] And speaking of the teams... [29:05.120 --> 29:07.160] Oh, wait. Oh, that's right. I forgot. This is the good one. [29:07.160 --> 29:08.800] So this is the actual breakdown where you can see [29:10.280 --> 29:11.160] each team [29:11.160 --> 29:12.820] has a sort of time slice [29:12.820 --> 29:15.640] of the window where their code's going to be run, [29:15.640 --> 29:17.420] and there's several different actions they can do. [29:18.440 --> 29:19.900] There's a scripting, [29:19.900 --> 29:22.020] there's a downlinking, [29:22.020 --> 29:23.380] and then there's an [29:23.380 --> 29:25.120] imaging kind of like section, [29:25.120 --> 29:26.640] actions that they can take. [29:27.140 --> 29:28.900] There's several different things they can do with that. [29:28.900 --> 29:30.460] It's like an actual scripting language [29:30.460 --> 29:32.980] and it's actually a Lua interface [29:32.980 --> 29:35.400] that's running on the flat site [29:35.400 --> 29:37.360] and so they're uploading this code that's actually going to be [29:37.360 --> 29:38.880] executed there. [29:39.440 --> 29:41.580] And you'll see each team changes though. [29:41.580 --> 29:43.340] So the colors of the team is unique to [29:43.340 --> 29:45.640] each of our five finalist teams, [29:45.640 --> 29:47.360] but it's different per pass. [29:47.360 --> 29:49.540] We randomize it up so that it's sort of fair. [29:49.540 --> 29:51.300] So if you went first in one pass, [29:51.300 --> 29:53.820] you'll go in a different spot in a later pass. [29:53.820 --> 29:55.480] And not all teams may take all actions [29:55.480 --> 29:57.340] every window, right? If they're not ready or if they don't have [29:58.140 --> 29:59.260] a thing that they want to attempt [29:59.260 --> 30:01.440] or they haven't solved a particular challenge and figured out what they need [30:01.440 --> 30:03.320] to do yet, maybe we have [30:03.440 --> 30:04.920] a couple go by where nothing is happening [30:04.920 --> 30:07.380] or maybe only a few teams do. [30:07.980 --> 30:09.320] Alright, so now speaking [30:09.320 --> 30:11.300] of the teams, let's talk about the teams [30:11.300 --> 30:13.240] themselves that are here. It's really [30:13.240 --> 30:14.960] cool to me that these have been [30:15.560 --> 30:17.220] five teams that have all [30:17.220 --> 30:19.100] got a long history now with the last [30:19.100 --> 30:21.240] four years that we've been running HackASat. [30:22.640 --> 30:23.220] Tremendous amount [30:23.220 --> 30:24.980] of placements and qualifiers [30:24.980 --> 30:27.040] and finalists. And so [30:27.040 --> 30:29.160] it's really cool that, again, the goal of this event as a whole [30:29.160 --> 30:31.680] was to increase interest, education. [30:31.720 --> 30:33.060] It's to help the [30:33.060 --> 30:35.060] Capture the Flag, the cybersecurity, the information security [30:35.060 --> 30:37.300] community engage with [30:37.300 --> 30:39.180] these new systems, right? There's a lot [30:39.180 --> 30:40.640] of unique constraints and unique [30:41.240 --> 30:43.220] things with the platform that they're running on. [30:43.400 --> 30:45.460] And we're going to go in order of their qualifications. [30:45.460 --> 30:46.940] So again, the qualifiers that was held [30:46.940 --> 30:49.000] on April 1st weekend. This was [30:49.000 --> 30:50.940] the first place team, which was CroutSat. They're [30:50.940 --> 30:53.060] actually a mostly German team. They've got a couple [30:53.060 --> 30:55.020] of Europeans as well. They've actually [30:55.020 --> 30:56.780] been participating in all four years [30:56.780 --> 30:58.820] of HackASat. And [30:59.280 --> 31:01.100] they've actually been in the finals [31:01.100 --> 31:02.920] now twice. They were [31:02.920 --> 31:05.000] first in Quals this year, which is like a good sign [31:05.000 --> 31:06.700] so they're kind of like on an upward trend. [31:06.940 --> 31:08.920] I think it's interesting to talk about them in [31:08.920 --> 31:11.040] particular because CroutSat [31:11.040 --> 31:13.040] and SourCloud, which [31:13.040 --> 31:14.920] is actually playing over in DEF CON CTF right now, are [31:14.920 --> 31:17.140] kind of like paired teams. They're part of the same [31:17.140 --> 31:19.040] CTF ecosystem. And this [31:19.040 --> 31:21.040] is sort of one of a couple of different CTF [31:21.040 --> 31:22.820] megateams, where there are several [31:22.820 --> 31:24.940] Capture the Flag teams that form up, oftentimes [31:24.940 --> 31:26.500] along national boundaries or other [31:26.500 --> 31:28.640] friend groups or colleges, and they'll [31:28.640 --> 31:30.660] have several different smaller teams that come together [31:30.660 --> 31:32.840] to form one team. [31:32.840 --> 31:34.520] And so you'll see this is our sort of German [31:34.520 --> 31:36.900] representatives of a CTF [31:36.900 --> 31:38.900] megateam. The second place team at [31:38.900 --> 31:40.880] the qualifiers was mHackeroni, [31:40.880 --> 31:43.000] an Italian sort of megateam. [31:43.000 --> 31:44.780] So they've got a number of [31:46.940 --> 31:47.720] folks on their team [31:47.720 --> 31:49.000] come from a number of different [31:49.000 --> 31:51.420] backgrounds. They've got a lot of academics, a lot of students, [31:51.420 --> 31:53.100] professors, researchers, as well [31:53.100 --> 31:54.240] as a lot of commercial engineers [31:56.740 --> 31:57.460] like tech [31:57.460 --> 31:59.200] companies, security people. And then they pulled [31:59.200 --> 32:00.480] in for [32:01.960 --> 32:03.180] in particular for [32:03.720 --> 32:05.200] Hackasat, they pulled in some folks [32:05.200 --> 32:07.180] that knew the space stuff, right? [32:07.180 --> 32:08.900] To learn how to do satellite operations, to learn [32:08.900 --> 32:10.820] some of those details. [32:11.680 --> 32:12.920] They claim that they [32:12.920 --> 32:15.060] do have one weakness, so don't [32:15.060 --> 32:16.960] tell the other teams, but [32:16.960 --> 32:18.820] if you deliver them pizza with pineapple [32:18.820 --> 32:20.900] on it, it's apparently their kryptonite. [32:21.240 --> 32:22.980] It's mHackeroni, so pepperoni [32:22.980 --> 32:25.260] only apparently, I guess is how that goes. [32:26.000 --> 32:26.660] But we'll see [32:26.660 --> 32:28.960] how they do. And again, they're one of the other teams [32:28.960 --> 32:30.420] along with [32:32.720 --> 32:33.180] Crowdsat [32:33.180 --> 32:34.980] that are kind of jointly playing [32:34.980 --> 32:37.260] on the CTF finals over in DefCon CTF [32:37.260 --> 32:38.960] and Hackasat at the same time. So [32:38.960 --> 32:40.760] these are large teams, they have large groups of people [32:40.760 --> 32:42.900] to even be able to split up and [32:42.900 --> 32:44.900] work sort of both of these events at the same time [32:44.900 --> 32:46.900] because they take a lot of energy and a lot of [32:46.900 --> 32:49.400] focus. SpaceBitsRUs [32:49.400 --> 32:51.020] is unlike the sort of CTF [32:51.020 --> 32:53.100] mega teams we saw from the last [32:53.100 --> 32:54.940] two, is actually one organization. [32:54.940 --> 32:56.840] So this is Northrop Grumman, they're primarily from the [32:56.840 --> 32:58.940] US and the UK, it's a defense [32:58.940 --> 33:00.960] contractor. What's interesting though [33:00.960 --> 33:03.120] is that they still have this sort of mixture of [33:03.120 --> 33:04.860] like backgrounds and experiences just [33:04.860 --> 33:07.000] in a very large company, right? So they could go find [33:07.000 --> 33:09.140] somebody who has satellite ops experience, [33:09.140 --> 33:11.480] they could find people with security, with reverse engineering, [33:11.480 --> 33:13.020] with data science, whatever [33:13.020 --> 33:15.100] skill sets that they needed, you know, [33:15.100 --> 33:17.000] physicists, and they could pull all those people [33:17.000 --> 33:18.540] into like one team. [33:18.720 --> 33:20.720] And they've formed that. They've actually been [33:21.300 --> 33:23.160] playing again for all four years. What I think is [33:23.160 --> 33:25.080] cool though is that they've like, they did much [33:25.080 --> 33:27.120] worse the first couple of years, they were very low in the rankings [33:27.120 --> 33:28.860] and they've really improved and increased [33:28.860 --> 33:31.000] and done super, super well. In fact, they were [33:31.000 --> 33:32.600] second place in the finals last year. [33:32.600 --> 33:34.920] So they've really come along, you can tell that [33:34.920 --> 33:36.880] they've built up the team, they've been learning [33:36.880 --> 33:39.100] in this space and done super [33:39.100 --> 33:39.760] well. [33:41.440 --> 33:42.940] The next team is the [33:42.940 --> 33:44.780] one to watch for though. They were only fourth [33:44.780 --> 33:46.600] in the qualifiers this year [33:46.600 --> 33:49.220] but Poland Can Into Space [33:49.220 --> 33:51.260] which is a [33:51.260 --> 33:53.040] play on words from the Country Balls comic. [33:53.040 --> 33:55.200] If you go look on the, like a webcomic [33:55.200 --> 33:57.520] Country Balls, there's a joke about Poland [33:57.520 --> 33:59.420] can't, like Poland can't get [33:59.420 --> 34:01.360] into space. And they're like, yes we can. And their [34:01.360 --> 34:02.620] code is indeed going to be running in space [34:02.620 --> 34:04.560] this year, so I would say that they [34:04.560 --> 34:06.740] certainly can. They're primarily made up of [34:06.740 --> 34:08.540] two Polish, primarily [34:08.540 --> 34:10.660] Polish CTF teams, Dragon [34:10.660 --> 34:12.640] Sector and P4. They're [34:12.640 --> 34:14.600] very, very strong capsule, like traditional [34:14.600 --> 34:16.540] kind of capsule flag teams and they've been [34:16.540 --> 34:18.560] dominant in Hackasat over [34:18.560 --> 34:20.480] the years. This fourth place qualifying [34:20.480 --> 34:22.380] that they had this year is actually their lowest [34:23.080 --> 34:24.620] result they've had. They've been first [34:24.620 --> 34:26.640] or second in every quals and every [34:26.640 --> 34:28.920] finals we've had in the past three years. [34:28.920 --> 34:30.560] Last year was the first time they got a final, the first [34:30.560 --> 34:32.420] place in the finals. But again, they've just [34:32.420 --> 34:34.560] consistently done extremely well. [34:34.820 --> 34:36.480] And so it's not a surprise that [34:36.480 --> 34:38.520] we're seeing them here at finals. If I had [34:38.520 --> 34:40.700] to pick, put some Vegas odds [34:40.700 --> 34:42.480] on it, they would be a hard one to beat. [34:42.480 --> 34:44.520] So definitely keep an eye on them as [34:44.520 --> 34:46.820] we see how they score throughout the weekend. [34:48.660 --> 34:50.440] Finally, our last qualifying team [34:50.440 --> 34:53.240] is JumpFS RCX. [34:53.280 --> 34:54.660] I actually decoded the opcode [34:54.660 --> 34:56.460] at first when I first saw the team name. I'm like, okay [34:56.460 --> 34:58.500] it's 0xFF64 [35:00.600 --> 35:01.000] 64FF21 [35:01.000 --> 35:02.500] and I was trying to decode [35:02.500 --> 35:04.660] the bits, like what does it mean? And then I was like, oh no, [35:04.660 --> 35:07.040] it's PFS and RCX. [35:07.040 --> 35:08.540] The logo makes it obvious. So they found [35:08.540 --> 35:10.720] an actual x64 CPU [35:11.660 --> 35:12.640] instruction that has [35:12.640 --> 35:14.980] their two team names combined into it. [35:14.980 --> 35:16.460] So PFS was a capture [35:16.460 --> 35:18.720] the flag team that actually won the first year of [35:18.720 --> 35:20.420] HackASAT. And then [35:20.420 --> 35:22.500] RCX is from Raytheon Technologies, [35:22.500 --> 35:24.460] another defense contractor. RCX is [35:24.460 --> 35:25.960] their CTF team. And so [35:25.960 --> 35:28.000] I was pretty impressed that they could actually [35:28.000 --> 35:29.960] find an x86 instruction with both [35:29.960 --> 35:32.040] of their mnemonics together, [35:32.040 --> 35:33.920] which is kind of cool. They claim [35:33.920 --> 35:34.560] that they can [35:35.720 --> 35:37.920] trigger random cosmic ray space [35:39.040 --> 35:39.840] rays and [35:39.840 --> 35:41.920] trigger bit flips. I think [35:41.920 --> 35:44.020] that's probably not true, but they did [35:44.020 --> 35:45.800] list that as their superpower on their [35:45.800 --> 35:48.120] team bio. If they can, [35:48.120 --> 35:50.040] Moonlighter will actually be much more susceptible to [35:50.040 --> 35:52.600] it than us on Earth with the ozone. [35:52.600 --> 35:53.920] If you're not familiar, there are actual [35:53.920 --> 35:56.280] cosmic rays that will literally hit electronics [35:56.280 --> 35:57.920] and flip bits randomly. So sometimes [35:57.920 --> 36:00.120] when your computer blue screens, it's not [36:00.120 --> 36:01.880] because of a software bug, it's actually [36:01.880 --> 36:04.140] because a space ray hit your memory [36:04.140 --> 36:05.960] and flipped a bit. This is actually [36:06.060 --> 36:07.920] a thing that happens, which is kind of crazy to think about. [36:08.300 --> 36:09.900] I don't think they can do it, but we'll see [36:09.900 --> 36:11.960] if it helps them in the [36:11.960 --> 36:12.860] final event. [36:13.880 --> 36:15.840] Alright, so that's it for the teams. Let's go ahead [36:15.840 --> 36:17.560] and talk a little bit more about the schedule [36:17.560 --> 36:19.400] and what you can expect [36:19.840 --> 36:20.880] the rest of the weekend. [36:22.480 --> 36:23.620] Thanks, Jordan. [36:23.760 --> 36:25.080] Okay, so let's just [36:25.080 --> 36:26.980] fill everybody in. If you haven't visited [36:26.980 --> 36:29.000] us, right on the other side of this wall, [36:29.000 --> 36:31.000] meander back out of the village. Please come [36:31.000 --> 36:32.940] see us. We do have stickers. If there's [36:32.940 --> 36:34.920] none out, ask one of us. We will hook [36:34.920 --> 36:36.500] you up with some cool stickers. [36:36.800 --> 36:38.780] We are, of course, running the CTF [36:38.780 --> 36:41.540] the rest of today and all day tomorrow. [36:41.620 --> 36:43.060] Let's just remember, this is [36:43.060 --> 36:45.100] quite literally the first CTF in space. [36:45.100 --> 36:46.820] So please digest our [36:46.820 --> 36:48.960] information, really get lost in [36:48.960 --> 36:51.460] the posters, ask questions. [36:51.460 --> 36:53.100] The only thing we do ask is that [36:53.100 --> 36:54.620] you give the privacy to the [36:54.620 --> 36:57.460] competitors and the main game ops table. [36:57.480 --> 36:58.940] They're kind of off limits, but [36:58.940 --> 37:01.140] we will help you and get you all the information [37:01.140 --> 37:02.480] you need in the meantime. [37:02.980 --> 37:05.020] Being our fourth year in the village, we still [37:05.020 --> 37:07.460] wanted to provide an educational aspect. [37:07.520 --> 37:09.040] Provide folks with kind of [37:09.300 --> 37:11.000] a trip down memory lane. So we have a really [37:11.000 --> 37:13.120] fun and cool technology museum. [37:13.180 --> 37:15.060] I personally think it looks awesome. [37:15.060 --> 37:16.960] In the cases, you'll find flatsats from [37:16.960 --> 37:18.960] years one and two. You'll also [37:18.960 --> 37:21.160] see a 3D print of Moonlighter. [37:21.160 --> 37:22.700] That's in the third case. [37:22.760 --> 37:25.100] The screen above those has a lot of information [37:25.100 --> 37:27.080] as far as the different boards and parts [37:27.080 --> 37:29.060] and pieces that it took to put those flatsats [37:29.060 --> 37:31.440] and make those work for us. [37:31.440 --> 37:33.320] We've got posters on Moonlighter [37:33.320 --> 37:35.060] on the game. We have a history [37:35.060 --> 37:37.040] poster, which is very informative [37:37.040 --> 37:38.980] as well. On our main [37:38.980 --> 37:41.100] screen, we're actually going to get some audio running out [37:41.100 --> 37:43.200] there. Live scoreboard, we're always [37:43.200 --> 37:45.180] tracking Moonlighter. It's very important to us [37:45.180 --> 37:47.780] and we want to be able to share that with you all as well. [37:49.160 --> 37:51.200] Other than that, we hope to see you again [37:51.200 --> 37:53.200] tomorrow, right back here in [37:53.200 --> 37:55.200] the same stage, same room at 11. [37:55.200 --> 37:57.280] Jordan is going to give a full [37:57.280 --> 37:59.200] deep dive of everything that occurs [37:59.200 --> 38:01.100] today. Anything else that he can [38:01.100 --> 38:03.160] talk about that's been scored and all the [38:03.160 --> 38:05.120] teams know. There will be [38:05.120 --> 38:07.360] no secrets or insider information [38:07.360 --> 38:08.900] given in this room. [38:08.900 --> 38:11.080] We're not anticipating any teams to come in [38:11.080 --> 38:13.180] and listen to these talks, so this is really [38:13.180 --> 38:14.960] for you guys to just get that [38:14.960 --> 38:17.180] piece of the competition that you don't otherwise [38:17.180 --> 38:19.280] get sitting at those chairs out [38:19.280 --> 38:21.280] there. So, like I said, tomorrow [38:21.280 --> 38:22.980] at 11, and then Sunday [38:22.980 --> 38:25.180] the awards ceremony is at noon [38:25.180 --> 38:27.180] and that will be the first time [38:27.180 --> 38:29.140] that anybody knows where the [38:29.140 --> 38:31.020] scoreboard is at and [38:31.020 --> 38:33.480] hears our first, second, and third place winners. [38:33.480 --> 38:35.160] The scoreboard is getting [38:35.160 --> 38:37.340] pulled off from our public website [38:37.340 --> 38:39.360] tomorrow at 6pm. [38:39.380 --> 38:41.100] Not necessarily to provide a [38:41.100 --> 38:42.920] blackout, but because we have many more [38:42.920 --> 38:44.300] contacts that we're going to [38:44.300 --> 38:47.120] be downlinking information [38:47.560 --> 38:48.980] and getting the final scores [38:48.980 --> 38:50.080] computated. [38:55.780 --> 38:56.860] Are you running through? [38:57.080 --> 38:59.540] Okay, Jordan, one more time for you all. [39:00.340 --> 39:01.400] Alright, so we're going to do a quick [39:01.400 --> 39:03.500] game update because, again, the competition [39:03.500 --> 39:04.820] actually started at [39:05.440 --> 39:07.220] 9am this morning. The teams have been [39:07.980 --> 39:09.440] actively communicating with things. [39:09.440 --> 39:11.520] And we do have a couple of scoring events, so we're going to pull [39:11.520 --> 39:13.420] up the scoreboard, but as a reminder, you can [39:13.420 --> 39:14.400] get to all this on [39:16.060 --> 39:17.200] Hackasat.com. [39:17.200 --> 39:19.580] I'm doing two different [39:19.580 --> 39:21.720] events this weekend, so it's a little crazy. [39:21.880 --> 39:23.560] If you go to Hackasat.com, you can see [39:23.560 --> 39:25.380] all of the data of, like, when the next [39:25.380 --> 39:27.340] contact window is. You can see [39:28.020 --> 39:29.520] how teams are scoring. [39:29.520 --> 39:31.340] And we do already have two teams who have scored. [39:31.340 --> 39:33.380] So remember earlier I mentioned there are two challenges [39:33.380 --> 39:35.320] that are just here on the ground station. [39:35.320 --> 39:37.480] So there's some services that the teams [39:37.480 --> 39:39.600] can interact with. And this is important [39:39.600 --> 39:41.540] because, you know, somebody's like, [39:41.540 --> 39:42.900] I thought this was a space hacking challenge. [39:42.900 --> 39:45.060] Why are they hacking just regular stuff [39:45.060 --> 39:47.380] that are normal servers sitting [39:47.380 --> 39:49.380] on the ground? It's like, well, because in actual [39:49.380 --> 39:51.500] satellite operations, the ground station is very much [39:51.600 --> 39:53.360] a part of the ecosystem. So that is very much [39:53.360 --> 39:55.160] part of securing it, is to [39:55.720 --> 39:57.380] secure the communication systems [39:57.380 --> 39:59.400] that they're working with. And those are oftentimes just [39:59.400 --> 40:01.500] running on standard servers, standard [40:02.380 --> 40:03.380] desktops and the [40:03.380 --> 40:04.660] operating systems they're running. [40:05.540 --> 40:07.520] Sometimes there's some slight differences, but some of those [40:07.520 --> 40:08.960] are actually surprisingly [40:08.960 --> 40:11.220] familiar to people who play regular CTFs. [40:11.220 --> 40:13.560] So it's not a surprise that teams are doing better with that. [40:13.600 --> 40:15.040] We've already got two scores [40:15.040 --> 40:17.760] on those ground station challenges. [40:17.860 --> 40:19.420] And so both PolinCAN [40:19.420 --> 40:21.220] and JumpFSRCX [40:21.220 --> 40:23.280] have scored on the [40:23.280 --> 40:26.020] flight software freebies challenge. [40:26.120 --> 40:27.240] So you'll see the [40:27.240 --> 40:29.440] scoreboard out on the wall and on the website. [40:29.440 --> 40:31.080] You'll see that they were able to [40:31.080 --> 40:33.280] get that in. We expect a couple more [40:33.280 --> 40:35.240] and then again hopefully we'll see some come [40:35.240 --> 40:37.200] through. They have their more communication [40:37.200 --> 40:39.220] windows throughout the day. [40:39.440 --> 40:41.300] So like I said, I think we'll just let you all [40:41.300 --> 40:43.480] check it out on the website. Unless it's here? Oh, it's here. [40:43.480 --> 40:45.660] There we go. Alright, so we can see the website. [40:48.060 --> 40:48.740] That's alright. [40:49.900 --> 40:51.300] It'll even work on mobile. [40:51.420 --> 40:52.400] It can be a little bit [40:53.520 --> 40:55.380] slow because there's a lot of stuff that loads on it. [40:55.380 --> 40:57.740] There's a whole bunch of different things. You'll see the score over time. [40:57.860 --> 40:59.140] The best one I think is probably [40:59.140 --> 41:01.100] the challenge dashboard. [41:01.240 --> 41:03.320] The challenge dashboard will show you by challenge [41:03.320 --> 41:05.060] who has solved things. [41:05.060 --> 41:07.060] So you get a pretty good idea of where people are [41:07.060 --> 41:09.220] throughout the competition, if that makes sense. [41:10.160 --> 41:11.140] Alright, I think [41:11.140 --> 41:12.840] that's it. We look forward to seeing everybody at [41:13.700 --> 41:15.160] our update tomorrow as well [41:15.160 --> 41:17.100] as Sunday. We'll tell you more details about how [41:17.100 --> 41:17.800] teams are doing.