<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Adversarial Examples: Attacks and Defenses for Deep Learning · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1712.07107/</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/1712.07107/feed.xml" rel="self" type="application/rss+xml" /><item><title>Adversarial Examples: Attacks and Defenses for Deep Learning — mentioned by madmax96</title><link>https://news.ycombinator.com/item?id=19446863</link><guid isPermaLink="false">urn:hackerpapers:mention:1712.07107:19446863</guid><pubDate>Wed, 20 Mar 2019 20:59:58 GMT</pubDate><description>&lt;p&gt;Consider how widely affected contemporary machine learning models are by adversarial examples [1]. I don&amp;#x27;t know the specific approach used by Tesla or their release process, but I would not be surprised at all if their software has similar shortcomings. Granted, a ton of active research is going on trying to prevent these sorts of problems, but it definitely isn&amp;#x27;t a solved problem. Basically, ask yourself this: how robust is this software? How are you measuring that? [1] https://arxiv.org/pdf/1712.07107.pdf&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1712.07107/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item></channel></rss>
