It is interesting to see the wide coverage of a police investigation looking to harvest data from the Amazon Echo, the always-listening home automation device you may know as Alexa. A murder investigation has led them to issue Amazon a warrant to fork over any recordings made during the time of a crime, and Amazon has so far refused.
Not too long ago, this is the sort of news would have been discussed on Hackaday but the rest of my family would have never heard about it. Now we just need to get everyone to think one step beyond this and we’ll be getting somewhere.
What isn’t being discussed here is more of concern to me. How many of you have a piece of tape over your webcam right now? Why did you do that? It’s because we know there are compromised systems that allow attackers to turn on the camera remotely. Don’t we have to assume that this will eventually happen with the Echo as well? Police warrants likely to affect far less users than account breaches like the massive ones we’ve seen with password data.
All of the major voice activated technologies assert that their products are only listening for the trigger words. In this case, police aren’t just looking for a recording of someone saying “Alexa, help I’m being attacked by…” but for any question to Alexa that would put the suspect at the scene of the crime at a specific time. Put yourself in the mind of a black hat. If you could design malware to trigger on the word “Visa” you can probably catch a user giving their credit card number over the phone. This is, of course, a big step beyond the data already stored from normal use of the system.
It’s not surprising that Amazon would be served a warrant for this data. You would expect phone records (although not recordings of the calls) to be reviewed in any murder case. Already disclosed in this case is that a smart water meter from the home reported a rather large water usage during the time of the murder — a piece of evidence that may be used to indicate a crime scene clean-up effort.
What’s newsworthy here is that people who don’t normally think about device security are now wondering what their voice-controlled tech actually hears them say. And this is a step in the right direction.
Tod Kurt knows a thing or two about IoT devices. As the creator of blink(1), he’s shipped over 30,000 units that are now out in the wild and in use for custom signaling on everything from compile status to those emotionally important social media indicators. His talk at the 2016 Hackaday SuperConference covers the last mile that bridges your Internet of Things devices with its intended use. This is where IoT actually happens, and of course where it usually goes astray.
Continue reading “Solving IoT Problems with Node.js for Hardware”
What will next generation space suits look like? Kari Love is making the case that new space suits will exhibit the best in soft robot technology. The problem is that most people don’t really understand much about soft robots, or about space for that matter. Her talk at the Hackaday SuperConference explores the research she has been doing into future generations of space suits. Check out the video below and then join us after the break for more on this topic.
Continue reading “Softer Side of Robots is Future of Space”
Last week, Hackaday had the chance to tour NASA’s Jet Propulsion Laboratory (JPL) in Pasadena, California. Tours are given all the time at JPL, but ours was special. Steve Collins invited us, and acted as our tour guide, and a new friendship with Michelle Easter got us a look inside the labs where equipment for the 2020 Mars mission is being built.
Continue reading “Extra Curricular Tour of NASA’s Jet Propulsion Laboratory”
Samy Kamkar is well known for many things, but lately it has been his hardware security hacks that have been turning heads. The nice thing to know is that, despite not having a background in hardware, Samy is able to run with the best of hardware researchers. At the Hackaday SuperConference he offered words of advice for anyone trying to walk the path of discovery with an exciting new piece of electronics. One might say it’s a crash-course in how to be a hardware hacker.
Continue reading “Samy Kamkar Illustrates How to Be a Hardware Hacker”
Bodo Hoenen and his family had an incredible scare. His daughter, Lorelei, suddenly became ill and quickly went from a happy and healthy girl to one fighting just to breathe and unable to move her own body. The culprit was elevated brain and spinal pressure due to a condition called AFM. This is a rare polio-like condition which is very serious, often fatal. Fortunately, Lorelei is doing much better. But this health crisis resulted in nearly complete paralysis of her left upper arm.
Taking an active role in the health of your child is instinctual with parents. Bodo’s family worked with health professionals to develop therapies to help rehabilitate Lorelei’s arm. But researching the problem showed that success in this area is very rare. So like any good hacker he set out to see if they could go beyond the traditional to build something to increase Lorelei’s odds.
What resulted is a wearable prosthesis which assists elbow movement by detecting the weak signals from her bicep and tricep to control an actuator which moves her arm. Help came in from all over the world during the prototyping process and the project, which was the topic of Bodo Hoenen’s talk at the Hackaday SuperConference, is still ongoing. Check that out below and the join us after the break for more details.
Continue reading “This DIY Wearable Assist Goes Beyond Traditional Therapy”
Today Pebble has announced that it will cease all hardware production. Their outstanding Kickstarter deliveries will not be fulfilled but refunds will be issued. Warranties on all existing hardware will no longer be honored. However, the existing smartwatch service will continue… for now.
This isn’t unexpected, we ran an article yesterday about the all-but-certain rumors FitBit had acquired Pebble (and what led to that). Today’s news has turned speculation about Pebble 2 and Pebble Core Kickstarter campaigns into reality. You won’t get your hands on that fancy new hardware, but at least backers will have the money returned.
Perhaps the most interesting part of today’s blog post from the founder of Pebble, Eric Migicovsky, is about how this impacts more than a million watches already in the wild. Service will continue but (wait for it) “Pebble functionality or service quality may be reduced in the future.”
It’s not like this is a unique problem. Devices purchased by consumers that are dependent on phoning home to a server to function is a mounting issue. Earlier this year [Elliot Williams] coined this issue “Obsolescence as a Service” which is quite fitting. Anyone who still has a functional first generation iPad has enjoyed reduced quality of service; without available upgrades, you are unable to install most apps. It’s zombie hardware; electrons still flow but there’s no brain activity.
One of the perks associated with FitBit acquiring Pebble is that they have decided to keep those servers running for watches in the field. A cynic might look at the acquisition as FitBit reducing competition in the market — they wouldn’t have let hardware production cease if they were interested in acquiring the user base. At some point, those servers will stop working and the watches won’t be so smart after all. FitBit owns the IP which means they could open source everything needed for the community to build their own server infrastructure. When service quality “reduced in the future” that’s exactly what we want to see happen.