In times like these, we all need to look beyond ourselves. This project might help: OnStep is an open-source telescope controller, a device that controls a telescope to point at something interesting in the sky. Want to take a look at M31? Use an app on a PC or smartphone, select the object and the OnStep will pan and tilt your telescope until the Andromeda Galaxy pops into view.
Continue reading “Open Source Telescope Controller Puts Smart Features In Old Telescopes”
OpenWrt announced a problem in opkg, their super-lightweight package manager. OpenWrt’s target hardware, routers, make for an interesting security challenge. A Linux install that fits in just 4 MB of flash memory is a minor miracle in itself, and many compromises had to be made. In this case, we’re interested in the lack of SSL: a 4 MB install just can’t include SSL support. As a result, the package manager can’t rely on HTTPS for secure downloads. Instead, opkg first downloads a pair of files: A list of packages, which contains a SHA256 of each package, and then a second file containing an Ed25519 signature. When an individual package is installed, the SHA256 hash of the downloaded package can be compared with the hash provided in the list of packages.
It’s a valid approach, but there was a bug, discovered by [Guido Vranken], in how opkg reads the hash values from the package list. The leading space triggers some questionable pointer arithmetic, and as a result, opkg believes the SHA256 hash is simply blank. Rather than fail the install, the hash verification is simply skipped. The result? Opkg is vulnerable to a rather simple man in the middle attack.
OpenWrt doesn’t do any automatic installs or automatic updates, so this vulnerability will likely not be widely abused, but it could be used for a targeted attack. An attacker would need to be in a position to MitM the router’s internet connection while software was being installed. Regardless, make sure you’re running the latest OpenWrt release to mitigate this issue. Via Ars Technica.
With the Linux Kernel version 5.6 being finally released, Wireguard has finally been christened as a stable release. An interesting aside, Google has enabled Wireguard in their Generic Kernel Image (GKI), which may signal more official support for Wireguard VPNs in Android. I’ve also heard reports that one of the larger Android ROM development communities is looking into better system-level Wireguard support as well.
Javascript makes the web work — and has been a constant thorn in the side of good security. For just an example, remember Samy, the worm that took over Myspace in ’05. That cross-site scripting (XSS) attack used a series of techniques to embed Javascript code in a user’s profile. Whenever that profile page was viewed, the embedded JS code would run, and then replicate itself on the page of whoever had the misfortune of falling into the trap.
Today we have much better protections against XSS attacks, and something like that could never happen again, right? Here’s the thing, for every mitigation like Content-Security-Policy, there is a guy like [theMiddle] who’s coming up with new ways to break it. In this case, he realized that a less-than-perfect CSP could be defeated by encoding Javascript inside a .png, and decoding it to deliver the payload.
Ah, systemd. Nothing seems to bring passionate opinions out of the woodwork like a story about it. In this case, it’s a vulnerability found by [Tavis Ormandy] from Google Project Zero. The bug is a race condition, where a cached data structure can be called after it’s already been freed. It’s interesting, because this vulnerability is accessible using DBus, and could potentially be used to get root level access. It was fixed with systemd v220.
For those of you running MacOS on Apple hardware, you might want to check your firmware version. Not because there’s a particularly nasty vulnerability in there, but because firmware updates fail silently during OS updates. What’s worse, Apple isn’t publishing release notes, or even acknowledging the most recent firmware version. A crowd-sourced list of the latest firmware versions is available, and you can try to convince your machine to try again, and hope the firmware update works this time.
Google recently announced a new security tool, USB Keystroke Injection Protection. I assume the nickname, UKIP, isn’t an intentional reference to British politics. Regardless, this project is intended to help protect against the infamous USB Rubber Ducky attack, by trying to differentiate a real user’s typing cadence, as opposed to a malicious device that types implausibly quickly.
While the project is interesting, there are already examples of how to defeat it that amount to simply running the scripts with slight pauses between keystrokes. Time will tell if UKIP turns into a useful mitigation tool. (Get it?)
Remember SMBGhost, the new wormable SMB flaw? Well, there is already a detailed explanation and PoC. This particular PoC is a local-only privilege escalation, but a remote code execution attack is like inevitable, so go make sure you’re patched!
We are hearing so much in the news about shortages of personal protective equipment, or PPE, for healthcare workers. Factories are being asked to perform the impossible when it comes to production be the need is so real, so immediate, and so widespread.
The problem with rapid consumption of PPE is that once it has been exposed to infection, it’s contaminated and can’t be used again. Physically it may be fine, but it retains the capability to infect other people. If there were some way it could be effectively cleaned and decontaminated for re-use, it would reduce the strain on the supply chain and result in a greater availability of PPE for all those who require it.
This is the promise of Battelle’s Critical Care Decontamination System, a shipping-container-sized unit which has received approval from the FDA at break-neck speed.
Most often, humans and robots do not have to work directly together, instead working on different parts in a production pipeline or with the robot performing tasks instead of a human. In such cases any human-robot interaction (HRI) will be superficial. Yet what if humans and robots have to work alongside each other? This is a question which a group of students at MIT’s Computer Science and Artificial Intelligence Lab (CSAIL) have recently studied some answers to.
In their paper on human-robot collaborative tasks (PDF), they cover the three possible models one can use for this kind of interaction: there can be no communication (‘silent’), the communication can be pre-programmed (state machine), or in this case a Markov model-based system. This framework which they demonstrate is called CommPlan and it uses observation data from human subjects to construct a Markov model that can integrate sensor data in order to decide on its next action.
In the experiment they performed (the preparation of a meal; see the embedded video after the break), human subjects had to work alongside a robot. Between the three different approaches, the CommPlan one was the fastest, using voice interaction only when it deemed it to be necessary. The experiment’s subjects expressed hereby a preference for bidirectional communication, much as would occur between human workers.
Vegemite is an Australian staple – a rich, protein-filled sandwich spread with a strong salty flavor. It serves as a great way to add a little umami to any dish, which is the hottest open secret in Australian cuisine this decade. It also works as a servicable conductive paint, which [Alex] used to make this baked good into a musical device.
The basis of the device is a basic audio example sketch running on an Adafruit Circuit Playground Express. The code was tweaked to play a 7-note C major scale. The PCB was then attached to the empanada with toothpicks through each pad, with the baked good itself seemingly connected to the ground plane. The toothpicks through the pads were then coated with Vegemite, and another toothpick treated the same way and used as a stylus. By touching the toothpick to the empanada and one of the pads, the circuit is made, and a note is played.
It’s an impractical way to go about musical performance, sure. But it is an effective demonstration of foodstuffs used in electronics. Calvin Harris did much the same back in 2009, albeit with humans substituting for the delicious pastry. Video after the break.
Continue reading “Empanada Becomes Impractical, Delicious Synth”
Medical device company Medtronic released designs for one of their ventilators to open source for use in the COVID-19 pandemic. This is a laudable action, and there is plenty to glean from the specs (notable is that the planned release is incomplete as of this writing, so more info is on the way). Some initial reactions: medical devices are complicated, requirements specifications are enormous, the bill of materials (BOM) is gigantic, and component sourcing, supply chain, assembly, and testing are just as vital as the design itself.
The pessimist in me says that this design was open sourced for two reasons; to capitalize on an opportunity to get some good press, and to flex in front of the DIY community and convince them that the big boys should be the ones solving the ventilator shortage. The likelihood of anyone actually taking these specs and building it as designed are essentially zero for a variety of reasons, but let’s assume their intent is to give a good starting point for newer changes. The optimist in me says that after what happened to California over the weekend with 170 ventilators arriving broken, it might be nice to have open designs to aid in repair of existing non-functioning ventilators.
The design details released today are for their PB560 model, which was originally launched in 2010 by a company called Covidien, before it merged with Medtronic, so we’re already starting with a device design that’s a decade old. But it’s also a design that has proven itself through widespread use, and this data dump gives us a great look at what actually goes into one of these machines. Let’s take a look.
Continue reading “Professional Ventilator Design Open Sourced Today By Medtronic”
When I started writing my recent article on COVID-19 testing, I assumed that I would be doing a compare and contrast sort of article. Like many people, I assumed that the “gold standard” test would be the reverse transcriptase-polymerase chain reaction (RT-PCR) test that I described in some detail. And indeed it is, but it’s not without its problems, such as the lack of certified labs and the need for trained technicians to run the samples. I also assumed there would be another test, a simple serological test that could use antibodies to discern if there was an active or even a previous, resolved infection.
At the time I wrote the first article, I could find no indication of an immunologic test for COVID-19 (more specifically, a test for SARS-Cov-2, the virus that causes COVID-19). But almost as rapidly as the number of COVID-19 cases rises, the news changes, and it appears that simple, rapidly performed antibody tests are now or soon will be available. They likely won’t replace the gold standard RT-PCR test, but they do stand to be a game-changer for the front line providers and the victims of this disease. So it pays to take a quick look at immunoassays for infectious diseases, and learn how they work.
Continue reading “Coronavirus Testing Follow-Up: Rapid Immunologic Testing”
