WiFi Networks Turned Targets In This Pocket Game

June 20, 2020 by Tom Nardi 1 Comment

Looking for a way to make his warwalking sessions a bit more interactive, [Roni Bandini] has come up with an interesting way to gamify the discovery of new WiFi networks. Using a Heltec WiFi Kit 8, which integrates an OLED screen and ESP8266, this pocket-sized device picks up wireless networks and uses their signal strength and encryption type as elements of the game.

After selecting which network they want to play against, a target is placed on the screen. The distance between the target and the player is determined by signal strength, and how much damage the target can take correlates to how strong its encryption is. As you can see in the video after the break, gameplay is a bit reminiscent of Scorched Earth, where the player needs to adjust the angle of their artillery to hit distant targets.

The Heltec board is attached to a 3D printed front panel, which fits neatly into an Altoids tin. The controls consist of a button and a potentiometer, and with the addition of a battery pack salvaged from an old cell phone, this little device is ready to do battle wherever you roam.

While this is just a fun diversion for the time being, [Roni] says it wouldn’t take much to actual log networks to a file and generate some statistics about their strength and encryption type. If the idea of a portable WiFi scanning companion seems interesting, you should definitely check out the Pwnagotchi project.

Continue reading “WiFi Networks Turned Targets In This Pocket Game” →

Chasing A Long-Obsolete Tube

June 20, 2020 by Jenny List 12 Comments

Regular readers will know that here at Hackaday we have a penchant for poking fun at the more silly end of the audiophile world, with its dubious accessories and purple prose. It’s worth remembering though that this is not representative of the whole discipline of audio design, indeed the quest for perfect audio reproduction contains plenty of complex engineering problems.

We’re indebted to [macsimski] then for sending us a link to a page from Phaedrus Audio from a year or two ago, in which they discuss the history of an unusual pentode tube used as an impedance converter in a series of legendary post-war microphones. It’s unlikely that you’ll have a Neumann U47 or U48 broadcast microphone on your bench, but even so the story behind their design is one that should fascinate anyone.

It takes us back to the period immediately following the Second World War, when German electricity supplies were varied and unreliable, and radio receivers designed for them required new tubes from the manufacturers. Among these was the VF14, with an unusual high-voltage heater designed such that two of them could be connected in series across the supply. This and its compact shape prompted its selection for the professional microphones, even though its performance was so poor that only a third of the production passed the performance test.

Since it passed out of production in the early 1950s the remaining components are extremely rare, and the majority of those surviving do not meet the performance characteristics of the microphone. The Phaedrus write-up goes into significant technical detail which should be of note to anyone with an interest in tubes, and ends up with their reason for it all, a plug-in hardware simulation of the original tube’s properties. Vintage capacitor microphones may be out of the ordinary for Hackaday, but it’s still a good read.

For a bit more on capacitor microphones it’s worth a look at our dive into electrets.

Header image: JacoTen / CC BY-SA 3.0

Great Badge Concept: A “Geiger Counter” For WiFi Deauthentication Frames

June 20, 2020 by Donald Papp 15 Comments

[Nick Price] had a wonderful concept for a DEFCON badge: a device that worked a lot like a directional Geiger counter, but chirped at detecting WiFi deauthentication packets instead of radiation. That’s a wild idea and it somehow slipped past us last year. Why detect such a thing? Well, the WiFi deauth attack is a kind of invisible toxicity, effectively jamming wireless communications by forcing users to be constantly tied up with authentication, and this device would detect it.

A few things were harder than expected, however. To make the device directional, [Nick] designed and built a PCB Yagi antenna but it wasn’t practical. Not only was it far too big, it would also have required going to four layers on a PCB that was already expensive. The solution he settled on — inspired by a friend’s joke about just dropping the badge into a Pringles can — was to surround the PCB omni antenna with a copper pipe end cap from the plumbing section of any hardware store. [Nick] figured that soldering that to the ground plane should result in a simple, cheap, and attractive directional antenna mod. Did it work? We’ll all have to wait and see.

Sadly, [Nick] wasn’t able to finish in time for last year’s DEFCON. Hardware revisions mounted, and fabrication times for his specialized PCB were longer than usual. Worse news is that this year’s is cancelled, or rather is going virtual, which means he’s going to have to deauth himself. The good news is that now he’s got another 12-month extension. Watch the brief video of the functional prototype, embedded below.

Continue reading “Great Badge Concept: A “Geiger Counter” For WiFi Deauthentication Frames” →

Seeing Code: The Widescreen Rant

June 20, 2020 by Elliot Williams 114 Comments

A couple of weeks ago, Linus Torvalds laid down the law, in a particularly Linusesque sort of way. In a software community where tabs vs. spaces can start religious wars, saying that 80-character-wide code was obsolete was, to some, utter heresy. For more background on how we got here, read [Sven Gregori]’s history piece on Hackaday, and you’ll learn that sliced bread and the 80-character IBM punch card both made their debut in July, 1928. But I digress.

When I look at a codebase, I like to see its structure, and I’m not alone. That’s one of the reasons for the Linux Kernel style guide’s ridiculously wide 8-character tabs. Combined with a trend for variable names becoming more and more descriptive, which I take to be a good thing, and monitors’ aspect ratios growing seemingly without end, which I don’t, the 80-column width seems like a relic from the long-gone era of the VT-220.

In Linus’ missive, we learn that he runs terminals at 100 x 50, and frequently drags them out to a screen-filling 142 x 76. (Amateur! I write this to you now on 187 x 48.) When you’re running this wide, it doesn’t make any sense to line-wrap argument lists, even if you’re using Hungarian notation.

And yet, change is painful. I’ve had to re-format code to meet 73-column restrictions for a book, only to discover that my inline comments were too verbose. Removing even an artificial restriction like the 80-column limit will have real effects. I write longer paragraphs, for instance, on a wider screen.

I see a few good things to come out of this, though. If single thoughts can be expressed on single lines, it makes the shape of the code better reflect its function. Getting rid of pointless wrapping takes up less vertical space, which is at a premium on today’s cinematic monitors. And if it makes inline comments better (I know, another holy war!) or facilitates better variable naming, it will have been worth it.

But any way you slice it, we’re no longer typing on the old 80-character Hazeltine. It’s high time for our coding style and practice to catch up.

Smartglove Helps Cyclists Be Seen

June 20, 2020 by Lewin Day 25 Comments

Cyclists share the road with other vehicles, often leading to problems when drivers fail to see or respect the rider’s space. To try and alleviate these issues, [Matlek] built the Smartglove to help cyclists communicate their intentions to other road users.

The project consists of a glove fitted with an Arduino Nano 33 BLE sense, featuring Bluetooth and motion sensing on board. Combined with TinyML machine learning code, the Arduino is able to sense hand gestures from the rider. These gestures are then interpreted, and relevant messages displayed on an LED screen worn on the rider’s back. Flicking the wrist left and right flashes indicators that the user is about to change direction, while a rearward flick flashes a warning that the user is braking.

It’s a tidy way to integrate vehicle-style lighting into a simple interface for cycling. This has benefits, particularly at night, for allowing other road users to see a cyclist and understand their intentions on the road. Of course, if you really want to be noticed, this bike boombox could also be a big help. Video after the break. Continue reading “Smartglove Helps Cyclists Be Seen” →

Key That Morse With Little More Than Your Laptop

June 20, 2020 by Jenny List 20 Comments

If you look at the computer in front of you, it will have an array of input devices. A keyboard and mouse, a touch screen, maybe a microphone, or even a gamepad. Each of them will have its moment to shine, and you’ll probably have put some effort into their selection. But when it comes to a computer, almost anything connected to it can be an input device in some form, as long as it provides some form of machine readable parameter.

Consider your laptop: it knows when its lid is closed such that it can put itself to sleep. Even that can be used as an input device with a little ingenuity, as [veggiedefender] has done with “open and shut“, a Morse keyer using opening and closing the laptop lid as its key.

The software for GNU/Linux distributions is a surprisingly accessible set of shell scripts that attach themselves to ACPI events surrounding the lid switch. In use it seems a little cumbersome, but we suspect its real value is not in repeatedly slammin the lid to produce Morse text input. Instead with many lid switches being magnetic reed switches an operator could simply wear a ring with a magnet and tap out their text every bit as quickly as they could using a traditional key.

We like the idea, and could see it being popular among radio amateurs. It’s a theme we’ve visited before with a more traditional key, and if you’d love to try but don’t know any Morse then perhaps this may help you learn.

Thanks [Kickaxe] for the tip.

Header image: Raimond Spekking / CC BY-SA 4.0.

Plant’m If You Got’m And Keep’m Alive

June 19, 2020 by Kristina Panos 13 Comments

Having a few plants around is a great way to liven up your living and/or working space. They look nice, you get to watch them grow and change, and some types of plants can actively improve the room’s air quality. But let’s face it — even the easy ones require a baseline level of care that can easily fall by the wayside. After all, the poor things can’t scream out for water or get up and find a sunnier spot for themselves.

[Ine Hocedez] was tired of watching her plants die and not knowing why. The two main culprits involve water and light, though there can be other issues like soil pH and bugs. It’s easy to get the balance wrong, so why not automate everything?

Plant’m is a complete, portable package that [Ine] designed for a school project. A soil moisture sensor dictates the watering schedule via Raspberry Pi, and water is automatically pumped from an elevated tank.

The lamp is meant to supplement the sunlight, not replace it. But that’s the real beauty of this botanical box — [Ine] can just pick it up and try a different spot if the plant droops or shows burnt spots.

Got the sunlight part down for your plant, but can’t remember to water it? Re-purpose an old Keurig and give it an automatic drip.