Критическая уязвимость в Adobe Flash Player, Adobe Reader, Adobe Acrobat
Вчера Adobe порадовала публикацией о критической уязвимости в Adobe Flash Player 10.0.45.2 и всех ранее выпущенных версиях, обнаруженной на практически всех используемых платформах (Windows, Macintosh, Linux и Solaris). Уязвимости подвержена и библиотека authplay.dll которая используется так же и Adobe Acrobat и Adobe Reader.
Эта уязвимость (CVE-2010-1297) может позволить злоумышленнику получить контроль над системой. Есть сообщения, что эта уязвимость в настоящее время уже используется.
Adobe рекомендует незамедлительно обновиться на Adobe Flash Player 10.1 release candidate!
У кого используется Adobe Reader или Acrobat ищем и удаляем C:\Program Files\Adobe\Reader 9.0\Reader\authplay.dll
via Хабрахабр.
Flash Player 10.1 Updates Released for Mac, Win, and Linux and Solaris
By Daniel T on May 20, 2010 8:42 AM
Adobe® Flash® Player 10.1 is the first runtime release of the Open Screen Project that enables uncompromised Web browsing of expressive applications, content and video across devices. With support for a broad range of mobile devices, including smartphones, netbooks, smartbooks and other Internet-connected devices, Flash Player 10.1 allows your content to reach your customers wherever they are.
Flash Player 10.1 updates include new release candidate build 5 for Mac, Win, and Linux and beta 2 for Solaris.
Learn how to optimize web content for mobile delivery.
via Flash Player 10.1 Updates Released for Mac, Win, and Linux and Solaris – Adobe Labs.
If you’ve installed the latest version of Google Chrome, and you are having a problem debugging your Flash in it, there’s a reason. As you may have heard, Chrome now comes pre-installed with the Flash player. For good reasons, this is not the debug version of the player. All well and good, you go over to Adobe.com and re-install the debug player of your choice and debug your latest project… still no debugging. Hmm… If you’re like me, you “solve” this by switching to Firefox for debugging. I finally found out what’s happening though.
It seem’s the built-in Flash player in Chrome will get used by default, despite whatever other version you might have installed. It’s always going to go back to its own original version. To change this, type the following in the URL field:
about:plugins
This will give you a list of plugins. Somewhere in there, you’ll see “Shockwave Flash” with the version, location, etc. Underneath that is a “Disable” link. Go ahead and click it. You’re not disabling Flash all together, just the built-in version. Now, when you hit a SWF on a web page, it’ll go to the latest system-wide version you installed, i.e. the debug player probably.
via Debugging Flash on New Google Chrome | BIT-101 Blog.
Thoughts on Flash
Apple has a long relationship with Adobe. In fact, we met Adobe’s founders when they were in their proverbial garage. Apple was their first big customer, adopting their Postscript language for our new Laserwriter printer. Apple invested in Adobe and owned around 20% of the company for many years. The two companies worked closely together to pioneer desktop publishing and there were many good times. Since that golden era, the companies have grown apart. Apple went through its near death experience, and Adobe was drawn to the corporate market with their Acrobat products. Today the two companies still work together to serve their joint creative customers – Mac users buy around half of Adobe’s Creative Suite products – but beyond that there are few joint interests.
I wanted to jot down some of our thoughts on Adobe’s Flash products so that customers and critics may better understand why we do not allow Flash on iPhones, iPods and iPads. Adobe has characterized our decision as being primarily business driven – they say we want to protect our App Store – but in reality it is based on technology issues. Adobe claims that we are a closed system, and that Flash is open, but in fact the opposite is true. Let me explain.
перевод
Continue reading ‘Стив Джобс: ”Вы уже достали со своим флешем!”’
