JS communication fails after version 23 update

Question

Im using flash player for one of my chrome application. It was working fine before flash version 23 update. Inside application we have a communication between JS and flash. For allowing that communication we are selecting the option "allways allow" option in "Global Security Settings panel".

But now the communication is not working after the new update. Is there any new security things to do for this version?

jeromiec83223024 · Answer

Without a lot of detail to go on, it sounds like you're running into this:

( From the release notes, here: Release Notes Flash Player 23 AIR 23 )

Disabling local-with-filesystem access in Flash Player by default

Beginning with Flash Player 23, local-with-network permissions will now be applied to all local SWF content, regardless of the preference chosen at compile time.

Background:
When playing Flash (SWF) content from local filesystem, developers have historically been able to configure content to exclusively read from the filesystem, or communicate to the network. When this functionality was introduced over a decade ago, it enabled an interesting array of use-cases ranging from simple games to interactive kiosks. In context of modern web security, we believe that it is time to retire local filesystem functionality in the browser plugin. At the same time, Adobe AIR has been established as a robust, mature solution for delivering ActionScript-based content as a standalone application.

Vast majority of Flash Player users and content will be unaffected by this change. This change only impacts Flash content played from the local filesystem, using the browser. Flash content hosted on the internet and local webservers, as well as the Standalone Flash Player remains unaffected.If you are a user who requires this functionality, these files can be added to the list of Trusted Locations in Flash Player.

Workarounds for Legacy Content:
We highly recommend that you only circumvent these controls to enable content from sources that they trust.

For Individuals:
For Internet Explorer, Edge, Firefox, Opera and Safari:
On the affected system, go to: Control Panel > Flash Player > Advanced > Developer Tools > Trusted Location Settings
Click the icon and add relevant SWF(s) to the list

For Google Chrome (and similar PPAPI browsers):
Navigate to the settings manager page
Choose Edit Locations > Add Locations from the list.

For System Administrators:
The legacy behavior can be restored by applying the EnableInsecureLocalWithFileSystem=1 flag to mms.cfg.

The Chrome directions in our guidance above need some tuning.

These steps are better:

Go to the Global Security Settings panel

Select Edit Locations, then pick the Add Location menu item

Paste in the folder location to trust (don't use Browse)

Hit Confirm, and you're done

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.