<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Sep 5, 2013, at 10:00 , Benjamin Smedberg <<a href="mailto:benjamin@smedbergs.us">benjamin@smedbergs.us</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">As I just mentioned to Richard, I'm not sure that in general I *want* hidden plugins to be more discoverable. I think the common case for everything except Flash is that you're being attacked by a compromised ad network and in those cases we don't want to throw this prompt up in the user's face.<br></div></blockquote></div><br><div><br></div><div>Do you have any numbers, any statistics, anything at all to back that assessment up? I realize that those are the visible ones, and those are the problems… but my experience is very, very different from that. The vast majority of FireBreath plugins, as I have mentioned, are hidden and are *not* malicious. How many such individual plugins are there that are malicious? How do they normally get installed? I can understand a concern about plugins with security vulnerabilities, but I have never even heard of a widespread plugin that was actually an attack.</div><div><br></div><div>Thanks,</div><div><br></div><div>Richard</div></body></html>