The browser AdobeFlashPlayer plugin removes the sandbox (protection mode) feature and enhances stability.

When the AdobeFlashPlayer plug-in is updated to 11.3, the sandbox feature (protection mode) is added to enhance the security of the browser. However, adding this technology requires more resources, it also makes the running of AdobeFlashPlayer more unstable. The Sandbox feature has not been applied to AdobeFlashPlayer for a long time. Since it is unstable

The Adobe Flash Player Plug-in was updated to 11.3 and added the sandbox feature (protection mode) to enhance the security of the browser. However, the addition of this technology requires more resources, it also makes the running of Adobe Flash Player more unstable. The Sandbox feature has not been applied to Adobe Flash Player for a long time. Since it is unstable

The Adobe Flash Player Plug-in was updated to 11.3 and added the sandbox feature (protection mode) to enhance the security of the browser. However, the addition of this technology requires more resources, it also makes the running of Adobe Flash Player more unstable. The Sandbox feature has not been applied to Adobe Flash Player for a long time. Since it is unstable, we do not need to use it. This is why most people are still using version 10.3, can the new version remove the sandbox feature? The answer is yes. The following uses Firefox as an example.

 

Method 1: Modify the mms. cfg configuration file (applicable to various browsers)

To remove/disable the sandbox feature of Adobe Flash Player, you can modify the mms in the folder where the NPSWF32_11_8_800_94.dll file is located (the version number is different from the file name. cfg: Open it as a text document. Add "ProtectedMode = 0" to it and save it.

Mms. cfg is the configuration file of Adobe Flash player. this configuration file is used to close the sandbox. However, the plugin-container.exe process will not be seen on firefox. In this case, I do not recommend using the original cause of this kind of plug-in. My Understanding of the plugin-container.exe process is to separate the Adobe Flash Player Plug-in into a process, so that when the Adobe Flash Player Plug-in crashes, it will not affect the browser and will be closed through, not only does the sandbox feature be disabled, but the plug-in independent process function is also disabled. Once the flash plug-in crashes, Firefox will suffer. The ProtectedMode parameter does not seem to be a sandbox.

 

Method 2: directly modify the NPSWF32_XX_X_XXX_XX.dll file (patch only applies to Firefox)

Modify the dll file so that the sandbox is skipped when the plug-in is running and the sandbox is not started. I don't know how to manually modify the dll file. However, if you have made a patch, you can modify the dll file of any version. The method is very simple. The reason for this suggestion is that the plugin-container.exe process of firefoxwill not disappear, and the crash of the plug-in will not affect Firefox.

● General sandfree patch download: http://pan.baidu.com/share/link? Consumer id = 137800585 & uk = 2684733227

 

Directory where the NPSWF32_XX_X_XXX_XX.dll file is located

● The 32-bit system directory is in % WINDIR % \ System32 \ Macromed \ Flash

● The 64-bit system directory is in % WINDIR % \ SysWOW64 \ Macromed \ Flash

In addition, Firefox can enter about: plugins in the address bar to view the location of each plug-in.

 

9. Seven Tips:

After using the Adobe Flash Player Plug-in to sandbox, most people are more fluent in playing flash in Firefox, and the chance of crash is much lower, which means it is still useful. I don't think you need to worry about the security risks caused by removing the sandbox. The security software used by ordinary people provides sufficient protection, or the immature sandbox technology brings more hidden risks.

Original article address: the browser Adobe Flash Player Plug-in removes the sandbox (protection mode) feature to enhance stability. Thank you for sharing it with me.