Airports Are Now AirBNBs For Honeybees

In the summer of 2012, honeybees swarmed the Pittsburgh airport, probably because the conditions are favorable there. Like many airports, the tarmac is surrounded by wild, wide-open fields that exist to contain the cacophony. And a couple of nearby creeks are dotted with plenty of forage-worthy wildflowers.

Free honey? Wúnderbar!

Now, nearly a decade later, the airport is home to 110 colonies that house around 4 million honeybees. And they aren’t alone. Several other US airports are getting in on the apiary action, including O’Hare, Sea-Tac, and Minneapolis-St. Paul.

The relationship between honeybees and airports is a symbiotic one — the honey the bees produce is a litmus test for air pollution levels around the airport, which must fall within regulations. German airports have employed bees as ‘bio-detectives’ for over twenty years, and they give the honey away for free inside the terminal. It’s okay, though — analysis reveals that the hydrocarbon and heavy metal levels in the airport honey aren’t any higher than honey from non-industrial bees.

Given that honeybees pollinate around $15 billion in crops annually in the US alone, it’s a wonder that we aren’t doing everything possible to fight colony collapse disorder and other problems around the world. This mysterious issue has grown in the last few years, and 2020 saw highest death toll since 2016. Colony collapse disorder aside, plenty of problems persist for our fuzzy friends — pests, pesticides, pathogens, and poor nutrition.

What’s the deal with bees, anyway? How do they fly? Because they aren’t supposed to fly.

This Week In Security: Dan Kaminsky, Banned From Kernel Development, Ransomware, And The Pentagon’s IPv4 Addresses

This week we’re starting off with a somber note, as Dan Kaminsky passed at only 42, of diabetic ketoacidosis. Dan made a name for himself by noticing a weakness in DNS response verification that could allow attackers to poison a target DNS resolver’s cache. A theoretical attack was known, where spoofed DNS responses could collide with requests, but Time-To-Live values meant that DNS requests only go out once per eight hours or so. The breakthrough was realizing that the TTL limitation could be bypassed by requesting bogus subdomains, and aiming the spoofed responses at those requests. This simple technique transformed a theoretical attack that would take 87 years to a very real 10 second attack. Check out the period video after the break, where Dan talked about his efforts in getting the problem fixed.
Continue reading “This Week In Security: Dan Kaminsky, Banned From Kernel Development, Ransomware, And The Pentagon’s IPv4 Addresses”

Looks Like A Pi Zero, Is Actually An ESP32 Development Board

ATMegaZero ESP32- S2, showing optional color-coded 40-pin header (top)

The ATMegaZero ESP32-S2 is currently being funded with a campaign on GroupGets, and it’s a microcontroller board modeled after the Raspberry Pi Zero’s form factor. That means instead of the embedded Linux system most of us know and love, it’s an ESP32-based development board with the same shape and 40-pin GPIO header as the Pi Zero. As a bonus, it has some neat features like a connector for inexpensive SSD1306 and SH1106-based OLED displays.

Being able to use existing accessories can go a long way towards easing a project’s creation, and leveraging that is one of the reasons for sharing the Pi Zero form factor. Ease of use is also one of the goals, so the boards will ship with CircuitPython (derived from MicroPython), and can also be used with the Arduino IDE.

If a microcontroller board using the Pi Zero form factor looks a bit familiar, you might be remembering the original ATMegaZero which was based on the Atmel ATMega32U4, but to get wireless communications one needed to attach a separate ESP8266 module. This newer board keeps the ATMegaZero name and footprint, but now uses the Espressif ESP32-S2 to provide all the necessary functions.

CircuitPython has been a feature in a wide variety of projects and hacks we’ve seen here at Hackaday, and it’s a fine way to make a microcontroller board easy to use right out of the box.

An Arduino With A Floppy Drive

For many of us the passing of the floppy disk is unlamented, but there remains a corps of experimenters for whom the classic removable storage format still holds some fascination. The interface for a floppy drive might have required some complexity back in the days of 8-bit microcomputers, but even for today’s less accomplished microcontrollers it’s a surprisingly straightforward hardware prospect. [David Hansel] shows us this in style, with a floppy interface, software library, and even a rudimentary DOS, for the humble Arduino Uno.

The library provides functions to allow low level work with floppy disks, to read them sector by sector. In addition it incorporates the FatFS library for MS-DOS FAT file-level access, and finally the ArduDOS environment which allows browsing of files on a floppy. The pictures show a 3.5″ drive, but it also supports 5.25″ units and both DD and HD drives. We can see that it will be extremely useful to anyone working with retrocomputer software who is trying to retrieve old disks, and we look forward to seeing it incorporated in some retrocomputer projects.

Of course, Arduino owners needn’t have all the fun when it comes to floppy disks, the Raspberry Pi gets a look-in too.