Inspiring

Question

Flash Projector Player 23.0.0.207 not able to access local media

Forum|Forum|9 years ago
November 14, 2016
4 replies
1573 views

The latest three critical update versions of the Flash Player Projector - designed to run games and flash built apps on a local computer prevents the projector from loading it's own start files or images on a local computer.

Preventing Flash Player's Internet version from accessing local files is a reasonable and useful feature and it's been like that for many years.

The Flash Projector customarily uses local swf files and images from local files to present the program. The update documentation says the Flash Projector is exempt from the restriction and it should be able to access local media - but it isn't.

Preventing local access in the Projector version prevents Projector run apps (like mine) from working.

Adobe's latest security updates has left thousands of Flash app developers without the ability to update security fixes. What does Adobe expect us to do: Toss out our Projector run apps? My Flash Projector programs took years to build and I am not able to simply dump them - I am sure there are a multitude of other app developers who also won't be willing to dump their apps.

Was this a mistake by a novice programmer?

Adobe senior programmers, PLEASE set the default in the Adobe Projector Player back to being able to access local files; t

This topic has been closed for replies.

R

rickyhcAuthor

Inspiring

I finally found the problem with the update for the standalone projector.

In the same folder I had a dll file from an earlier locking system to prevent piracy. It was not actually called by the flash program files but was just in the folder. As soon as I deleted that - it worked as it should.

So it wasn't a coding problem or a bug with the standalone update. The old dll file didn't cause a problem with the earlier updates. It started with version 23. I'll add a comment on the forum and on the bug report.

Thanks for getting back to me, it started me looking again to find the problem.

jeromiec83223024

Inspiring

I can definitely see one or more mitigations that we've done in recent history breaking that approach from a number of different angles. One of the vectors for loading malware on a target machine is to drop a malicious DLL adjacent to an executable, where it's named the same as something that the executable would load from its search path. Depending on what your anti-piracy approach was in the DLL itself, if you were doing something clever in memory, that is also likely to no longer work. Those are not changes that we're likely to walk back.

R

rickyhcAuthor

Inspiring

Thank you for responding Jerome

I sent you a PM re what files to include in a dropbox folder and I submitted a bug report Bug 4197686

jeromiec83223024

Inspiring

Hi Richard,

On further inspection, our local with filesystem tests actually pass with the standalone player. There's probably some additional nuance that we're not accounting for.

Would it be possible to get a reproducible example from you? We'd be happy to investigate further.

You're welcome to submit a bug over at http://bugbase.adobe.com/, or if it's easier to just PM me a dropbox link or something, that's fine too. Whatever is easiest.

Thanks!

jeromiec83223024

Inspiring

Thanks for the note. It's a reasonable request. I've opened an internal bug to get a conversation started.

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.