Saving Australia’s Ants With Age Of Empires II

Australia’s native meat ants are struggling. Invasive species of foreign ants have a foothold on the continent, and are increasingly outcompeting their native rivals for territory. Beyond simple encroachment, they pose a hazard to native animals and agriculture.

Scientists at the CSIRO have been investigating the problem, hoping to find a way to halt the invasion. Charged with finding a way to help Australia’s native ants fight back, they turned to one of the most popular battle simulations of all time: Age of Empires II. 

Continue reading “Saving Australia’s Ants With Age Of Empires II”

Hackaday Links Column Banner

Hackaday Links: October 29, 2023

“As California goes, so goes the nation.” That adage has been true on and off for the last 100 years or so, and it’s true again now that GM’s Cruise self-driving car unit has halted operations across the United States, just a couple of days after California’s DMV suspended its license to conduct driverless tests on state roadways. The nationwide shutdown of testing was undertaken voluntarily by the company and takes their sore beset self-driving taxi fleet off the road in Phoenix, Houston, Austin, Dallas, and Miami, in addition to the California ban, which seemed to be mainly happening in San Francisco. Cruise’s fleet has suffered all manner of indignities over the last few months, from vandalism to “coning” pranks to even being used as rolling hookup spots, and that’s not to mention all the trouble they caused by brigading to the same address or losing games of chicken with a semi and a firetruck. We’re not sure what to make of all this; despite our somewhat snarky commentary on the company’s woes, we take little pleasure in this development other than to the degree it probably increases roadway safety in the former test cities. We really do want to see self-driving cars succeed, at least for certain use cases, but it seems like this is a case of too much, too soon for the technology we currently have at our disposal.

Continue reading “Hackaday Links: October 29, 2023”

Impostor Syndrome: It’s Not Your Fault!

[Crispernaki] and I have something in common. We both saw this awesome project that made a scroll wheel out of a VHS head back in 2010, and wanted to make one. We both wanted to put our own spin on the gadget, (tee-hee), discovered that it was harder than either of us wanted to commit to, and gave up.

Flash forward about a million Internet years, and [crispernaki] finally made his and wrote it up. The only problem is that it was too easy. In 2010, making USB gadgets was a lot more involved than it is today. (Back then, we had to chisel device descriptors on stone tablets.) Nowadays, the firmware is just a matter of importing the right library, and the hardware is a magnetic rotation sensor breakout board, a magnet, and super glue. Cheap, and easy.

All of this led our hero to feeling insecure. After all, a hack that beat him a dozen years ago turned out to be dead easy today. Maybe it was too easy? Maybe he wasn’t a “real” hacker? These are the signs of impostor syndrome – that feeling that just because you aren’t the world’s best, or climbing the highest mountain, or hacking the hardest project, you’re not worthy.

Well, listen up. Impostors don’t finish projects, and impostors don’t write them up to share with all the rest of us. By actually doing the thing – hacking the hack – all chances of being a fake are ruled out. The proof is sitting there on your desk, in all its Altoids-tin glory.

And it’s not your fault that it was too easy this time around. You can’t do anything to turn back the hands of time, to make the project any harder these days, or to undo the decade of hacker technical progress on the software side, much less change the global economy to make a magnetic sensor unobtainable again. The world improved, you got your hack done, and that’s that. Congratulations! (Now where do I buy some of those on-axis magnets?)

Hackaday Podcast 242: Mechanical Math, KaboomBox, And Racing The Beam

This week, Editor-in-Chief Elliot Williams and Kristina Panos met up from their separate but equally pin drop-quiet offices to discuss the best hacks of the previous week. Well, we liked these one, anyway.

First up in the news, it’s finally time for Supercon! So we’ll see you there? If not, be sure to check out the talks as we live-stream them on our YouTube channel!

Don’t forget — this is your last weekend to enter the 2023 Halloween Hackfest contest, which runs until 9 AM PDT on October 31st. Arduino are joining the fun this year and are offering some spooky treats in addition to the $150 DigiKey gift cards for the top three entrants.

It’s time for a new What’s That Sound, and Kristina was able to stump Elliot with this one. She’ll have to think of some more weirdo sounds, it seems.

Then it’s on to the hacks, beginning with an insanely complex mechanical central air data computer super-teardown from [Ken Shirriff]. We also learned that you can 3D-print springs and things by using a rod as your bed, and we learned whole lot about rolling your own electrolytic capacitors from someone who got to visit a factory.

From there we take a look at a Commodore Datassette drive that sings barbershop, customizing printf, and a really cool dress made of Polymer-dispersed Liquid Crystal (PDLC) panels. Finally we talk about racing the beam when it comes to game graphics, and say goodbye to Kristina’s series on USPS technology.

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

Download and savor at your leisure.

Continue reading “Hackaday Podcast 242: Mechanical Math, KaboomBox, And Racing The Beam”

This Week In Security: 1Password, Polyglots, And Roundcube

This week we got news of a security incident at 1Password, and we’re certain we aren’t the only ones hoping it’s not a repeat of what happened at LastPass. 1Password has released a PDF report on the incident, and while there are a few potentially worrying details, put into context it doesn’t look too bad.

The first sign that something might be amiss was an email from Okta on September 29th — a report of the current list of account administrators. Okta provides authentication and Single Sign-On (SSO) capabilities, and 1Password uses those services to manage user accounts and authentication. The fact that this report was generated without anyone from 1Password requesting it was a sign of potential problems.

And here’s the point where a 1Password employee was paying attention and saved the day, by alerting the security team to the unrequested report. That employee had been working with Okta support, and sent a browser session snapshot for Okta to troubleshoot. That data includes session cookies, and it was determined that someone unauthorized managed to access the snapshot and hijack the session, Firesheep style.

Okta logs seemed to indicate that the snapshot hadn’t been accessed, and there weren’t any records of other Okta customers being breached in this way. This pointed at the employee laptop. The report states that it has been taken offline, which is good. Any time you suspect malicious action on a company machine, the right answer is power it off right away, and start the investigation.

And here’s the one part of the story that gives some pause. Someone from 1Password responded to the possible incident by scanning the laptop with the free edition of Malwarebytes. Now don’t get us wrong, Malwarebytes is a great product for finding and cleaning the sort of garden-variety malware we tend to find on family members’ computers. The on-demand scanning of Malwarebytes free just isn’t designed for detecting bespoke malicious tools like a password management company should expect to be faced with.

But that turns out to be a bit of a moot point, as the real root cause was a compromised account in the Okta customer support system, as revealed on the 20th. The Okta report talks about stolen credentials, which raises a real question about why Okta support accounts aren’t all using two-factor authentication.

Continue reading “This Week In Security: 1Password, Polyglots, And Roundcube”

Retrotechtacular: Crash Testing Truck Attenuators, For Science

There are those among us who might bristle at something from the early 1980s qualifying for “Retrotechtacular” coverage, but it’s been more than 40 years since the California Department of Transportation’s truck-mounted attenuators crash testing efforts, so we guess it is what it is.

If you’re worried that you have no idea what a “truck-mounted attenuator” might be, relax — you’ve probably seen these devices attached to the backs of trucks in highway work zones. They generally look like large boxes attached to frames at the rear of the truck which are intended to soften the blow should a car somehow not see the giant orange truck covered with flashing lights and drive into the rear of it at highway speeds. Truck-mounted attenuators are common today, but back in 1982 when this film was produced, the idea was still novel enough to justify crash-testing potential designs.

Continue reading “Retrotechtacular: Crash Testing Truck Attenuators, For Science”

Simple Badge Is Simple, But It’s Yours

Making conference badges, official or unofficial, has become an art form. It can get pretty serious. #badgelife.

But DEFCON-goers aren’t the only people making fancy personalized nametags. Hams often had callsign badges going back as far as I can remember. Most were made of engraved plastic, but, at some point, it became common to put something like a flashing LED on the top of the engraved antenna tower or maybe something blinking Morse code.

Going back to that simpler time, I wanted to see if I could make my own badge out of easily accessible modules. How easy can it be? Let’s find out. Along the way, we’ll talk about multicore programming, critical sections, namespaces, and jamming images into C++ code. I’ll also show you how to hijack the C preprocessor to create a little scripting language to make the badge easier to configure.

Bottom Line Up Front

The photo shows the Pico badge. It has an RP2040 CPU but not a proper Raspberry Pi Pico. The Waveshare RP2040-Plus clone has a battery connector and charger. It also has a reset button, and this one has 16 MB of flash, but you don’t need that much. The LCD is also a Waveshare product. (This just happened to work out. I bought all of this stuff, and I don’t even know anyone at Waveshare.) The only other thing you need is a USB C cable and a battery with an MX 1.25 connector on it with the correct polarity. Hardware done! Time for software.

Continue reading “Simple Badge Is Simple, But It’s Yours”