LWN: Comments on "Horn: Mitigations are attack surface, too" https://lwn.net/Articles/812296/ This is a special feed containing comments posted to the individual LWN article titled "Horn: Mitigations are attack surface, too". en-us Fri, 03 Oct 2025 04:58:39 +0000 Fri, 03 Oct 2025 04:58:39 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Horn: Mitigations are attack surface, too https://lwn.net/Articles/812709/ https://lwn.net/Articles/812709/ immibis <div class="FormattedComment"> And then they can contribute that code upstream, to comply.<br> </div> Tue, 18 Feb 2020 10:24:34 +0000 Horn: Mitigations are attack surface, too https://lwn.net/Articles/812708/ https://lwn.net/Articles/812708/ immibis <div class="FormattedComment"> Upstream from Samsung is Google.<br> </div> Tue, 18 Feb 2020 10:23:54 +0000 Horn: Mitigations are attack surface, too https://lwn.net/Articles/812552/ https://lwn.net/Articles/812552/ tuna <div class="FormattedComment"> You can compare how much freedom end users had on Windows phones. On some of Android phones (like Sony XPeria Z3) it is possible to run a fully free operating system (with the need for some blobs for certain hardware enablement).<br> </div> Sat, 15 Feb 2020 11:50:54 +0000 Horn: Mitigations are attack surface, too https://lwn.net/Articles/812544/ https://lwn.net/Articles/812544/ oldtomas <div class="FormattedComment"> " [...] freedom for manufacturers which makes it possible to have freedom for end users as well"<br> <p> Now this is one bold claim.<br> <p> Based on experience, I'd say the results are very mixed, in both directions?<br> </div> Sat, 15 Feb 2020 10:23:17 +0000 Horn: Mitigations are attack surface, too https://lwn.net/Articles/812528/ https://lwn.net/Articles/812528/ xophos <div class="FormattedComment"> Researchers care about actual safety. The it security industry just sells snake oil to make money.<br> </div> Sat, 15 Feb 2020 07:10:55 +0000 Horn: Mitigations are attack surface, too https://lwn.net/Articles/812456/ https://lwn.net/Articles/812456/ dvdeug <div class="FormattedComment"> I don't think there's any claim that Linux could have succeeded without being Free Software. I doubt going semi-free would have worked; a lot of early distribution was done on commercial CD-ROMs, that couldn't have been done with a NC license, and many commercial companies kicked in over the years. We can debate whether the BSD license would have worked; I think GPL is better, but the AT&amp;T lawsuit made the legal status of BSD between 1992 and 1994 confusing, which gave Linux some time to grab market and mind share. <br> <p> I think it's clear that Linux and the BSDs smoked commercial Unixes, and I think it's clear that's because they were open systems that both individual hackers and various companies could use and distribute. MacOS X is the major commercial Unix left, and they're playing a game that only Apple really successfully plays. The rest is legacy systems and possibly certain huge or specialized systems.<br> </div> Fri, 14 Feb 2020 09:24:24 +0000 Horn: Mitigations are attack surface, too https://lwn.net/Articles/812369/ https://lwn.net/Articles/812369/ tuna <div class="FormattedComment"> What would happen if upstream would not accept the contributed code? It would be pretty crazy for Google to have their trademark policy depend on Linus Thorvalds and others.<br> </div> Thu, 13 Feb 2020 13:32:55 +0000 Horn: Mitigations are attack surface, too https://lwn.net/Articles/812356/ https://lwn.net/Articles/812356/ bangert <div class="FormattedComment"> It is sad how obvious his conclusions are.<br> <p> There is a huge disconnect between the top security researchers and the bulk of the IT Security industry - to the degree that they are actually saying the opposite of each other.<br> </div> Thu, 13 Feb 2020 08:58:57 +0000 Horn: Mitigations are attack surface, too https://lwn.net/Articles/812353/ https://lwn.net/Articles/812353/ tuna <div class="FormattedComment"> If you want to do new unique hardware (like little.Big cores, double screens, other stuff) you will need to change the core system. It is actually about freedom for manufacturers which makes it possible to have freedom for end users as well.<br> </div> Thu, 13 Feb 2020 08:06:43 +0000 Horn: Mitigations are attack surface, too https://lwn.net/Articles/812351/ https://lwn.net/Articles/812351/ ILMostro <div class="FormattedComment"> The question then becomes, did Linux succeed in-spite of GPL or because of it? And, where does it go through Google's vision?<br> <p> </div> Thu, 13 Feb 2020 08:01:35 +0000 Horn: Mitigations are attack surface, too https://lwn.net/Articles/812346/ https://lwn.net/Articles/812346/ pj <div class="FormattedComment"> <font class="QuotedText">&gt; Allowing "fragmentation" (aka "proprietary value add") is the primary reason Android succeeded.</font><br> <p> IMO "proprietary value add" belongs as apps or as a HAL with a standardized API (ala Project Treble), not in Android core. Requiring non-software companies to maintain their own fork of an OS is just insane.<br> <p> </div> Thu, 13 Feb 2020 04:30:18 +0000 Horn: Mitigations are attack surface, too https://lwn.net/Articles/812337/ https://lwn.net/Articles/812337/ pizza <div class="FormattedComment"> Allowing "fragmentation" (aka "proprietary value add") is the primary reason Android succeeded.<br> <p> As for upstream contribution, remember this is the same Google that replaced every GPL userspace with a more permissively licensed one. Meanwhile, they're working on doing that for the Linux kernel too.<br> <p> Meanwhile, when Google attempts to attach conditions to the use of its trademarks have them up on antitrust charges in multiple jurisdictions.<br> <p> <p> </div> Thu, 13 Feb 2020 01:23:33 +0000 Horn: Mitigations are attack surface, too https://lwn.net/Articles/812335/ https://lwn.net/Articles/812335/ Deleted user 129183 <div class="FormattedComment"> <font class="QuotedText">&gt; How so?</font><br> <p> They encouraged, or at least didn’t try to prevent, the Android fragmentation. They had the tools to discourage it: for example, they could have not allowed to use Android trademark by vendors who tried to add ‘device-specific code’ without contributing it to the upstream. So we ended with completely dysfunctional “ecosystem” where there’s no one “Android” system: instead, we have millions of incompatible forks, with all its implications, including security implications, as described in the article.<br> </div> Wed, 12 Feb 2020 23:39:31 +0000 Horn: Mitigations are attack surface, too https://lwn.net/Articles/812322/ https://lwn.net/Articles/812322/ clugstj <div class="FormattedComment"> Just generic Google bashing<br> </div> Wed, 12 Feb 2020 20:12:08 +0000 Horn: Mitigations are attack surface, too https://lwn.net/Articles/812312/ https://lwn.net/Articles/812312/ pkern <div class="FormattedComment"> How so? After all this seems to have been an out of tree patch by Samsung?<br> </div> Wed, 12 Feb 2020 18:48:07 +0000 Horn: Mitigations are attack surface, too https://lwn.net/Articles/812305/ https://lwn.net/Articles/812305/ Deleted user 129183 <div class="FormattedComment"> Google heroically solving problems that they caused themselves, I see.<br> </div> Wed, 12 Feb 2020 18:10:38 +0000