<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Digital Forensic Approaches for Amazon Alexa Ecosystem · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1707.08696/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1707.08696/feed.xml" rel="self" type="application/rss+xml" /><item><title>Digital Forensic Approaches for Amazon Alexa Ecosystem — mentioned by kennu</title><link>https://news.ycombinator.com/item?id=21501618</link><guid isPermaLink="false">urn:hackerpapers:mention:1707.08696:21501618</guid><pubDate>Mon, 11 Nov 2019 02:19:08 GMT</pubDate><description>&lt;p&gt;I don&amp;#x27;t think that&amp;#x27;s entirely true. People have analyzed the network traffic and found it to match the wakewords. The hardware and software architecture has also been analyzed and my understanding is that the wakeword functionality is implemented by secondary low-power hardware, which turns on the main system only after hearing the wakeword. Of course, anything is possible in theory and I wouldn&amp;#x27;t be surprised to see some targeted attacks happening occasionally, but that&amp;#x27;s pretty different from massive always-on 24/7 audio collection from all consumers. Some related links…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1707.08696/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
