Introducing FISSURE: A Toolbox For The RF Hacker

No matter what the job at hand is, if you’re going to tackle it, you’re going to need the right kit of tools. And if your job includes making sense out of any of the signals in the virtual soup of RF energy we all live in, then you’re going to need something like the FISSURE RF framework.

Exactly what FISSURE is is pretty clear from its acronym, which stands for Frequency Independent SDR-Based Signal Understanding and Reverse Engineering. This is all pretty new — it looks like [Chris Poore] presented a talk at DEFCON a few weeks back about using FISSURE to analyze powerline communications between semi-trucks and their trailers, and they’ve got a talk scheduled for next month’s GNU Radio Conference as well. We’ve been looking through all the material we can find on FISSURE, and it appears to be an RF hacker’s dream come true. They’ve got a few examples on Twitter, like brute-forcing an old garage door opener with a security code set by a ten-position DIP switch, and sending tire pressure monitoring system (TPMS) signals to a car. They also mention some of the framework’s capabilities on the GitHub README; we’re especially interested in packet crafting for various protocols. The video below has some more examples of what FISSURE can do.

It looks like FISSURE could be a lot of fun, and very handy for your RF analysis and reverse engineering work. If you’ve been using Universal Radio Hacker like we have, this looks similar, only more so. We’ll be downloading it soon and giving it a try, so be on the lookout for a hands-on report.

Continue reading “Introducing FISSURE: A Toolbox For The RF Hacker”

Machine Learning Gives Cats One More Way To Control Their Humans

For those who choose to let their cats live a more or less free-range life, there are usually two choices. One, you can adopt the role of servant and run for the door whenever the cat wants to get back inside from their latest bird-murdering jaunt. Or two, install a cat door and let them come and go as they please, sometimes with a “present” for you in their mouth. Heads you win, tails you lose.

There’s another way, though: just let the cat ask to be let back in. That’s the approach that [Tennis Smith] took with this machine-learning kitty doorbell. It’s based on a Raspberry Pi 4, which lives inside the house, and a USB microphone that’s outside the front door. The Pi uses Tensorflow Lite to classify the sounds it picks up outside, and when one of those sounds fits the model of a cat’s meow, a message is dispatched to AWS Lambda. From there a text message is sent to alert [Tennis] that the cat is ready to come back in.

There’s a ton of useful information included in the repo for this project, including step-by-step instructions for getting Amazon Web Services working on the Pi. If you’re a dog person, fear not: changing from meows to barks is as simple as tweaking a single line of code. And if you’d rather not be at the beck and call of a cat but still want to avoid the evidence of a prey event on your carpet, machine learning can help with that too.

[via Tom’s Hardware]

Everything You Didn’t Know You Need To Know About Glitching Attacks

If you’ve always been intrigued by the idea of performing hardware attacks but never knew where to start, then we’ve got the article for you: an in-depth look at the hows and whys of hardware glitching.

Attentive readers will recall that we’ve featured [Matthew Alt]’s reverse engineering exploits before, like the time he got root on a Linux-based arcade cabinet. For something a bit more challenging, he chose a Trezor One crypto wallet this time. We briefly covered a high-stakes hack (third item) on one of these wallets by [Joe Grand] a while back, but [Matthew] offers much, much more detail.

After introducing the theory of glitching attacks, which seek to force a processor into an undefined state using various methods, [Matthew] discusses the specifics of the Trezor wallet and how the attack was planned.

His target — the internal voltage regulator of the wallet’s STM32 microcontroller — required desoldering a few caps before the attack could begin, which was performed with a ChipWhisperer. After resolving a few initial timing issues, he was able to glitch the chip into dropping to the lowest level of readout protection, which gave access to the dongle’s SRAM through an ST-Link debugger.

While this summary may make the whole thing sound trivial, it’s obvious that the attack was anything but, nor was the effort that went into writing it all up. The whole thing reads a little like a techno-thriller, and there’s plenty of detail there if you’re looking for a tutorial on chip glitching. We’re looking forward to part 2, which will concentrate on electromagnetic fault-injection using a PicoEMP and what looks like a modified 3D printer.

How Resilient Is The Natural Gas Grid?

A few years ago, I managed to get myself on a mailing list from a fellow who fancied himself an expert on energy. Actually, it seemed that no area was beyond his expertise, and the fact that EVERY EMAIL FROM HIM CAME WITH A SUBJECT LINE IN CAPS WITH A LOT OF EXCLAMATION POINTS!!!! really sealed the deal on his bona fides. One of the facts he liked to tout was that natural gas was the perfect fuel. Not only is it clean-burning and relatively cheap, it’s also delivered directly to consumers using a completely self-powered grid. Even under “zombie apocalypse” conditions, he claimed that natural gas would continue to flow.

At the time, it seemed a bit overstated, but I figured that there was at least a nugget of truth to it — enough so that I converted from an electric range and water heater to gas-powered appliances a couple of years ago, and added gas fireplaces for supplemental heat. I just sort of took it for granted that the gas would flow, at least until the recent kerfuffle over the Nordstream pipeline. That’s when I got a look at pictures of the immense turbine compressors needed to run that pipeline, the size and complexity of which seem to put the lie to claims about the self-powered nature of natural gas grids.

Surely a system dependent on such equipment could not be entirely self-powered, right? This question and others swirled doubt in my mind, and so I did what I always do in these cases: I decided to write an article so I could look into the details. Here’s what I found out about how natural gas distribution works, at least in North America.

Continue reading “How Resilient Is The Natural Gas Grid?”

Ryobi Battery Hack Keeps CPAP Running Quietly

When it comes to cordless power tools, color is an important brand selection criterion. There’s Milwaukee red, for the rich people, the black and yellow of DeWalt, and Makita has a sort of teal thing going on. But when you see that painful shade of fluorescent green, you know you’ve got one of the wide range of bargain tools and accessories that only Ryobi can offer.

Like many of us, Redditor [Grunthos503] had a few junked Ryobi tools lying about, and managed to cobble together this battery-powered inverter for light-duty applications. The build started with a broken Ryobi charger, whose main feature was a fairly large case once relieved of its defunct guts, plus an existing socket for 18-volt battery packs. Added to that was a small Ryobi inverter, which normally plugs into the Ryobi battery pack and converts the 18 VDC to 120 VAC. Sadly, though, the inverter fan is loud, and the battery socket is sketchy. But with a little case modding and a liberal amount of hot glue, the inverter found a new home inside the charger case, with a new, quieter fan and even an XT60 connector for non-brand batteries.

It’s a simple hack, but one that [Grunthos503] may really need someday, as it’s intended to run a CPAP machine in case of a power outage — hence the need for a fan that’s quiet enough to sleep with. And it’s a pretty good hack — we honestly had to look twice to see what was done here. Maybe it was just the green plastic dazzling us. Although maybe we’re too hard on Ryobi — after all, they are pretty hackable.

Thanks to [Risu no Kairu] for the tip on this one.

Superconference 2022 Hack Chat

Join us on Wednesday, August 24 August 31 at noon Pacific for the Superconference 2022 Hack Chat!

[Sorry folks — due to a scheduling snafu, we’ve got to push this off a week. — ed]

To say that a lot of water has passed under the bridge since 2019 is something of an understatement. When last we met as a group, in Pasadena in November of that year, the Covid-19 pandemic and its fallout were ahead of us. Supercon 2019 was a smashing success, a three-day meetup that brought together the best the hacker community has to offer to exchange ideas, share their projects, and meet up IRL rather than reading about everyone’s exploits and adventures online. It was a fantastic time, but how were we to know that it would be the last meatspace meetup for a painfully long time?

join-hack-chatThankfully, that’s all behind us now, and Supercon 2022 is back, live and in person! Everyone in the hacker community is going to want to be in Pasadena, but since it’s been so long since we’ve met up in person, we thought a Hack Chat focusing on Supercon would be a good idea. We’ve invited Majenta Strongheart on to field your questions, plus hopefully we’ll have a few surprise guests too. But this will mainly be your chance to sort of “pre-network” before the con. If you’re a Supercon first-timer, this is a great way to ask questions about how it all works and whether it’s worth it to attend (answer: it is — go buy tickets now!) For vets, this is your chance to share your stories of Supercons past, or perhaps to reconnect with con-buddies you’ve lost touch with. There’ll be something for everyone, both at the Hack Chat and at Supercon, so drop by the chat and find out what all the hype is about.

Our Hack Chats are live community events in the Hackaday.io Hack Chat group messaging. This week we’ll be sitting down on Wednesday, August 31 at 12:00 PM Pacific time. If time zones have you tied up, we have a handy time zone converter.

Hackaday Links Column Banner

Hackaday Links: August 21, 2022

As side-channel attacks go, it’s one of the weirder ones we’ve heard of. But the tech news was filled with stories this week about how Janet Jackson’s “Rhythm Nation” is actually a form of cyberattack. It sounds a little hinky, but apparently this is an old vulnerability, as it was first noticed back in the days when laptops commonly had 5400-RPM hard drives. The vulnerability surfaced when the video for that particular ditty was played on a laptop, which would promptly crash. Nearby laptops of the same kind would also be affected, suggesting that whatever was crashing the machine wasn’t software related. As it turns out, some frequencies in the song were causing resonant vibrations in the drive. It’s not clear if anyone at the time asked the important questions, like exactly which part of the song was responsible or what the failure mode was on the drive. We’ll just take a guess and say that it was the drive heads popping and locking.

Continue reading “Hackaday Links: August 21, 2022”