Adobe has released an update to Flash Player 9 today (9.0.124.0). This is the April 2008 security release that I blogged about earlier. This is primarily a security release to address certain issues and maintain the high confidence level that developers and end users have always had in Flash Player.
As I mentioned before, there are changes in this player that can impact existing content. For the full details, please read the updated article on the Adobe Developer Connection.
Content changes are frustrating and inconvenient. We’ve tried very hard to secure Flash Player in ways that reduce the impact to our customers. Whenever possible, we make choices that minimize the need to recompile or re-work an application. In all of the issues except “JavaScript:” placed in unusual network APIs there is an available solution that can be implemented outside the SWF, whether that is through a crossdomain.xml, an HTML parameter or an implicit call to a socket policy server.
Also, if you haven’t been to the Flash Player Download Center in a while, we just completed our re-design with this release. The new look is designed to make the experience of downloading Flash Player easier and more consistent with other Adobe technologies.
Pingback: JD on EP
Pingback: jonnymac blog » Flash Player 9.0.124 Released with Security Updates
“maintain the high confidence level”
Dude, you’ve released something like eight bug fixes to the Flash 9 player, and it’s still buggy. Whatever you’re doing for QA, it’s not working.
“Dude, you’ve released something like eight bug fixes to the Flash 9 player, and it’s still buggy. Whatever you’re doing for QA, it’s not working.”
You conveniently forget that Flash Player 8 had about 10 years to come to fruition. Flash Player 9 has been around ow for a little less than two years.
Great news Justin =) are the players available from the download center debug versions, and if not, is there a timeframe for their availability?
A little suggestion: how about testing the flash player installed when the user visits to see if its a debug version, and offer that up to users trying to upgrade their debug player?
Ultimately I’d like to see the version test and player download on the same page, and have easy access to the debug versions.
I’m running Vista and I was forced to download Flash Player 9 and it fails to download correctley, even the updated version! I have used the uninstaller from the Adobe site, cleaned Temp files, rebooted, downloaded the Flash player again and again and it still doesnt work!!!! (worked fine on flash Player 8 ). Anyone any suggestions?
The linux transparency issue hasn’t been fixed to date. Its been years. What are you waiting? Silverlight to run you off the market?
Pingback: flash addiction explained » Archives » Get Flash Player 9.0.124 to Test Against New Security Model
Neat… Though I was hoping this release would address the MAJOR performance bug that 9.0.115 introduced on the Linux builds.
Once again, Adobe has left Linux out in the rain.
Beau
So uhm,
why does 9.0.124 no longer play streamed h.264 from wowza/rubyizumi? Introduce a little TPM fun? What’s the deal?
124 fixes the bad linux fullscreen performance for me.
although i cant find any info about this from adobe.
The linux transparency issue hasn’t been fixed to date. Its been years
Arrgghhhh.. This 124 version frustrates the hell out of me, and the corresponding articles about the security changes as well. We simply do not understand the changes and what to do.
Our app. has stopped working for users that use ..124
We have domain http://www.softcapital.com and has a flex application running at http://www.softcapital.com/labs/demo/radarlite.html
This application talks to a socketserver at the same IP through port 20xxx
And after 124 version we get sandbox violation, and we do not know how to write this crossdomain file.
Has anyone any ideas?
Thanks in advance.
Cheers,
Lars
I’m looking for information – I’ve read all about the 124 security updates and they don’t seem to apply to my problem. The problem I’m experiencing is that none of our getUrl links work at all, period. We have no target specified and there is no javascript in the URL… it’s only 124, also. I verified this by testing on different machines and platforms – mac, pc, ie, ff, it’s all the same… movies with getUrl worked – update to 124 and now clicking no longer does anything. I can provide code samples if you like – I’ve been digging for a while and since this doesn’t apply to everyone else’s issues I thought I’d come here… any ideas?
So… javascript: calls with getURL are okay but ones with sendToURL are just too unusual? What about, y’know, urchinTracker calls failing all of a sudden, like the one that brought down a big site of mine today…? This (was) the recommended way of calling urchinTracker from within a Flash app. Easy patch with ExternalInterface, but not fun for thousands of users who just got the new flash player and had this site stop working.
I don’t read this blog often enough, I guess…
(I can hear the Vogons saying, “the plans have been in your local office in Alpha Centauri for the past 50 earth years…”)
Not sure if it’s just in .124, but did you know switch{} statements that are missing a break; in the case before default: make this version of the browser player enter a silent, unending loop, and fail to give any result from the switch, while the same is not true (i.e. the break; seems to be assumed) in the IDE?