This excellent content from the Hackaday writing crew highlights recurring topics and popular series like Linux-Fu, 3D-Printering, Hackaday Links, This Week in Security, Inputs of Interest, Profiles in Science, Retrotechtacular, Ask Hackaday, Teardowns, Reviews, and many more.
Going from a microcontroller blinking an LED, to one that blinks the LED using voice commands based on a data set that you trained on a neural net work is a “now draw the rest of the owl” problem. Lucky for us, Shawn Hymel walks us through the entire process during his Tiny ML workshop from the 2020 Hackaday Remoticon. The video has just now been published and can be viewed below.
This is truly an end-to-end Hello World for getting machine learning up and running on a microcontroller. Shawn covers the process of collecting and preparing the audio samples, training the data set, and getting it all onto the microcontroller. At the end of two hours, he’s able to show the STM32 recognizing and responding to two different spoken words. Along the way he pauses to discuss the context of what’s happening in every step, which will help you go back and expand in those areas later to suit your own project needs.
Hackaday editors Elliot Williams and Mike Szczys discuss the latest and greatest in geeky goodness. This week we saw a Soviet time capsule come to light with the discovery of a computer lab from a building abandoned in the 1990’s. A two-cycle compressed air engine shatters our expectations of what is involved in RC aircraft design. There’s a new toolkit for wireless hacking on the scene in the form of a revitalized HackRF PortaPack firmware fork. And what goes into dishwasher design? Find out in this exciting episode.
Take a look at the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!
I hope everyone had a wonderful Thanksgiving last week. My household celebrated by welcoming a 4th member to the family. My daughter was born on Wednesday morning, November 25th. And thus explains what I did last week instead of writing the normal Hackaday column. Never fear, we shall catch up today, and cover the news that’s fit to be noticed.
iOS Zero-click Wifi Attack
[Ian Beer] of Google’s Project Zero brings us the fruit of his lockdown-induced labors, a spectacular iOS attack. The target of this attack is the kernel code that handles AWDL, an Apple WiFi protocol for adhoc mesh networks between devices. The most notable feature that makes use of AWDL is AirDrop, Apple’s device-to-device file sharing system. Because AWDL is a proprietary protocol, the WiFi hardware can’t do any accelerated processing of packets. A few years back, there was an attack against Broadcom firmware that required a second vulnerability to jump from the WiFi chip to the device CPU. Here, because the protocol is all implemented in Apple’s code, no such pivot is necessary.
And as you’ve likely deduced, there was a vulnerability found. AWDL uses Type-Length-Value (TLV) messages for sending management data. For a security researcher, TLVs are particularly interesting because each data type represents a different code path to attack. One of those data types is a list of MAC addresses, with a maximum of 10. The code that handles it allocates a 60 byte buffer, based on that maximum. The problem is that there isn’t a code path to drop incoming TLVs of that type when they exceed 60 bytes. The remainder is written right past the end of the allocated buffer.
There is more fun to be had, getting to a full exploit, but the details are a bit too much to fully dive in to here. It interesting to note that [Ian] ran into a particular problem: His poking at the target code was triggering unexpected kernel panics. He discovered two separate vulnerabilities, both distinct from the vuln he was trying to exploit.
Finally, this exploit requires the target device to have AWDL enabled, and many won’t. But you can use Bluetooth Low Energy advertisements to trick the target device into believing an Airdrop is coming in from a trusted contact. Once the device enables AWDL to verify the request, the attack can proceed. [Ian] reported his findings to Apple way back in 2019, and this vulnerability was patched in March of 2020.
Circuit Sculpture was one of our most anticipated workshops of Hackaday Remoticon 2020, and now it’s ready for those who missed it to enjoy. A beginning circuit sculptor could hardly ask for more than this workshop, which highlights three different approaches to building firefly circuit sculptures and is led by some of the most prominent people to ever bend brass and components to their will — Jiří Praus, Mohit Bhoite, & Kelly Heaton.
For starters, you’ll learn the different tools and techniques that each of them uses to create their sculptures. For instance, Kelly likes to use water-based clay to hold components in specific orientations while forming the sculpture and soldering it all together. Jiří and Mohit on the other hand tend to use tape. The point is that there is no right or wrong way, but to instead have all of these tips and tricks under your belt as you sculpt. And that’s what this workshop is really about.
On November 17th, a Vega rocket lifted off from French Guiana with its payload of two Earth observation satellites. The booster, coincidentally the 17th Vega to fly, performed perfectly: the solid-propellant rocket engines that make up its first three stages burned in succession. But soon after the fourth stage of the Vega ignited its liquid-fueled RD-843 engine, it became clear that something was very wrong. While telemetry showed the engine was operating as expected, the vehicle’s trajectory and acceleration started to deviate from the expected values.
There was no dramatic moment that would have indicated to the casual observer that the booster had failed. But by the time the mission clock had hit twelve minutes, there was no denying that the vehicle wasn’t going to make its intended orbit. While the live stream hosts continued extolling the virtues of the Vega rocket and the scientific payloads it carried, the screens behind them showed that the mission was doomed.
Displays behind the hosts clearly showed Vega wasn’t following the planned trajectory.
Unfortunately, there’s little room for error when it comes to spaceflight. Despite reaching a peak altitude of roughly 250 kilometers (155 miles), the Vega’s Attitude Vernier Upper Module (AVUM) failed to maintain the velocity and heading necessary to achieve orbit. Eventually the AVUM and the two satellites it carried came crashing back down to Earth, reportedly impacting an uninhabited area not far from where the third stage was expected to fall.
Although we’ve gotten a lot better at it, getting to space remains exceptionally difficult. It’s an inescapable reality that rockets will occasionally fail and their payloads will be lost. Yet the fact that Vega has had two failures in as many years is somewhat troubling, especially since the booster has only flown 17 missions so far. A success rate of 88% isn’t terrible, but it’s certainly on the lower end of the spectrum. For comparison, boosters such as the Soyuz, Falcon 9, and Atlas have success rates of 95% or higher.
Further failures could erode customer trust in the relatively new rocket, which has only been flying since 2012 and is facing stiff competition from commercial launch providers. If Vega is to become the European workhorse that operator Arianespace hopes, figuring out what went wrong on this launch and making sure it never happens again is of the utmost importance.
You hold in your hand a circuit board from a product you didn’t make. How does the thing work? What a daunting question, but it’s both solvable and approachable if you know what you’re doing. The good news is that Eric Schlaepfer knows exactly what he’s doing and boiled down the process of reverse engineering printed circuit boards into this excellent workshop. It was presented live during the 2020 Hackaday Remoticon, and the edited video, which you’ll find below, was just published. Slides for the talk have been published on the workshop project page.
Sure, the SpaceX crew made it safely to the ISS, but there’s plenty happening beyond just that particular horizon. The Chinese National Space Administration have launched their Chang’e 5 mission to collect and return lunar rock samples, a collaboration between NASA and ESA to do the same with samples from Mars has passed its review, and a pair of satellites came uncomfortably close to each other in a near-miss that could have had significant orbital debris consequences. It’s time for Spacing Out!
Bringing Alien Rocks to Earth
The Chang’e 5 mission on the launch pad. China News Service, CC BY 3.0.
Ever since the NASA and Soviet lunar launches at the height of the Space Race, there have been no new missions to collect material from the Lunar surface and return it to Earth. That changed last week.
Not to be outdone in the field of ambitious sample return missions, NASA and ESA’s joint plan to collect and return rock core samples from Mars has met with the approval of the independent review board set up to examine it. This will involve multiple craft from both agencies, with NASA’s already launched Perseverance rover collecting and containing the samples before leaving them on the surface for eventual collection by a future ESA rover. This will then pass them to a NASA ascent craft which will take them to Martian orbit and rendezvous with an ESA craft that will return them to Earth. We space-watchers are in for an exciting decade.
That Was a Close One!
Anyone who has seen the film Gravity will be familiar with the Kessler syndrome, in which collisions between spacecraft and or debris could create a chain reaction of further collisions and render entire orbital spheres unusable to future craft because of the collision hazard presented by the resulting cloud of space debris. Because of this, spacecraft operators devote considerable resources towards avoiding such collisions, and it is not uncommon for slight orbital adjustments to be made to avoid proximity with other orbiting man-made objects.
On the 27th of November it seems that these efforts failed, with a terse announcement from Roscosmos of a near-miss between their Kanopus-V craft and the Indian CARTOSAT 2F. The two remote-imaging satellites passed as close as 224 metres from each other, which in space terms given their likely closing speeds would have been significantly too close for comfort. The announcement appears worded to suggest that the Indian craft was at fault, however it’s probably a fairer conclusion that both space agencies should have seen the other’s satellite coming. Fortunately we escaped a catastrophe this time, but it is to be hoped that all operators of such satellites will take note.
RocketLab Joins the Reusable Booster Club
Other recent launches that might excite the interest of readers are the New Zealand-based RocketLab launching their Electron rocket with 30 small satellites on board before for the first time retrieving their booster stage, and the Japanese Mitsubish Electric sending their JDRS-1 satellite to geosynchronous orbit. This last craft is of interest because it carries an optical data link rather than the more usual RF, and could prove the technology for future launches.
The coming weeks should be full of news from China on Chang’e 5’s progress. Getting a craft to the moon and returning it will be a huge achievement, and we hope nothing fails and we’ll see pictures of the first new Moon rocks on Earth since the 1970s. We don’t know how to say “Good luck and a successful mission!” in Chinese, so we’ll say it in English.
