<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Keep Me Updated: An Empirical Study of Proprietary Vendor Blobs in Android Firmware · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2410.11075/</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/2410.11075/feed.xml" rel="self" type="application/rss+xml" /><item><title>Keep Me Updated: An Empirical Study of Proprietary Vendor Blobs in Android Firmware — mentioned by protimewaster</title><link>https://news.ycombinator.com/item?id=46679615</link><guid isPermaLink="false">urn:hackerpapers:mention:2410.11075:46679615</guid><pubDate>Mon, 19 Jan 2026 14:50:13 GMT</pubDate><description>&lt;p&gt;That&amp;#x27;s not entirely correct. There are also updates to the baseband, bootloader, binary driver blobs, etc. E.g., the bootloader for the FP3 was set to trust roms signed with the AOSP test keys (https://forum.fairphone.com/t/bootloader-avb-keys-used-in-ro...). That&amp;#x27;s not something fixable by the OS / rom maker. The security issues stemming from such things are likely real, as well. There was a paper released some time back, about binary blobs, that found: &amp;gt; Our results reveal that device manufacturers often neglect vendor blob updates. About 82% of firmware releases contain outdated GPU blobs…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2410.11075/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item></channel></rss>
