An Explosive Look At Detonators

If you’ve ever watched a cartoon where something blows up, you’ve probably seen a detonator — the device with a plunger that, when you push it, some dynamite blows up a bridge or a building or whatever. Detonators may be common in cartoons, but they are very real, and [Our Own Device] talks about some vintage detonators and, along the way, gives a brief history of explosive compounds.

For many years, black powder — a low explosive — was the only game in town. But a flurry of scientific advances brought a new class of high explosives far more powerful than gunpowder. The story of antique explosive factory safety measures, and lack thereof, is also an interesting side detour.

We enjoyed the trip down memory lane. However, if you want to skip the history lesson, jump about 17 minutes in to get a better look at the hardware. The teardown follows soon thereafter. These boxes are built solidly and have many safety features to prevent accidental detonations. One is a dynamo device with some clever mechanisms to ensure that the unit produces enough voltage, the other uses a charged capacitor.

Our usual interest in pyrotechnics is usually aimed more at fireworks. You think of explosives as having an imprecise effect, but that isn’t necessarily the case.

Continue reading “An Explosive Look At Detonators”

This Week In Security: Browser Exploits, Play Protect, And Turn ON Your Firewall!

Google Chrome has done a lot of work on JavaScript performance, pushing the V8 engine to more and more impressive feats. Recently, that optimization has one more piece, the Maglev compiler, which sits between Sparkplug and TurboFan, as a mid-tier optimization step. With a Just In Time (JIT) system, the time saving of code optimization steps has to be carefully weighed against the time costs, and Maglev is another tool in that endless hunt for speed. And with anything this complicated, there’s the occasional flaw found in the system. And of course, because we’re talking about it here, it’s a security vulnerability that results in Remote Code Execution (RCE).

The trick is to use Maglev’s optimization against it. Set up a pair of classes, such that B extends A. Calling new B() results in an attempt to use the constructor from A. Which works, because the compiler checks to make sure that the constructors match before doing so. There’s another way to call a constructor in JS, something like Reflect.construct(B, [], Array);. This calls the B constructor, but indicates that the constructor should return an Array object. You may notice, there’s no array in the A class below. Tricking the compiler into using the parent class constructor in this fashion results in the array being uninitialized, and whatever happens to be in memory will set the length of the array. Continue reading “This Week In Security: Browser Exploits, Play Protect, And Turn ON Your Firewall!”

Debugging A 1950s Computer Sounds Like A Pain

Debugging computers in the 1950s sounds like it wasn’t an easy task. That’s one of the interesting facts from this fascinating talk by [Guy Fedorkow] about the Whirlwind, one of the first digital computers ever built. The development of this remarkable computer started at MIT (Funded by the US Navy) in 1949 as a flight simulator but pivoted to plotting interceptions in the early 1950s. That was because the USSR had just set off their first boosted nuclear bomb, which could be mounted on a missile or bomber. So, the threat of incoming missiles and atomic bombers became real, and the need arose to intercept nuclear bombers.

As a real-time computer, Whirlwind received radar data from radar stations around the US that showed the location of the interceptor and the incoming bogey, then calculated the vector for the two to meet up and, erm, have a frank exchange of views. So, how do you debug one of the first real-time computers? Carefully, it seems.

Continue reading “Debugging A 1950s Computer Sounds Like A Pain”

Commodore Datassette Does Barbershop Quartet

Okay, now this is just plain fun. [Linus Åkesson] modified a Commodore Datassette player to move its “mouth” and, when quadrupled, sing a clever barbershop tune called “Sweet End of Line” that’s a play on “Sweet Adeline“, a top hit from the summer of 1903.

What? Let us explain. Those with Commodore 64s who lacked disk drives often had the Datassette — a magnetic storage tape device, or cassette player used to load and save files. But they couldn’t open the doors themselves with a keypress, and they certainly couldn’t sing barbershop.

First off, [Linus] redirected the current that drives the magnetizing tape head through a speaker coil instead. Then he replaced the motor with a servo that opens the lid from the inside. A simple rubber band pulls the lid back shut. Software-wise, [Linus] is using a timer interrupt to run code that toggles the output signal, the rate of which determines the pitch.

Don’t worry — all of these modifications are reversible, so no Datassettes were truly harmed in the making. Don’t forget to check out the brief build/demo video after the break.

We’ve seen our share of tape players, but we’d never seen one with a crank until recently.

Continue reading “Commodore Datassette Does Barbershop Quartet”