What you are saying seems to be like saying there are no security issues within Windows as if you run it within a VM it can't escape into the host OS.

These aren't issues with types of plugins, APIs or middleware, they are issues with the Flash Player which is why Adobe patched them, not browser coders:

http://www.cvedetails.com/vulnerability-list/vendor_...

Flash has a long and unenviable history of security problems and has been made obsolete by HTML 5, etc.

Edited by deleted (Sun 06-Aug-17 11:39:47)

In reply to a post by Zadeks:

No, you said "Its not flash that has the security issues".

The vulnerabilities are in the plug-in itself (Flash, Java, etc), not the API. A new API wouldn't have been required if the plug-in didn't have security vulnerabilities, nor would it have needed sandboxing.

I said the reason browsers was dropping it was due to the type of plugin which has security issues, which has been known for years.

Paul

The security issues in Flash are still present, it's just that more of them are mitigated due to the sandbox nature of PPAPI. It's harder to leverage Flash's vulnerabilities because PPAPI doesn't grant as much access to the host system.

http://www.insanitybit.com/2012/08/03/with-chrome-21...

You can think of Flash as a roaring fire, which may be dangerous without proper protection. PPAPI acts as robust fireguard.

I prefer the speedtest that doesn't rely on ancient and dangerous technology. So it's the new labs speedtest for me.

Prefer 'A'.

The needle / speed counter seems more 'FPS happy'. That is to say, it seems to change from one number to the next by cycling through the fractions, rather than skipping from one number to the next. Also, 'B' didn't have any ISPs in the drop down for me.

Add to that the Flash argument, 'A' seems to be the way to go.