After Decades, NASA May Finally Replace Mars Relays

We’ve yet to find any definitive evidence that there’s biological life on present-day Mars, but to say it’s a dead planet isn’t exactly accurate. Since the first Viking lander touched down in 1976, a revolving cast of humanity’s robotic envoys have worked on and around the Red Planet — and as access to space becomes cheaper and more routine, the mechatronic population of Mars will continue to grow.

Given the number of landers, rovers, and orbiting spacecraft that have been sent to study Mars over the last 50 years, you might be surprised to find that the communications systems in place to transmit all that critical scientific data back to Earth aren’t nearly as robust as you’d think. While it’s understandable that the first craft to arrive at Mars had to operate in isolation, even the flagship Perseverance and Curiosity rovers carry their own high-gain radio systems so they can communicate directly with Earth. Given the incredible premium put on the mass of an interplanetary craft, each mission that needs to bring along its own link back to Earth effectively reduces its payload of much scientific equipment.

It’s not that satellites in orbit around the planet aren’t used to relay signals between Martian ground assets and their controllers back on Earth. In fact these relay links are used extensively for bandwidth-intensive tasks such as image transfers. But it’s also true that the craft currently available to act as intermediaries between the two planets aren’t terribly well suited to the task. The current fleet of Mars orbiters were conceived primary as research vehicles, and so every decision regarding their design and positioning around the planet was made with that goal in mind. What relatively limited capability they do have as communication relays is further hindered by the age of their hardware.

But after decades of false starts and shifting budgets, NASA is closer than ever to finally establishing the Mars Telecommunications Network, a dedicated high-bandwidth communication relay that will ensure current and future missions always have a way to phone home.

Continue reading “After Decades, NASA May Finally Replace Mars Relays” →

2026 Hackaday Supercon: Announcing Our First Round Of Speakers

Supercon is the Ultimate Hardware Conference™ and you need to be there November 6-8 in Pasadena, California! Below is just the tip of the speakers’ iceberg, but if that’s not enough to convince you to attend, well, stay tuned and we’ll reveal more speakers early next week.

Speakers, workshops, food, drink, music, badge hacking, and general merriment? That’s what we do every year at our annual gathering. This year is even bigger, as we’re moving a few blocks south to the Art Center campus, so be sure to come join us. Get your tickets now.

Continue reading “2026 Hackaday Supercon: Announcing Our First Round Of Speakers” →

Raspberry Pi RAM Restrictions No Big Deal, Frankly

Hacking on Raspberry Pi board internals is one of my favourite topics. I know a bunch of obscure things about these cute little boards. Three years ago, I covered a Raspberry Pi 4 RAM upgrade story. Getting a BGA RAM chip and swapping it in seemed like a no-brainer to me – apart from all the numerous uncertain parts about it, you know. It was a joy to see hackers pull it off, and for it to function as well as it did!

Things changed. You can’t really get RAM chips anymore. You also can’t get RAM sticks. You can’t get even SSDs with RAM chips on them. Even getting Raspberry Pi boards can be hard unless you know where to look. This is where a recent three-minute video by [Jeff Geerling] finds us.

Turns out, Raspberry Pi Foundation pushed binary-blob bootloader changes that limit your ability to upgrade RAM. I’ve known about it since last year through the grapevine, and somehow, as I read about it, this didn’t bother me at all. Not enough to write a Hackaday article about it, even, much less talk about it more widely. Why didn’t it bother me? Today, I sat down and pondered this for a bit.

Here’s my conclusion: I don’t think it’s a big deal at all, even if it seems that many people would disagree. Come in, as you are, and I hope you find my thoughts on the situation entertaining.

Continue reading “Raspberry Pi RAM Restrictions No Big Deal, Frankly” →

DIY Router On X86 E-Waste: OpenWrt And OPNsense

In previous installments of this series we looked at how creating a DIY router using an e-waste-level PC has changed over the years, before attempting to boot OpenWrt for x86 on it. After an initial SD card booting failure on one system, another system with a newer mainboard – an Intel Board D2500CC – was used which happily booted OpenWrt from an SD card inserted into a USB card reader.

Unfortunately, OpenWrt didn’t see any usable Ethernet interfaces despite having no less than four Intel Ethernet controllers and two hooked up to active networks. After recently getting back to the project, I found out why both onboard Intel 82574L Ethernet controllers didn’t show up in OpenWrt: the drivers for the Intel 82574L controllers are in the e1000e driver package, while only the e1000 package is present in the provided x86 image. This issue persists in the ‘generic’ image profile to this day.

Yet rather than diving head-first into building my own image that includes the kmod-e1000e package, I decided to give OPNsense a shake first.

Continue reading “DIY Router On X86 E-Waste: OpenWrt And OPNsense” →

What Are Your Indispensable Software Skills?

Using tools properly takes skill, and this goes for software tools as well as hardware. You don’t just buy a paintbrush and on day one paint the Mona Lisa. Similarly, you can’t just open up a CAD program and whip out whatever 3D objects your heart desires, or fire up Vim and start typing. Software tools take a bit of learning before you can wield them efficiently, if even at all. And because you can’t be skilled at everything, no matter how hard we are all trying, it’s good to have at least some of the software tools you know do double duty.

Tom and I were watching [Clough42] design an electronics cabinet for a CNC machine. He does a lot of CNC machining and design work, so he’s no stranger to CAD software. So he downloaded all of the parts that he needed inside cabinet, slid them onto virtual DIN rails, modeled the hinges, and made sure that everything fit before buying anything.

Now I know that some of you out there do CAD modeling like this all the time, but for Tom and I, who are 3D printerers and PCB layouterers, doing the CAD without then following through and finishing up with the CAM seemed a bit novel. I never open CAD unless I’m going to have a machine make the thing – otherwise I’d just draw it out on paper, right? But [Clough42]’s point is that getting models of all of the subparts is so easy these days, you might as well model it.

If, and this is the big “if”, you know your way around the CAD tool of your choice. If you don’t yet, it’s going to be a couple of days’ worth of effort to get there. But once you reach CAD nirvana, you’ll find it’s useful for sketching up anything that has a third dimension to it, not just stuff you need to print out.

What other software tools are like CAD in that once you know them well enough, a wealth of applications opens up before you? Of was this just an instance of having a hammer and everything looking like a nail?

Hackaday Podcast Episode 387: Superhuman Clocks, CAN In USB-C, And The Joys Of Bare Metal

This week, Hackaday Editors Elliot Williams and Tom Nardi start the episode off by discussing the latest CircuitPython developments before covering some impressive reverse engineering efforts, the benefits of modeling your projects in 3D, and some of the most incredible timepieces that have ever graced the pages of Hackaday.

You’ll also hear about the fascinating potential of combing 3D and UV printing, Linux on the ESP32, and a virtual TV station that pulls from the Internet Archive. The episode wraps up with a Hackaday Europe double-feature: one talk extols the virtues of keeping things simple through bare metal development, while the other covers off-world hacks and fixes that will make you want to sign up for Space Camp.

Check out the links if you want to follow along, and as always, tell us what you think about this episode in the comments!

Direct download, the MP3 way.

Continue reading “Hackaday Podcast Episode 387: Superhuman Clocks, CAN In USB-C, And The Joys Of Bare Metal” →

This Week In Security: Flock Cameras Are Old, Microsoft Patches Patches, And Researchers Attack SSH

Leak site Distributed Denial of Secrets has released a dump of the filesystems of a Flock camera, and Micah Lee has published a dive into the contents.  Apparently the Flock security model did not include “angry citizens with a hacksaw in the middle of the night” in the physical security category.

The first thing Micah notes is that the Flock hardware runs Android 8.1 (for those not keeping track, the current Android release is Android 17 released in June 2026).  The version of Android running on the Flock camera was last patched in June of 2018, and the Linux kernel (3.18.71) is over nine years out of date, and the 3.18 series went end-of-life in 2019.

You might assume “wouldn’t an operating system this old have known vulnerabilities?”, and you’d be completely right.  Micah calls out two in particular, one in the Qualcomm GPU which allows any program to manipulate kernel memory and gain root (similar, yet simpler, than the spate of kernel vulnerabilities this year that allowed manipulating memory via the disk IO cache), and the “WrongZone” vulnerability which allows a process to escalate to root via socket handling errors.  You might also guess both of these have been patched, and again, you’d be right, in 2021 and 2018 respectively.

Digging deeper, Micah discovers that API keys with access into the Flock infrastructure appear to be hard-coded into the binaries.  Each camera appears to request credentials from an authentication server, using the MAC address of the camera.  After obtaining the credentials from an Okta Auth0 sign-in service, the Flock stores them, in plain text.

Also stored on the camera unencrypted are logs and position data:  The camera dumped to Distributed Denial of Secrets came from a suburb of Milwaukee. Continue reading “This Week In Security: Flock Cameras Are Old, Microsoft Patches Patches, And Researchers Attack SSH” →