What’s The Deal With Chromium On Linux? Google At Odds With Package Maintainers

Linux users are more likely than most to be familiar with Chromium, Google’s the free and open source web project that serves as the basis for their wildly popular Chrome. Since the project’s inception over a decade ago, users have been able to compile the BSD licensed code into a browser that’s almost the same as the closed-source Chrome. As such, most distributions offer their own package for the browser and some even include it in the base install. Unfortunately, that may be changing soon.

A post made earlier this month to the official Chromium Blog explained that an audit had determined “third-party Chromium based browsers” were using APIs that were intended only for Google’s internal use. In response, any browser attempting to access features such as Chrome Sync with an unofficial API key would be prevented from doing so after March 15th.

To the average Chromium user, this doesn’t sound like much of a problem. In fact, you might even assume it doesn’t apply to you. The language used in the post makes it sound like Google is referring to browsers which are spun off of the Chromium codebase, and at least in part, they are. But the search giant is also using this opportunity to codify their belief that the only official Chromium builds are the ones that they provide themselves. With that simple change, anyone using a distribution-specific build of Chromium just became persona non grata.

Unhappy with the idea of giving users a semi-functional browser, the Chromium maintainers for several distributions such as Arch Linux and Fedora have said they’re considering pulling the package from their respective repositories altogether. With a Google representative confirming the change is coming regardless of community feedback, it seems likely more distributions will follow suit.

Continue reading “What’s The Deal With Chromium On Linux? Google At Odds With Package Maintainers”

Failed Test Could Further Delay NASA’s Troubled SLS Rocket

The January 16th “Green Run” test of NASA’s Space Launch System (SLS) was intended to be the final milestone before the super heavy-lift booster would be moved to Cape Canaveral ahead of its inaugural Artemis I mission in November 2021. The full duration static fire test was designed to simulate a typical launch, with the rocket’s main engines burning for approximately eight minutes at maximum power. But despite a thunderous start start, the vehicle’s onboard systems triggered an automatic abort after just 67 seconds; making it the latest in a long line of disappointments surrounding the controversial booster.

When it was proposed in 2011, the SLS seemed so simple. Rather than spending the time and money required to develop a completely new rocket, the super heavy-lift booster would be based on lightly modified versions of Space Shuttle components. All engineers had to do was attach four of the Orbiter’s RS-25 engines to the bottom of an enlarged External Tank and strap on a pair of similarly elongated Solid Rocket Boosters. In place of the complex winged Orbiter, crew and cargo would ride atop the rocket using an upper stage and capsule not unlike what was used in the Apollo program.

The SLS core stage is rolled out for testing.

There’s very little that could be called “easy” when it comes to spaceflight, but the SLS was certainly designed to take the path of least resistance. By using flight-proven components assembled in existing production facilities, NASA estimated that the first SLS could be ready for a test flight in 2016.

If everything went according to schedule, the agency expected it would be ready to send astronauts beyond low Earth orbit by the early 2020s. Just in time to meet the aspirational goals laid out by President Obama in a 2010 speech at Kennedy Space Center, including the crewed exploitation of a nearby asteroid by 2025 and a potential mission to Mars in the 2030s.

But of course, none of that ever happened. By the time SLS was expected to make its first flight in 2016, with nearly $10 billion already spent on the program, only a few structural test articles had actually been assembled. Each year NASA pushed back the date for the booster’s first shakedown flight, as the project sailed past deadlines in 2017, 2018, 2019, and 2020. After the recent engine test ended before engineers were able to collect the data necessary to ensure the vehicle could safely perform a full-duration burn, outgoing NASA Administrator Jim Bridenstine said it was too early to tell if the booster would still fly this year.

What went wrong? As commercial entities like SpaceX and Blue Origin move in leaps and bounds, NASA seems stuck in the past. How did such a comparatively simple project get so far behind schedule and over budget?

Continue reading “Failed Test Could Further Delay NASA’s Troubled SLS Rocket”

New Parts, New Hacks

The biggest news this week is that Raspberry Pi is no longer synonymous with single-board Linux computers: they’re dipping their toes into the microcontroller business with their first chip: the RP2040, and the supporting breakout board, the Pico. It’s an affordable, capable microcontroller being made by a firm that’s never made microcontrollers before, so that’s newsy.

The Hackaday comments lit on fire about this chip, with some fraction of the commenters lamenting the lack of wireless radios onboard. It’s a glass-half-full thing, I guess, but the RP2040 isn’t an ESP32, folks. It’s something else. And it’s got a hardware trick up its sleeve that really tickles my fancy — the programmable input/output (PIO) units.

The other half of the commenters were, like me, salivating about getting to try out some of the new features. The PIO, of course, was high on that list, but this chip also caters to folks who are doing high-speed DSP, with fast multiplication routines burnt into ROM and a nice accumulator. (You know you’re a microcontroller nerd when you’re reading through a 663-page datasheet and thinking about all the funny ways you can use and/or abuse the hardware peripherals.)

All chip designs are compromises. Nothing can do everything. The new peripherals, novel combinations of old elements, and just pleasant design decisions, open up new opportunities if you’re willing to seek them out. When the ESP32 was new, I was looking at their oddball parallel-I2S hardware and thinking what kind of crazy hacks that would enable, and clever hackers have proven me right. I’d put my money on the PIO being similar.

New chips open up new possibilities for hacks. What are you going to do with them?

Meet The Magic Eye Vacuum Tube

Vacuum tubes ruled electronics for several decades and while you might think of them as simple devices analogous to a transistor or FET, there were many special types. We’re all familiar with nixie tubes that act as numeric displays, and there are other specialty tubes that work as a photomultiplier, to detect radiation, or even generate microwaves. But one of the most peculiar and distinctive specialty tubes has an intriguing name: a magic eye tube. When viewed from the top, you see a visual indication that rotates around a central point, the out ring glowing while the inner is dark, like an iris and pupil.

By [Quark48] – CC BY-SA 2.0

These tubes date back to the RCA 6E5 in 1935. At the time, test equipment that used needles was expensive to make, so there was always a push to replace them with something cheaper.  They were something like a stunted cathode ray tube. In fact, the inventor, Allen DuMont, was well known for innovations in television. An anode held a coating that would glow when hit with electrons — usually green, but sometimes other colors. Later tubes would show a stripe going up and down the tube instead of a circle, but you still call them magic eyes.

The indicator part of this virtual meter took the form of a shadow. Based on the applied signal, the shadow would be larger or smaller. Many tubes also contained a triode which would drive the tube from a signal.

There’s a great web site full of information on these venerable tubes and it has examples of these tubes appearing in plenty of things. They frequently appeared in service equipment, radios, and tape recorders. They even appeared in pro audio equipment like the Binson Echorec echo-delay unit.

Continue reading “Meet The Magic Eye Vacuum Tube”

Hackaday Podcast 102: Raspberry Pi Microcontroller, Microphone Killswitch, And A 45-Degree 3D-Printer

Hackaday editors Elliot Williams and Mike Szczys sift through a week of excellent hacks. Big news is of course the Raspberry Pi microcontroller which Elliot had a few weeks to play around with on the bench before the announcement — it has some fascinating programmable modules (PIO) built in! Philips designed an LED light bulb that under-drives the LEDs for efficiency and long life. And Amazon added a nice little hardware disable circuit for the microphone in the Echo Flex — a rather extreme teardown shows how they did it. Plus we talk about an open source long-range RC protocol, wall-sized pen plotter art, and a 3D printer that angles the nozzle to avoid needing support.

Take a look at the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!

Direct download (~65 MB)

Places to follow Hackaday podcasts:

Continue reading “Hackaday Podcast 102: Raspberry Pi Microcontroller, Microphone Killswitch, And A 45-Degree 3D-Printer”

This Week In Security: OpenWRT, Favicons, And Steganographia

OpenWRT is one of my absolute favorite projects, but it’s had a rough week. First off, the official OpenWRT forums is carrying a notice that one of the administrator accounts was accessed, and the userlist was downloaded by an unknown malicious actor. That list is known to include email addresses and usernames. It does not appear that password hashes were exposed, but just to be sure, a password expiration has been triggered for all users.

OpenWRT Security Notice

The second OpenWRT problem is a set of recently discovered vulnerabilities in Dnsmasq, a package installed by default in OpenWRT images. Of those vulnerabilities, four are buffer overflows, and three are weaknesses in how DNS responses are checked — potentially allowing cache poisoning. These seven vulnerabilities are collectively known as DNSpooq (Whitepaper PDF). Continue reading “This Week In Security: OpenWRT, Favicons, And Steganographia”

A Few Of My Favorite Things: Amateur Radio

Hackaday has among its staff a significant number of writers who also hold amateur radio licenses. We’re hardware folks at heart, so we like our radios homebrew, and we’re never happier than when we’re working at high frequencies.

Amateur radio is a multi-faceted hobby, there’s just so much that’s incredibly interesting about it. It’s a shame then that as a community we sometimes get bogged down with negativity when debating the minutia. So today let’s talk about a few of my favourite things about the hobby of amateur radio. I hope that you’ll find them interesting and entertaining, and in turn share your own favorite things in the comments below.

Continue reading “A Few Of My Favorite Things: Amateur Radio”