Detect Pepper API Flash in Chrome and force NPAPI version?

Question

Flash version The PPAPI version of Flash is now half the speed of the NPAPI version. This is completely unacceptable. In both cases, using Stage3D and the usual Flash Display list, PPAPI lags behind performance and doesn't even use hardware acceleration for Stage3D compared to NPAPI, which fully utilizes it.

My question is: I already know that there is a way to determine if PPAPI is being used, but can the NPAPI version of Flash be enforced on Chrome users in any way through headers or Javascript?

My current solution is to simply show a little guide on manually disabling Flash PPAPI whenever this version of the plugin is detected, but it would be much more convenient if I could force the NPAPI plugin to be forced to use in the background.

Is it possible?

Answer 1

There is no way to do this. If you find it, it will be a security problem and will be fixed, because if an attacker can force the user to switch from an isolated PPAPI plugin to an unlimited NPAPI plugin, then all the security benefits of having an isolated plugin will be lost.

(And I hope your tutorial tells users that, according to your instructions, their vulnerability to attacks from malicious websites increases so that they make an informed decision.)