It's been known Adobe terminates flash support by end of 2020, however companies are interested what happens after 2020 - is it possible still to run Flash in major browsers, just without support? Asking to have plan B if companies won't finish migration by end of 2020, and what are possible workarounds?
Microsoft support told that it depends on Adobe, if they keep flash still available.
I was able to install flash for firefox.
However, I wish to test configuring the below parameters in mms.cfg file
I tried setting the parameters as above in the file (utf-8) but whitelisting doesnt seem to work properly.
I set specific website in below parameter, but flash is still allowing the content from other website.
website to be allowed: http://abc.com/
Flash still loaded content from http://xyz.com/
Please advise how to configure the whitelisting in flash properly?
I also wish to whitelist two websites, how can I add them to above parameter?
Thanks in advance
I'm able to whitelist a pair of flash player and Firefox.
However, I'm unable to whitelist another webpage which has port numbers.
Can anyone advise how can I make, flash player read wildcard for portnumber in whitelist url pattern?
Landing page has port number 7000 while content resides on other ports.
Is it possible to use wildcard for port numbers or to allow all ports in this domain/subdomain automatically?
Can you share your mms.cfg file?
I'm trying to change the date of my PC, load my Flex application with Firefox ESR and flash player 32 but it always block my application.
I'm trying this configuration in mms.cfg:
Thanks in advance,
It looks like it was a problem with my flash player version, I updated to version 22.214.171.1243 and tested again, it works on Windows 10, Firefox ESR and Flash Player Debugger version 126.96.36.1993 with this mms.cfg:
Alexei5D13 & MauricioB82B,
Have you tried those settings with a non-local site, especially a secure site? I haven't been able to get around the 1/1/2021 End of Life animation. (I also have the 188.8.131.523 debug player for Firefox, and the same mms.cfg as MauricioB82B, other than the domain name.)
It looks like the 184.108.40.206 debug player (August 2019) does not include the 1/1/2021 bomb. I installed that and it works fine after the setting my clock to any 2021 date. I do not know what is the latest version that does prevent use, but at least that one is fine.
Unfortunately, Adobe is not supplying any older versions of Flash Player. The decommissioned the pages to retrieve older versions.
"Documented in troubleshooting" Sorry for my ignorance, but where is the "troubleshooting" you are referring to?
I have used basically the identical mms.cfg file as Mecurio, but it still does not work. When it gets to the point in the application where it asks to get to Flash, I get taken to a screen with a logo and when you click on the logo you get taken to a screen with all the Adobe informatoon about Flash being EOL.
Oh, and interestingly enough, in my testing the "time bomb" goes off on 1/12/2021, not 1/1/2021 as I would have expected.
WHY Adobe cannot just give SPECIFIC examples of mms.cfg files that have been tested as opposed to just links to the Admin manual, is beyond me! They can add disclaimers to the effect that just because it worked for them, it may not work in a given users environment as well as disclaimers that they strongly recommend against this in any event. The people at Adobe should be ashamed how disrectful of the customer base they are being. They should have just put the source code out into the public domain!
I do understand your situation and share the same worries about it. If you have found any solution to this issue, I would appreciate to keep in contact with you and learn about them.
we are working on backup solution from 2021 to run chrome browser using app-V, where we disable chrome browser from updates. that's a temporary solution until we finalize our project.
I'm using the 220.127.116.114 version of the Flash player. Will that be useable next year even though Flash won't be supported anymore? In fact, is there a way to protect your own Flash player?
For others still looking to port Flex apps to html5, Apache Royale (https://royale.apache.org/) can provide another reasonable option. It still requires some effort (mostly in UI parts) when porting apps, but because Apache Royale supports actionscript 3 and mxml for targeting the browser, large parts of the original business logic code can usually be retained as-is. Apache Royale is open source (and the community is receptive to new people getting involved if you want to join in with the effort). Although there are some Flex 'emulation' component sets which may make porting from the original mxml easier, there are also other modern approaches such as Jewel: https://royale.apache.org/tourdejewel/.
what about NetConnection, NetStream and Stage3D classes?
Hi Robert, it's fair to say that most of the effort for Royale has been focused on the Flex classes, without trying to emulate everything at the flash.* package level. But, to be clear, there are already many commonly used flash.* classes that are emulated in some way. For example AMF3 serialization/deserialization is currently supported (via AMFBinaryData instead of ByteArray) and so regular remoting service calls (http) are currently supported via some basic 'NetConnection' emulation. But rtmp data streaming connections are not currently emulated. I think this could very likely be addressed for rtmp data-only streaming if there was enough demand and shared effort (I believe something similar has been done in the past via websockets in other projects, such as Mozilla Shumway). I am part of the Royale community and I have had conversations with others about this, but we did not get started on it yet. For rtmp video and audio streaming I am far less confident about those, but I also have not looked into it in any way. I think that among the issues there would probably be related to the codecs which the flash player has that may not be available.
Thanks Greg for the details, as Royale is in JS do you think in the near Future it will be compiled into WebAssembly with emscripten or else?
There has certainly been interest expressed in making WebAssembly supported as another Royale target, I had understood that was direct as opposed to generating output for emscripten. And there is generally a longer term interest in adding other targets, such as native targets for mobile, beyond the currently supported Node, browsers (and mobile or desktop apps via Cordova or Electron). But I am not aware of others working on any of that at this point, so I would not describe any of this as 'near future'. If you have relevant knowledge and interest in achieving WebAssembly targeting, then I can only suggest you sign up to the dev mailing list and get involved. Progress is really only limited by the availability and willingness of people to contribute. One of the benefits of working on an open source project is that we can all help create the ecosystem that makes sense for all of us, to fill some of the gaps left behind after flash player demise, in this case.
just to complement to what Greg Dove said and for people insterested in Apache Royale. A part from Tour De Jewel I can give you some links that could show what can be done with this new technology:
Some instersting links about Royale:
We''ll be doing some talks in few days in at ApacheCon Home: https://twitter.com/carlosrovira/status/1296017685789257729
The talk about "Starting from a blank file" will cover the TodoMVC examples.
If you're interested join us in our user and/or dev mailing lists here: https://royale.apache.org/mailing-lists/
Does anyone know what the Harman solution will cost for 100/1000/10000/100000 seats?
Are you sure there is actually a way to use flash after 2020? I do not believe that this is actually true.
Your partner Harman is charging an exhorbitant amount for their solutions. Small companies with a short term need could never justify the costs.
1) The Harman option is going to be prohibitively expense for many organization! I wonder it Adobe has a stake in them or otherwise receives "kickbacks" from Harman!
2) Users everywhere should boycott Adobe and stop using their products! Did they give 3 years notice? Well yes they did. Did anyone know there was going to be a worldwide pandemic that require IT resources to be focuse elsewhere? No one knew! But does Adobe care? Clearly the answer is NO. They could delay the EOL of Flash in deference to the COVID-19 pandemic and the associated ramifications, but they chose not to. SHAME ON ADOBE. SHAME!
But what will you do once your Flash Player distribution license runs out? I doubt they will be renewed after EOL, so all corporate rights to install will lapse.