Jump to content

Search the Community

Showing results for tags 'flash'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 38 results

  1. Where do browsers stand on Flash's impending demise? It's been two years since Adobe announced it would finally kill off its Flash Player; browser makers plan to follow suit on their own timelines. Thinkstock Two years ago, Adobe announced it would finally kill and bury Flash Player, the plug-in that simultaneously launched a million websites and gave security professionals nightmares. The oft-abused technology, equally praised and scorned even when it was at the top of its game, will land in the digital landfill at the end of 2020, when the company said it "will stop updating and distributing the Flash Player." Browser makers quickly chimed in to tell their users how they would sunset Flash, setting up sometimes specific, sometimes vague, timetables for curtailing usage, figuring that going cold turkey would catch site owners unprepared, break the web and turn customers into angry peasants waving torches and pitchforks. Two years after those initial promises of cutting out Flash, where are the browsers? How about a status update? Chrome's this close to turning Flash off by default Starting with Chrome 76, which is the next version slated to ship, Google's browser will disable Flash by default, the state the browser will remain in until all support is yanked in late 2020. With Flash default disabled - Chrome 76 will appear July 30, or in six weeks - sites requiring the plug-in will show the "missing puzzle piece" symbol and the message "Adobe Flash Player is blocked." Users will not be able to run Flash - at all - without going into Settings. Only after re-enabling Flash - Settings->Advanced->Site Settings->Flash->Ask First - will Chrome users be able to run Flash and display Flash content, and then only after their explicit okay. Google is thinking about adding what it called an "infobar" to the top of Chrome with the debut of version 76. If the user manually switches Flash back on through Settings, the infobar will appear, warning that the plug-in won't be supported at all after December 2020. IDG/Gregg Keizer Starting with Chrome 76, users will have to dive into Settings to run Flash after seeing this message on a site. Firefox soon to limit Flash options At this point, Firefox continues to run Flash Player on a per-site basis when a user authorizes the action. And Firefox will remember the site that was authorized if the user checks the box marked "Remember this decision" in the pop-up that appears when giving Flash permission. In early September, Mozilla will take the next step in purging the plug-in. With Firefox 69, scheduled for release Sept. 3, the browser is losing the "Always Activate" option for Flash, meaning that every request to run it must be user approved. From this point forward, the only settings will be "Ask to Activate," the default, and "Never Activate." (Most Firefox users probably didn't know that there was an "Always Activate" setting that let them skip the authorization hassle. It's in Preferences (macOS) and Options (Windows): Extensions & Themes-Plugins->Shockwave Flash->Always Activate.) Still to come for Firefox: Mozilla plans to strip all Flash support from the browser in early 2020. The exception will be Firefox's Extended Support Release (ESR), designed for enterprise settings, which will continue to run the plug-in through 2020. On a related note, Mozilla pointed out that barely half - 50.8% - of all copies of Firefox now have Flash installed. IDG/Gregg Keizer September's Firefox 69 will eliminate the "Always Activate" shortcut, forcing users to approve Flash every time on every site. No exceptions. Edge in turmoil What to say about Microsoft's Edge? Microsoft had a fire-Flash plan two years ago. But then the Redmond, Wash. developer went and decided to bag its version of Edge and instead go full-Chromium, replacing its foundational technology with the same that drives Chrome. While Microsoft didn't necessarily tie itself to Google's Flash timetable when it adopted Chromium, the company is likely to copy the browser big dog. There's no reason not to: "full-Chromium" Edge won't make a difference, one way or the other, to websites still running Flash, not with its very small share. By the time Microsoft has Chromium Edge ready, Chrome will have long put version 76, and its Flash-disabled-by-default behind it. Edge will do the same, whether it launches this year or next. As for Internet Explorer (IE) and the old Edge, in 2017 Microsoft promised that somewhere around mid-to-late 2019, those browsers would default to a disabled Flash state. Users were going to have to manually re-enable Flash in the browsers' settings panels to view content. The change has yet to appear in either browser. (It was unclear when Microsoft would throw the disabled-Flash switch; there was no hint, for example, in the Edge development roadmap.)_ Because Microsoft only upgrades old-Edge when it issues a Windows 10 feature upgrade, the next opportunity for this will be the fall refresh, 1909 in the operating system's yymm notation. Microsoft has hinted that it will retain old-Edge even after full-Chromium Edge ships, so it will have to manage multiple browsers - IE, too, for Windows 10 users and laggards still running Windows 7 - through their Flash end times. IDG/Gregg Keizer The 'old-Edge,' the one powered by Microsoft's own EdgeHTML engine, still lets users run Flash with minimal hassle. But the upcoming 'full-Chromium' Edge will probably mimic Chrome when it debuts. Safari and the no-Flash zone Apple and Flash never much cared for each other. iOS has always been a no-Flash operating system and macOS, formerly OS X, has omitted the Adobe plug-in since 2010, when Cupertino first told users to fetch Flash themselves. (Meanwhile, Chrome, and later, Edge, came with Flash baked in. Chrome dropped that approach in 2016 with version 53. Since then, Flash has been background downloaded the first time the Chrome user calls on it to render content.) "Apple is working with Adobe, industry partners, and developers to complete this transition," a July 2017 post to the WebKit blog asserted. Since then, nothing. Even if a user installs Flash on macOS, Safari still treats it as off by default. And Safari still requires user approval on each site (although the user can tell that site to run Flash every time going forward). In other words, Apple's made no change - and has announced none that it will make - in how Safari deals with Flash. IDG/Gregg Keizer Safari's handling of Flash hasn't changed in the two years since Adobe announced the plug-in's 2020 demise. This is still what users see when they click on content. Source: Where do browsers stand on Flash's impending demise? (Computerworld - Gregg Keizer)
  2. Mozilla plans to disable Adobe Flash in Firefox 69 by default according to an updated bug listing on the organization's bug-tracking website. Adobe Flash Player is the last NPAPI plugin that Mozilla Firefox supports; support for other NPAPI plugins like Microsoft Silverlight or Java was removed in Firefox 52. Firefox users could switch to Firefox ESR to continue using NPAPI plugins at the time. Google dropped support for NPAPI plugins in 2015 in Chrome. Firefox continued to support Adobe Flash provided that users installed the software on supported devices, and even considered integrating a Flash replacement called Shumway in Firefox, and later on Pepper Flash, the Flash system that Google used. Google integrated Adobe Flash in the company's Chrome browser in 2010, and Microsoft did the same for its latest browsers. Mozilla, Google, and other browser makers announced that Flash was on its way out, and Adobe decided to retire Flash in 2020. Mozilla's Flash retiring timeline lists two Flash related events for 2019: Early 2019 -- a visible warning displayed to Firefox users about Flash usage. 2019 -- disable Adobe Flash by default in Firefox. Adobe Flash was a major technology for many years but its popularity decreased in recent years. New web standards emerged that replaced Flash functionality for the most part. While there are still sites out there that make use of Flash, Adobe Flash is playing less of an important role on today's Internet than the technology did ten years ago. Flash is problematic from a security and also a stability point of view. Mozilla plans to disable Adobe Flash in Firefox 69. The Firefox release schedule lists September 3, 2019 as the release date for the stable version. Mozilla will disable Flash in Nightly when the browser hits version 69, then in Beta, and finally in Stable. Disabling means that Flash cannot be used anymore by default unless activated again by the user. Firefox won't prompt users anymore to enable Flash when sites require it, but it will be possible to enable Flash in the browser. The next steps in the Flash deprecation happen in 2020 and 2021. Flash support is removed completely from all Firefox versions except for Firefox ESR in 2020. Firefox ESR will continue to support Flash until the end of 2020. When Adobe stops the release of security updates for Flash, all Firefox versions won't load the plugin anymore. Google and other browser makers plan to end Flash support at the same time. Google made Flash usage more annoying already in Chrome 69. Closing Words Adobe Flash won't be supported by major browsers anymore from 2020 onward. Smaller browsers or fork may continue to support Flash so that Flash content that is still available on the Internet remains accessible; the downside to this is that these Flash versions are no longer supported with security or stability updates. It is unclear if organizations like Archive.org will preserve Flash content, e.g. tens of thousand of Flash games and applications, and how they would go about it. Source: Firefox 69: Flash disabled by default (gHacks - Martin Brinkmann)
  3. The Flash Preservation project Flashpoint created a solution to play thousands of Flash games on Windows and Linux machines after Flash's retirement. Adobe Flash will be retired in 2020 and browser makers such as Google, Mozilla or Microsoft started to phase out Flash support already in the browsers they create. Think of Flash what you want but the technology was used to create a number of impressive games. Problem is, if no modern browser supports Flash, no one can play those games anymore unless they use browsers that still support it or find other ways to preserve the games and play them. Even if browsers still support Flash, Flash itself will not be updated anymore and any security vulnerability found will remain unpatched. It is possible that Flash content will be removed on many sites once Flash is gone for good; this would mean that many Flash games would be lost forever. The Flash Games preservation project The Flash Games preservation project is an attempt to preserve Flash games so that they remain available and playable. The project is huge; the current full distribution of Flashpoint has a size of 31 Gigabytes. You can download a smaller collection with a size of just 2.2 Gigabytes if you prefer. The main difference between the two is that Infinity is configured to download Flash games that you select from Archive.org. The upside to this is that you won't have to download more than 30 Gigabytes of Flash files directly before you can start playing games. The main downside is that it takes longer on first start to play games as they have to be downloaded first to the local system. Also, some games won't work with Infinity and are not displayed because of this. The project maintains a Game Master List that is updated regularly. The current full version comes with more than 4000 games including many classic games. The developer has more than 2 Terabyte of Flash dumps on Google Drive from sites such as Gamepilot, JayIsGames, Newsgrounds, Kongregate, Armorgames, or NotDoppler. Some Flash games can be saved to the local system and run from there without any issues provided that a browser or the standalone Adobe Flash projector is used for that. Others won't run because they rely on servers or have DRM baked into them which prevents local playback without modification. The project uses the interface of LaunchBox and Apache web server capabilities to provide access to Flash games on Windows. The launcher displays the list of games that are available, and users may click on any to look them up, and on play to start the game locally. The distribution takes care of DRM, sitelocked games, games that have server requirements, and games that require external files. The developer and volunteers test games, download required external components, and hack the games if required so that they will run on the local system. Flashpoint requires Windows 7 or newer versions of Windows. It does require the .NET Framework 4.7 and a Visual C++ redistributable. You find copies of those in the arcade folder after you have unpacked the package on the local system. Linux users may run Flashpoint as well. Instructions are found in the readme.txt file that is included in the distribution. How Flashpoint works Flashpoint changes the system proxy while it is running; this is required to get games to run that are locked, with DRM, or have dependencies that are not locally available. You can run the custom redirector or the Fiddler redirector. The main difference between the two is that Fiddler is more reliable but also more interfering with network traffic while Flashpoint is running. The developer suggests that no mission critical networking operations are run while Flashpoint is running. Note that this will do certain things to your network traffic while Flashpoint is open, and while we maintain that we do not use this proxy or your network traffic for any kind of nefarious purpose, and we do believe that network traffic should remain relatively normal while Flashpoint is open, we do recommend that you do not do any sort of 'mission critical' networking while you're running Flashpoint, and if you do use a system proxy on the computer you plan to use Flashpoint on, we recommend making a copy of your settings somewhere in case something goes wrong. The way things are set up can be cause for concern. If you are concerned, consider running Flashpoint in a virtual machine on the system or a spare PC if you have one. Games are listed with screenshots and information; very useful. A quick test of the Infinity edition was completely positive. I played several games, and while it took a while before downloads completed, playing them worked fine and without any issues. Closing Words With hundreds of thousands of Flash games around on the Internet, and 2 Terabyte of data sitting on the author's Google Drive account, it is clear that Flashpoint is a massive project that will take a long time before the majority of games have been included. The project offers an excellent option for gamers to play classic Flash games even after the technology has been put to rest finally. Now You: Do you play online games? Source
  4. Adobe Flash Player, Connect, and Dreamweaver are the focus of this month's patch cycle. Adobe has patched a set of critical vulnerabilities which can lead to remote code execution, information leaks, and file deletion. On Tuesday, the tech giant's security advisory noted that the vulnerabilities impact Adobe Flash Player, Adobe Connect, and Adobe Dreamweaver CC. Two vulnerabilities which relate to Flash, a use-after-free flaw (CVE-2018-4919) and type confusion bug (CVE-2018-4920), are critical vulnerabilities which impact Adobe Flash Player and earlier on the Windows, Macintosh, Linux and Chrome OS platforms. Adobe says that successful exploitation may lead to arbitrary code execution in the context of current users. "This patch remediates two critical vulnerabilities and should be prioritized for workstation-type devices," said Jimmy Graham, Qualys Director of Product Management. "There are currently no active attacks against these vulnerabilities." Adobe also addressed two vulnerabilities in Adobe Connect. The first security flaw, CVE-2018-4923, is an OS Command Injection bug which can lead to arbitrary file deletion. The second vulnerability, CVE-2018-4921, is an error which causes unrestricted SWF file uploads and may lead to information disclosure. The final bug, CVE-2018-4924, is a critical OS Command Injection flaw in Adobe Dreamweaver CC. If successfully exploited, attackers can execute arbitrary code. Adobe thanked Yuki Chen of Qihoo 360 Vulcan Team working alongside the Chromium Vulnerability Rewards Program and independent researchers Rgod and Ciaran McNally for reporting the issues. The company recommends that users update their software versions immediately to stay protected. In February, Adobe addressed a total of 41 vulnerabilities across Adobe Acrobat and Reader. In total, 17 of which were considered critical security flaws and could be exploited by attackers to perform the remote execution of code. Source
  5. // Supported Products // *** Use CTRL + F to locate the product you are finding fast. Adobe After Effects CC 2017 (64-Bit) Adobe Animate CC 2017 (64-Bit) Adobe Audition CC 2017 (64-Bit) Adobe Bridge CC 2017 (64-Bit) Adobe Character Animator CC (Beta) (64-Bit) Adobe Dreamweaver CC 2017 (64-Bit) Adobe Illustrator CC 2017 (64-Bit) Adobe InCopy CC 2017 (64-Bit) Adobe InDesign CC 2017 (64-Bit) Adobe Media Encoder CC 2017 (64-Bit) Adobe Muse CC 2017 (64-Bit) Adobe Photoshop CC 2017 (64-Bit) Adobe Prelude CC 2017 (64-Bit) Adobe Premiere Pro CC 2017 (64-Bit) Adobe Bridge CC 2017 (32-Bit) Adobe Dreamweaver CC 2017 (32-Bit) Adobe Illustrator CC 2017 (32 Bit) Adobe InCopy CC 2017 (32-bit) Adobe InDesign CC 2017 (32-bit) Adobe Photoshop CC 2017 (32-bit) Adobe After Effects CC 2015.3 (64-Bit) Adobe Animate CC 2015.2 (64-Bit) Adobe Audition CC 2015.2 (64-Bit) Adobe Illustrator CC 2015.3 (64-Bit) Adobe Media Encoder CC 2015.4 (64-Bit) Adobe Muse CC 2015.2 (64-Bit) Adobe Photoshop CC 2015.5 (64-Bit) Adobe Prelude CC 2015.4 (64-Bit) Adobe Premiere Pro CC 2015.3 (64-Bit) Adobe Illustrator CC 2015.3 (32 Bit) Adobe Photoshop CC 2015.5 (32-bit) Adobe After Effects CC 2015 (64-Bit) Adobe Audition CC 2015 (64-Bit) Adobe Bridge CC 2015 (64-Bit) Adobe Character Animator CC (Preview) (64-Bit) Adobe Dreamweaver CC 2015 (64-Bit) Adobe Edge Animate CC 2015 (64-Bit) Adobe Flash Professional CC 2015 (64-Bit) Adobe Illustrator CC 2015 (64-Bit) Adobe InCopy CC 2015 (64-Bit) Adobe InDesign CC 2015 (64-Bit) Adobe Media Encoder CC 2015 (64-Bit) Adobe Muse CC 2015 (64-Bit) Adobe Photoshop CC 2015 (64-Bit) Adobe Photoshop Lightroom CC 2015 (64-Bit) Adobe Prelude CC 2015 (64-Bit) Adobe Premiere Pro CC 2015 (64-Bit) Adobe SpeedGrade CC 2015 (64-Bit) Adobe Acrobat Pro DC 2015 (32-Bit) Adobe Bridge CC 2015 (32-Bit) Adobe Dreamweaver CC 2015 (32-Bit) Adobe Illustrator CC 2015 (32 Bit) Adobe InCopy CC 2015 (32-bit) Adobe InDesign CC 2015 (32-bit) Adobe Photoshop CC 2015 (32-bit) Adobe FrameMaker 2015 (32-bit) Adobe Presenter Video Express 11 (64-bit) Adobe Presenter 11 (32-bit) Adobe Presenter Video Express 11 (32-bit) Adobe Elements 15 Organizer (64-Bit) Adobe Photoshop Elements 15 (64-Bit) Adobe Premiere Elements 15 (64-Bit) Adobe Elements 14 Organizer (64-Bit) Adobe Photoshop Elements 14 (64-Bit) Adobe Premiere Elements 14 (64-Bit) Adobe Elements 14 Organizer (32-Bit) Adobe Photoshop Elements 14 (32-Bit) Adobe Premiere Elements 14 (32-Bit) Adobe After Effects CC 2014 (64-Bit) Adobe Audition CC 2014 (64-Bit) Adobe Dreamweaver CC 2014 (64-Bit) Adobe Flash CC 2014 (64-Bit) Adobe Illustrator CC 2014 (64-Bit) Adobe InCopy CC 2014 (64-Bit) Adobe InDesign CC 2014 (64-Bit) Adobe Media Encoder CC 2014 (64-Bit) Adobe Muse CC 2014 (64-Bit) Adobe Photoshop CC 2014 (64-Bit) Adobe Prelude CC 2014 (64-Bit) Adobe Premiere Pro CC 2014 (64-Bit) Adobe SpeedGrade CC 2014 (64-Bit) Adobe Dreamweaver CC 2014 (32-Bit) Adobe Edge Animate CC 2014 (32-Bit) Adobe Illustrator CC 2014 (32-Bit) Adobe InCopy CC 2014 (32-bit) Adobe InDesign CC 2014 (32-bit) Adobe Photoshop CC 2014 (32-bit) Adobe Elements 13 Organizer (64-Bit) Adobe Photoshop Elements 13 (64-Bit) Adobe Premiere Elements 13 (64-Bit) Adobe Elements 13 Organizer (32-Bit) Adobe Photoshop Elements 13 (32-Bit) Adobe Premiere Elements 13 (32-Bit) Adobe After Effects CC (64-Bit) Adobe Audition CC (64-Bit) Adobe Bridge CC (64-Bit) Adobe Flash Builder 4.7 (64-Bit) Adobe Flash Professional CC (64-Bit) Adobe Illustrator CC (64-Bit) Adobe InCopy CC (64-Bit) Adobe InDesign CC (64-Bit) Adobe Media Encoder CC (64-Bit) Adobe Photoshop CC Extended (64-Bit) Adobe Prelude CC (64-Bit) Adobe Premiere Pro CC (64-Bit) Adobe SpeedGrade CC (64-Bit) Adobe Acrobat XI Pro (32-Bit) Adobe Bridge CC (32-Bit) Adobe Dreamweaver CC (32-Bit) Adobe Edge Animate CC (32-Bit) Adobe Flash Builder 4.7 (32-Bit) Adobe Illustrator CC (32-Bit) Adobe InCopy CC (32-Bit) Adobe InDesign CC (32-Bit) Adobe Muse CC (32-Bit) Adobe Photoshop CC Extended (32-Bit) Adobe FrameMaker 12 (32-bit) Adobe Premiere Elements 12 (64-Bit) Adobe Elements 12 Organizer (32-Bit) Adobe Photoshop Elements 12 (32-Bit) Adobe Premiere Elements 12 (32-Bit) Adobe Photoshop Lightroom 5.x CC (64-Bit) Adobe Photoshop Lightroom 5.x (64-Bit) Adobe Photoshop Lightroom 5.x CC (32-Bit) Adobe Photoshop Lightroom 5.x (32-Bit) Adobe After Effects CS6 (64-Bit) Adobe Bridge CS6 (64-Bit) Adobe Encore CS6 (64-Bit) Adobe Illustrator CS6 (64-Bit) Adobe Media Encoder CS6 (64-Bit) Adobe Photoshop CS6 Extended (64-Bit) Adobe Premiere Pro CS6 (64-Bit) Adobe SpeedGrade CS6 (64-Bit) Adobe Acrobat X Pro (32-Bit) Adobe Audition CS6 (32-Bit) Adobe Bridge CS6 (32-Bit) Adobe Dreamweaver CS6 (32-Bit) Adobe Fireworks CS6 (32-Bit) Adobe Flash Builder 4.6 (32-Bit) Adobe Flash Professional CS6 (32-Bit) Adobe Illustrator CS6 (32-Bit) Adobe InDesign CS6 (32-Bit) Adobe Media Encoder CS6 (32-Bit) Adobe Photoshop CS6 Extended (32-Bit) Adobe Prelude CS6 (32-Bit) Adobe FrameMaker 11 (32-bit) Adobe Premiere Elements 11 (64-Bit) Adobe Elements 11 Organizer (32-Bit) Adobe Photoshop Elements 11 (32-Bit) Adobe Premiere Elements 11 (32-Bit) Adobe Photoshop Lightroom 4.x (64-Bit) Adobe Photoshop Lightroom 4.x (32-Bit) Adobe After Effects CS5.5 (64-Bit) Adobe Media Encoder CS5.5 (64-Bit) Adobe Photoshop CS5.1 Extended (64-Bit) Adobe Premiere Pro CS5.5 (64-Bit) Adobe Audition CS5.5 (32-Bit) Adobe Bridge CS5.1 (32-Bit) Adobe Contribute CS5.1 (32-Bit) Adobe Device Central CS5.5 (32-Bit) Adobe Dreamweaver CS5.5 (32-Bit) Adobe Encore CS5.1 (32-Bit) Adobe Fireworks CS5.1 (32-Bit) Adobe Flash Builder 4.5 (32-Bit) Adobe Flash Catalyst CS5.5 (32-Bit) Adobe Flash CS5.5 (32-Bit) Adobe Illustrator CS5.1 (32-Bit) Adobe InDesign CS5.5 (32-Bit) Adobe Media Encoder CS5.5 (32-Bit) Adobe Photoshop CS5.1 Extended (32-Bit) Adobe FrameMaker 10 (32-bit) Adobe Premiere Elements 10 (64-Bit) Adobe Elements 10 Organizer (32-Bit) Adobe Photoshop Elements 10 (32-Bit) Adobe Premiere Elements 10 (32-Bit) Adobe Photoshop Lightroom 3.x (64-Bit) Adobe Photoshop Lightroom 3.x (32-Bit) Adobe After Effects CS5 (64-Bit) Adobe Media Encoder CS5 (64-Bit) Adobe Photoshop CS5 Extended (64-Bit) Adobe Premiere Pro CS5 (64-Bit) Adobe Bridge CS5 (32-Bit) Adobe Contribute CS5 (32-Bit) Adobe Device Central CS5 (32-Bit) Adobe Dreamweaver CS5 (32-Bit) Adobe Encore CS5 (32-Bit) Adobe Fireworks CS5 (32-Bit) Adobe Flash Builder 4 (32-Bit) Adobe Flash Catalyst CS5 (32-Bit) Adobe Flash CS5 (32-Bit) Adobe Illustrator CS5 (32-Bit) Adobe InDesign CS5 (32-Bit) Adobe Media Encoder CS5 (32-Bit) Adobe Photoshop CS5 Extended (32-Bit) Adobe Soundbooth CS5 (32-Bit) Adobe FrameMaker 9 (32-bit) Adobe Elements 9 Organizer (32-Bit) Adobe Photoshop Elements 9 (32-Bit) Adobe Premiere Elements 9 (32-Bit) Adobe Photoshop CS4 Extended (64-Bit) Adobe Acrobat 9 (32-Bit) Adobe After Effects CS4 (32-Bit) Adobe Contribute CS4 (32-Bit) Adobe Dreamweaver CS4 (32-Bit) Adobe Encore CS4 (32-Bit) Adobe Fireworks CS4 (32-Bit) Adobe Flash CS4 (32-Bit) Adobe Illustrator CS4 (32-Bit) Adobe InDesign CS4 (32-Bit) Adobe Media Encoder CS4 (32-Bit) Adobe OnLocation CS4 (32-Bit) Adobe Photoshop CS4 Extended (32-Bit) Adobe Premiere Pro CS4 (32-Bit) Adobe Soundbooth CS4 (32-Bit) // Installation Notes // Download and Install Adobe product using the official trial installer Run Universal Adobe Patcher as administrator Select the required software name from the list according to your Adobe product installed (including the right version) Click ‘Patch’ (if you get an error message then you need to locate the installation manually, or just copy the patcher to the installation directory and then apply it again) All done, enjoy! *** For any other Adobe product you are trying to crack but not listed in the support list, just choose the “Try to patch another product with the amtlib file” instead (give a try). *** If you meet the previous installation/cracking problems of Adobe software, please uninstall and delete these folders manually: C:\Program Files (x86)\Common Files\Adobe\SLCache C:\ProgramData\Adobe\SLStore If the occasion should arise, you have to use the Adobe Creative Cloud Cleaner Tool to clean them completely. // Warning // The Universal Adobe Patcher v2.0 may be reported as Threat // Download URLs //
  6. Adobe announced today that it plans to retire Adobe Flash in December 2020 when it will stop updating and distributing Flash. The company suggests that developers switch from using Flash to modern web technologies such as HMTL5, WebGL or WebAssembly. Adobe will support Flash "on a number of major" operating systems and browsers that support Flash currently. This includes 32-bit and 64-bit versions of Windows XP to 10, Mac OS X 10.9 or later, and packages for Linux. As far as browsers are concerned, Internet Explorer, Edge, Firefox, Chrome and Opera are supported on Windows. On Mac OS X, the browsers are Safari, Firefox, Chrome and Opera, and on Linux, Firefox and Chrome are supported. The reason that Adobe gives for ending Flash support is that web technology has matured and support many of the capabilities and functionalities that plugins introduced to the browsing world. Mozilla, Microsoft, Google and Facebook have published announcements of their own highlighting the End of Life for Flash. Mozilla updated its plugin roadmap for Firefox and adjusted it based on Adobe's end of support announcement. 2018 Second Half -- Firefox users have to enable Flash on each session they want to use Flash. 2019 Early -- Firefox will display a visible warning to users if a site uses Flash. 2019 -- Flash is disabled by default. Users won't be prompted anymore to enable Flash, but Flash may still be activated on certain sites by users. 2020-- Flash support is removed from Firefox. Firefox ESR continues to support Flash until the end of 2020. 2021 -- Firefox won't load the Flash plugin anymore when Adobe stops shipping security updates for Flash in December 2020 Microsoft announced on the Microsoft Edge development blog how it plans to retire Adobe Flash in company products 2018 -- Microsoft Edge requires users to enable Flash for each session individually. Internet Explorer continues to allow Flash. 2019 mid to late -- Flash is disabled by default in Microsoft Edge and Internet Explorer. Users have options to re-enable Flash. 2020 end -- Adobe Flash is removed from Microsoft Edge and Internet Explorer. Flash cannot be run anymore. Google announced on the company blog that Flash will be retired in Google Chrome as well.The company did not publish a roadmap but stated that it will remove Flash completely from Google Chrome toward the end of 2020. https://www.ghacks.net/2017/07/25/adobe-retires-flash-in-december-2020/
  7. This morning, Adobe announced its roadmap to stop supporting Flash at the end of 2020. Working with Adobe and other browser vendors, Mozilla has prepared a roadmap for Flash support in Firefox, and guides for site authors to make their final transition away from Flash technology. By managing this transition carefully, announcing it years in advance, and providing options for transition, Mozilla will help make the web faster, safer, and better for everyone. To provide guidance for site authors and users that continue to rely on Flash, Mozilla has updated its published roadmap for Flash in Firefox. Starting next month, users will choose which websites are able to run the Flash plugin. Flash will be disabled by default for most users in 2019, and only users running the Firefox Extended Support Release (ESR) will be able to continue using Flash through the final end-of-life at the end of 2020. In order to preserve user security, once Flash is no longer supported by Adobe security patches, no version of Firefox will load the plugin. As part of improving Firefox performance and security this year, Firefox users will choose which sites may run the Flash plugin. This choice will give users the ability to keep using legacy sites that require Flash, while letting modern sites shine with blazingly fast HTML speed. This change was announced last year and will ship in Firefox next month. Firefox users will still have the opportunity to enable Flash on specific sites that require it. It is possible to test this behavior today by downloading Firefox beta and changing the Flash setting in the Firefox Add-ons manager. Because each browser implements this feature slightly differently, MDN Web Docs lists the differences in Flash activation among the major browsers as a guide for authors. The Spellstone game has already migrated from Flash to HTML. Over the years, Flash has helped bring the Web to greatness with innovations in media and animation, which ultimately have been added to the core web platform. The end of Flash offers an opportunity to bring legacy design and content in the Flash format into an new era using HTML and web technologies. If you are a site author currently using Flash to implement video, games, chat, file upload or clipboard access on your site, the web platform now has fast, secure, and reliable features which can do all of these tasks. Browser makers have prepared a guide to help website authors transition away from Flash to the open web. This transition guide, published through MDN Web Docs, provides documentation and links to open web APIs, libraries, and frameworks to help make updating to the web platform a great experience. HTML is being rapidly adopted for web games. Image provided courtesy of Kongregate. Game developers that formerly built games for Flash are quickly switching to HTML and seeing great results. Last week, Kongregate published data about the transition to HTML and the trends in game technologies used on their web gaming platform. Mozilla works closely with games publishers and developers to advance the state of games on the Web, and continues to develop technologies such as WebAssembly which allow developers to achieve near-native performance. For more information about building great web games, see MDN Web Docs. This year, Firefox will become the fastest it has ever been. Reducing Flash usage now is an important part of making the web and Firefox better together, and will support the end of Flash in 2019 and 2020. The security and privacy features users have come to expect, combined with a new interface and added functionality, will streamline and modernize the browser experience for Firefox users. Article source
  8. Mozilla plans to implement a change in Firefox 55 that restricts plugins -- read Adobe Flash -- to run on HTTP pr HTTPS only. Adobe Flash is the only NPAPI plugin that is still supported by release versions of the Firefox web browser. Previously supported plugins such as Silverlight or Java are no longer supported, and won't be picked up by the web browser anymore. Flash is the only plugin left standing in Firefox. It is also still available for Google Chrome, Chromium-based browsers, and Microsoft Edge, but the technology used to implement Flash is different in those web browsers. Adobe Flash causes stability and security issues regularly in browsers that support it. If you check the latest Firefox crash reports for instance, you will notice that many top crashes are plugin-related. Security is another hot topic, as Flash is targeted quite often thanks to new security issues coming to light on a regular basis. Mozilla's plan to run Flash only on HTTP or HTTPS sites blocks execution of Flash on any non-HTTP non-HTTPS protocol. This includes among others FTP and FILE. Flash content will be blocked completely in these instances. This means that users won't get a "click to play" option or something similar, but just resources blocked from being loaded and executed by the Firefox web browser. Mozilla provides an explanation for the decision on the Firefox Site Compatibility website: Firefox 55 and later will prevent Flash content from being loaded from file, ftp or any other URL schemes except http and https. This change aims to improve security, because a different same-origin policy is applied to the file protocol, and loading Flash content from other minor protocols is usually not well-tested. Mozilla is also looking into extending the block to data: URIs. The change should not affect too many Firefox users and developers, but it will surely impact some. Mozilla implemented a new preference in Firefox that allows users to bypass the new restriction: Type about:config in the browser's address bar and hit the Enter-key. Confirm that you will be careful if the warning prompt appears. Search for the preference plugins.http_https_only. Double-click on it. A value of True enables the blocking of Flash content on non-HTTP/HTTPS pages, while a value of False restores the previous handling of Flash so that it runs on any protocol. Mozilla suggests however that developers set up a local web server instead for Flash testing if that is the main use case. (via Sören) Article source
  9. The upcoming version of Firefox blocks dangerous flash content. The Plugins section in Add-ons Manger of Firefox browser, which on Nightly has got a new option for Flash Plugin –Block dangerous and intrusive Flash content‘ with a checkbox that can be controlled by about:config preference plugins.flashBlock.enabled. FYI, 32-bit Firefox version on Windows already offers preferences page for Flash Plugin which is to enable or disable Flash Player protected mode, with this addition, you can notice two checkboxes on 32-bit version of Firefox browser, but this is the only checkbox you’ll see for Flash on 64-bit Firefox. FYI, the new Flash allow/blocklist feature applies to either ‘Ask to Activate’ setting or ‘Always Activate’ setting. For this bug -‘ Implement new plugin option for Flash as a checkbox to toggle the allow/blocklist feature (plugins.flashBlock.enabled)‘ target milestone has been set to Firefox 55. Article source
  10. After announcing last week that February's patches would be delayed until March, Microsoft alerts large customers that security patches are due today--but details remain sketchy Credit: Thinkstock Microsoft sent an email to its largest customers on Monday, alerting them that Adobe Flash Player patches for Internet Explorer and Edge will be coming today. Apparently Microsoft's announcement last week that it would delay February patches until March 14 didn't tell the whole story. Yesterday's email says in part: Microsoft is planning to release security updates for Adobe Flash Player. These updates will be offered to the following operating systems: Windows 8.1, Windows Server 2012, Windows Server 2012 R2, Windows RT 8.1, Windows 10, and Windows Server 2016... No other security updates are scheduled for release until the next scheduled monthly update release on March 14, 2017. These Flash patches are important for those who still use Flash with IE or Edge. There must be three of you out there, somewhere. For those who don’t use Flash-- or who only use Flash from inside Chrome or Firefox or a different browser--the fixes aren’t important. This is a particularly odd situation. The bundled Windows 7 and 8.1 “patchocalypse” patching method has been amended, with Microsoft declaring last month that starting in February, IE patches won’t be included with the monthly Win7 and 8.1 security-only patch: Starting with February 2017, the Security Only update will not include updates for Internet Explorer, and the Internet Explorer update will again be available as a separate update for the operating systems listed above. Of course, we didn’t have a security-only patch in February. In fact, we didn’t have any security patches in February. With Internet Explorer patches being yanked out of the Win7 and 8.1 security-only patches, it’s hard to guess what form these new Win7 and 8.1 patches will take. Adding to the confusion: Microsoft needs to patch Windows Server 2012, which is still stuck on Internet Explorer 10. Perhaps we’ll see a return to the old KB patches for IE10 and 11? Will there be Security Bulletins tying all of this together? The Windows 10 situation is even more obtuse. We have two dangling Win10 hotfix patches – 14393.726 and 14393.729 – which, much to Microsoft’s credit, were released and fully documented but not rolled out the Win10 Automatic Update chute. Will the IE11 and Edge patches for the various versions of Win10 take the form of a cumulative update? And if so, will that cumulative update be issued as a hotfix or will it be pushed onto all Win10 PCs? Will the fix go to 1507 and 1511 systems, in addition to the latest version, 1607? Microsoft hasn’t released corresponding hotfixes for Win10 1507 and 1511. If this patch goes out to 1507 and 1511 PCs, will the analogous hotfixes be issued for those versions? It’s a tangled web Microsoft has woven. Its move to bunch together all patches on all versions of Windows -- and its subsequent backtracking to accommodate well-founded complaints -- increases the complexity enormously. Bunched patches may be part of a “cloud first” future, but they’re hell to install and manage. There’s one point that sticks in my craw: All of this was foreseeable. Adobe has always released its patches on Patch Tuesday, and Microsoft always has to roll those patches into IE11 and Edge. Didn’t somebody see this train wreck coming? Source: Surprise! Microsoft issues Flash patches for Internet Explorer, Edge (InfoWorld - Woody Leonhard) Flash patches for Internet Explorer and Edge due today (AskWoody forums)
  11. The Australian Signals Directorate's award-winning Top Four cyber threat mitigation strategy has become the Essential Eight. They're based on data, they're essential, and they'll upset vendors. When the Australian Signals Directorate (ASD) released its Top Four Strategies to Mitigate Targeted Cyber Intrusions in 2011, it was revolutionary, because it cut to the chase. Do these four things first, before anything else, and you'll repel 85 percent of targeted intrusions. On Monday, the ASD released the new improved version. It's now the Essential Eight, and the advice is just as blunt. "The eight mitigation strategies with an 'essential' effectiveness rating are so effective at mitigating targeted cyber intrusions and ransomware, that ASD considers them to be the cyber security baseline for all organisations," the ASD writes. "Any organisation that has been compromised despite properly implementing these mitigation strategies is encouraged to notify ASD." The Top Four was intended to defend against targeted intrusions, including those executed by advanced persistent threats such as foreign intelligence services. That list remains the same, although the order has changed. The Essential Eight expands the defences to cover "ransomware and external adversaries with destructive intent, malicious insiders, 'business email compromise', and industrial control systems". The Essential Eight is divided into two sections. The first two items in each section were part of the original Top Four. To prevent malware running: Implement application whitelisting, so only selected software applications can run. Make sure all applications are kept patched. Disable untrusted Microsoft Office macros, because they're increasingly being used to enable the download of malware. Harden users' applications by blocking web browser access to: Adobe Flash player, uninstalling it if possible; web advertisements; and untrusted Java code. Microsoft Office macros have been singled out to reflect the prevalence of malicious macros. The ASD has seen their advice "mitigate attempts to compromise Australian organisations by adversaries working for a foreign intelligence service," ASD writes. "The list of applications has been reordered since Flash, web browsers, and Microsoft Office are exploited more than Java and PDF viewers ... "Some organisations might choose to support selected websites that rely on ads for revenue by enabling just their ads and potentially risking compromise." To limit the extent of incidents and recover data: Restrict administrative privileges to people who truly need them for managing systems, installing legitimate software, and applying patches. Patch operating systems, and keep them patched. Use multi-factor authentication. Back up important data daily, and store it securely. "Multi-factor authentication is now rated 'essential' to reflect the prevalence of passphrase theft and the abuse of remote access for infiltration, data exfiltration, and persistence," the ASD writes. As with the Top Four, the Essential Eight is based on ASD's experience responding to cyber security incidents, performing vulnerability assessments, and penetration testing Australian government organisations. The ASD has also revised its full list of mitigation strategies, classifying them as essential but of lower priority, very good, good, and limited. The strategies of limited effectiveness include: signature-based anti-virus software; TLS encryption between email servers; network-based intrusion detection and prevention system using signatures and heuristics; and capturing network traffic to perform incident detection and analysis. The original Top Four won the US Cybersecurity Innovation Award in 2011. According to Alan Paller, founder and director of research of the SANS Institute, the genius was encouraging organisations to fix the Top Four before anything else. "It takes such guts to put white space in a list, to say: 'This is enough. This matters. Do it first.' That's what Australia did, and no one else had the guts to do that," Paller told a meeting of security professionals in Sydney in 2012. The Essential Eight is just as gutsy. Most of the ASD's top recommendations continue to focus on basic network hygiene, and most of that can be achieved by the IT department simply doing its job properly. But cybersecurity vendors want to sell fancy and expensive techniques, some of which do very little to improve security. The ASD's recommendation that every organisation install ad blockers will also be controversial, given that it declares as hostile a key part of online business models. But... Given all the warnings about cyber threats and cyber war, we do want a secure internet, don't we? Well this is how you do it. By Stilgherrian http://www.zdnet.com/article/block-adverts-delete-flash-kill-java-asd/
  12. For Firefox :: http://fpdownload.macromedia.com/get/flashplayer/current/licensing/win/install_flash_player_24_plugin.exe For Internet Explorer :: http://fpdownload.macromedia.com/pub/flashplayer/latest/help/install_flash_player_ax.exe For Opera and Google Chrome :: http://fpdownload.macromedia.com/pub/flashplayer/latest/help/install_flash_player_ppapi.exe
  13. The top 10 vulnerabilities this year were mostly Adobe Flash, followed by Internet Explorer, according to a Recorded Future study. Six of the top 10 vulnerabilities found in cyberattack exploit kits in 2016 were bugs in Adobe Flash Player – including one Flash flaw that was packaged with a whopping seven different exploit kits, new research found. Recorded Future studied the contents of 141 exploit kits from Nov. 16, 2015 to Nov. 15 of this year, and found that Flash for the second year running led as the application whose vulns were used most in exploit kits; Flash comprised 8 of the top 10 last year. "A large majority of exploit kits have Adobe Flash Player vulnerabilities, so at the end of the day, not a whole lot has changed" with Flash's prevalence in exploit kits since last year's study, says Scott Donnelly, director of technical solutions at Recorded Future. Interestingly, the Flash vulnerability found in the most exploit kits by Recorded Future's research, CVE-2015-7645 - which lives in seven exploit kits - was the first zero-day Flash flaw discovered in the wake of Adobe's efforts over the past year to better secure its software with code-structure updates and mitigation features. Adobe worked with Google's Project Zero team to add attack mitigation features to Flash last year. Meanwhile, Microsoft Internet Explorer, Silverlight, and Windows vulnerabilities also made the top 10 list, with IE's CVE-2016-0189 as the number one flaw found in exploit kits overall. "CVE-2016-0189's impact is tied to multiple version of IE it affects as well as its link to three active exploit kits including Sundown and RIG, which have helped fill the void left by the Angler Exploit Kit," according to Recorded Future's report published today, "New Kit, Same Player: Top 10 Vulnerabilities Used by Exploit Kits in 2016." Recorded Future also found that the exploit kits that have stepped up to fill the gap of the now-defunct Angler exploit are Sundown, RIG, and Neutrino. Flash-y The Flash CVE-2015-7645 flaw affects Windows, Mac, and Linux operating systems, which Recorded Future said makes it especially attractive and "versatile" for attackers. The flaw, which Trend Micro had dubbed a "method confusion" bug, was used by the Russian state hacking group known as Pawn Storm/APT 28/Fancy Bear. The attack group sent spear phishing emails to foreign affairs ministers in various nations and rigged the URLs with exploits that the flaw, which allows an attacker to wrest control of the victim's machine. Its dominance among exploit kits came as a bit of surprise to researchers since Adobe had been working on better securing its apps. "Theoretically, that was the more secure version" of Adobe software, Donnelly says. But the vuln is fairly simple to exploit, and isn't always patched, according to Recorded Future. "While the vulnerability was patched by Adobe fairly quickly, its ease of exploitation and the breadth of operating systems affected have kept it active. Unfortunately, slow enterprise patching and lack of knowledge by home users mean the vulnerability still manages to help kits infect machines," the report says. None of the vulnerabilities that made the top 10 in last year's report were found this year in exploit kits. "These were all new" vulnerabilities, Donnelly says. Another key finding of the report was that the new exploit kit on the block, Sundown, is making inroads. Sundown, which reuses other kits' exploits, appears to be the handiwork of less sophisticated authors, experts say. "It's not like Angler and Neutrino, which were written from scratch by sharp guys," says CW Walker, a Recorded Future researcher. "It's gaining a lot of popularity, but it doesn't require the same support as Tier 1, AAA-level exploit kits in the past." Checklist Recorded Future says the best bet is to patch the vulns it cites in the report, as well as get rid of any of these affected apps that aren't needed by the business. The security firm in its report also recommends: Enable "click to play" for Flash Take a look at running Google Chrome, which benefits from Google Project Zero's work and study of Flash flaws Deploy browser ad-blockers to protect from malvertisting attacks Run regular backups, especially for shared files Source: Adobe Flash Flaws Dominate Exploit Kits In 2016 (DARKReading)
  14. http://fpdownload.macromedia.com/pub/flashplayer/latest/help/install_flash_player.exe http://fpdownload.macromedia.com/pub/flashplayer/latest/help/install_flash_player_ax.exe http://fpdownload.macromedia.com/pub/flashplayer/latest/help/install_flash_player_ppapi.exe
  15. Google Chrome HTML5 Roll-Out Plan Google revealed yesterday how it plans to make the shift to prioritizing HTML5 over Flash in the company's Chrome browser. The company announced previously that it will deprioritize Flash content on the web in favor of HTML5 content. The decision left many questions unanswered: will Chrome block all Flash content eventually? What is the time frame for the change? What happens to sites that only support Flash but not HTML5? This article will answer all those questions and a couple more. Google Chrome HTML5 Roll-out plan The roll out runs from January 2017 to October 2017 if things go as planned. Chrome uses the site engagement metric to determine whether "activate Flash" prompts are displayed to the user on sites that don't support HTML5 fallbacks. Site engagement describes how often a site is accessed by a Chrome user. The value gets higher with visits, and starts at 0 for sites that have not been visited yet. Tip: You can display the site engagement values for all visited sites in Chrome by loading Google chrome://site-engagement in the address bar. Points can be edited for any site. This can be useful for testing purposes, but also to raise the score of a site above a certain threshold. Chrome will display a Flash prompt for any site visited in the browser that falls below a selected threshold for the given month. In January 2017, any site below 1% will throw a prompt to activate Flash. This goes up to a threshold of 32 in June 2017, and to 100 in October 2017. Only new sites will display prompts in the beginning, but this will change over the course of the year 2017 until all sites will prompt the user for activation. January 2017 is special, as only 1% of all stable users of Chrome will join the Flash deprioritizing group. Google plans to increase the value to 100% with the release of Chrome 56 Stable in February 2017. Testing Developers may test the functionality in Chrome Beta. To do so, load chrome://flags/#prefer-html-over-flash in the browser and set the flag to enabled. Restart the browser to complete the change. This enables the HTML5 over Flash functionality in the browser with a fixed site engagement rating of 30. Any site below that threshold will prompt to enable Flash, any site above it won't. Closing Words Flash will remain a part of Google Chrome for the foreseeable future but users will face more and more prompts when they want to run Flash in the browser. The change is of concern to website operators as well who use Flash exclusively or predominantly on their sites as part of Chrome's user base will probably exit the site instead of following the prompt to enable Flash. Mozilla plans to drop NPAPI plugin support in Firefox 53 which will be out April 18th, 2017 (Google did so in Chrome 45 already, but Flash is not NPAPI but PPAPI in Chrome so it did not affect the technology). Flash will likely be the only exception to the rule as plans are underway to whitelist Flash so that it remains available. Now You: Do you visit sites that rely on Flash? Source
  16. Chrome 55 Now Blocks Flash, Uses HTML5 by Default Chrome 55, released earlier this week, now blocks all Adobe Flash content by default, according to a plan set in motion by Google engineers earlier this year. Back in May, Google's staff announced that starting with Q4 2016, Chrome would use HTML5 by default, while Flash would be turned off. While some of the initial implementation details of the "HTML5 By Default" plan changed since May, Flash has been phased out in favor of HTML5 as the primary technology for playing multimedia content in Chrome. Users have to allow Flash to run on non-HTML5 websites Google's plan is to turn off Flash and use HTML5 for all sites. Where HTML5 isn't supported, Chrome will prompt users and ask them if they want to run Flash to view multimedia content. The user's option would be remembered for subsequent visits, but there's also an option in the browser's settings section, under Settings > Content Settings > Flash > Manage Exceptions, where users can add the websites they want to allow Flash to run by default. Back in May, to avoid over-prompting users, Google said it would whitelist some of the Internet's biggest web portals where HTML5 isn't yet supported, or where not all content could be played back via HTML5 just yet. The list included YouTube, Flash, VK, and others. This top 10 list has been dropped, in favor of a better system called Site Engagement (chrome://site-engagement) that gives scores to websites based on the number of visits and time spent on each site. The Site Engagement indicator takes a value from 1 to 100, and once it drops under 30, users will be prompted to enable Flash, regardless of the site's popularity and Alexa ranking. Flash, who's been accused of being a resource hog and a security threat, will continue to ship with Chrome for the time being. If you don't like Google's decision to go with HTML5 by default, there's an option in the chrome://flags section where you can revert to using Flash. Google has been preparing for a life without Flash for many years now. YouTube has dropped Flash support a long time ago, while starting with January 2, 2017, Google will stop accepting Flash ads in its AdWords program. Both Chrome and Firefox now block non-essential Flash content, such as analytics and user fingerprinting scripts. Google has been doing this since Chrome 53, and Mozilla since Firefox 48. Source
  17. Firefox 49: Two New System Add-ons To Fix Flash And Graphics Issues Mozilla has started to distribute two new system add-ons for Firefox 49.0 and Firefox 49.0.1 to address two issues affecting Adobe Flash Player and graphics issues. The organization is working on Firefox 49.0.2 currently, but made the decision to release two new patches for the current stable version of Firefox as system add-ons to address issues that users are affected by. System add-ons are like hotfixes. They can be pushed out to all Firefox users who have automatic updates enabled to fix issues of the browser. That's usually a lot faster than having to create a new build of Firefox. The two system add-ons address two issues in Firefox 49 and 50. Asynchronous Plugin Rendering and D3D9 Acceleration Fallback Asynchronous Plugin Rendering enables asynchronoous plugin rendering in Firefox 49. The patch is designed to improve the performance of Adobe's Flash Player in Firefox, and to reduce the likelihood of crashes. The patch flips the switch dom.ipc.plugins.asyncdrawing.enabled to true on Firefox 49 and Firefox 49.0.1. This fixes an issue that 64-bit users of Firefox experienced. Mozilla calls these issues "functional", and mentioned that it also caused issues with scrolling for e10s users and Flash content. Mozilla will integrate the change in Firefox 49.0.2 which will be out soon. If you don't want to wait for the system add-on to be pushed to your copy of Firefox, flip the preference manually instead to resolve the issues: Type about:config in the Firefox address bar. Confirm that you will be careful if the warning prompt spawns. Search for dom.ipc.plugins.asyncdrawing.enabled. If the preference's value is set to false, double-click it to set it to true instead. This enables asynchronous plugin rendering in Firefox. The D3D9 Acceleration Fallback system add-on on the other hand deactivates Direct3D9 fallback if hardware acceleration is enabled in Firefox. This should fix graphics artifacts issues that some Firefox users are experiencing currently. The patch will land in Firefox 49 and Firefox 50. Find out if the system add-ons are installed You can find out if the system add-ons are already installed on your version of Firefox. Simply load about:support in the Firefox address bar and scroll down to the extensions group on the page. There you find all user installed and Mozilla installed Firefox add-ons. If you find the two system add-ons mentioned above, then they are installed and enabled. If not, there is little that you can do but wait for them to become available on your system. (via Sören Hentzschel) Source
  18. Firefox :: http://fpdownload.adobe.com/get/flashplayer/pdc/ Internet Explorer :: http://fpdownload.adobe.com/get/flashplayer/pdc/ Chrome & Opera :: http://fpdownload.adobe.com/get/flashplayer/pdc/ Flash Uninstaller :: http://fpdownload.macromedia.com/get/flashplayer/current/support/uninstall_flash_player.exe
  19. Firefox 52 Nightly: Plugin Support (Except Flash) Dropped If you run Firefox Nightly, currently at version 52, you may have noticed that plugins that you may have used in the past are no longer supported in the browser. So-called NPAPI plugins such as Java, Silverlight or Flash are on their way out. While the time frame varies browser by browser, all major browser developers announced the end of NPAPI support. Mozilla did so about a year ago on October 8, 2015 stating that plugins were the source for performance, crash and security incidents. The organization published a schedule recently that details when support for NPAPI plugins end in Firefox. The first Firefox version to ship without support for NPAPI plugins by default -- except for Adobe Flash -- is Firefox 52. Mozilla plans to ship that version with an override that allows you to turn support back on in Firefox 52. This override is removed from Firefox 53 however, and the only Firefox version with support for NPAPI plugins onward is Firefox 52 ESR. Firefox 52: end of NPAPI The end of NPAPI in Firefox 52 affects all plugins except for Adobe Flash. Flash is still widely used, and the chance is high that this won't change in the coming six months. Note: You may still see content listed under plugins, namely Content Decryption Modules or Video Codecs. These don't use NPAPI and will continue to work just fine in Firefox. Eventually though, Flash NPAPI support will also be removed from Firefox. This may coincide with Mozilla bringing Pepper Flash, the same that is used by Google Chrome, to Firefox. First, lets take a look at the timeline of events: March 7, 2017 -- Firefox 52 and Firefox 52 ESR are released. All plugins but Flash are disabled by default. Mozilla Firefox users may flip a preference switch to enable support for non-Flash NPAPI plugins in Firefox 52. Firefox 52 ESR will support plugins throughout its lifecycle (until Firefox 60 ESR is released). Firefox users may flip the preference plugin.load_flash_only to false to re-enable support for other NPAPI plugins. April 18, 2017 -- The release of Firefox 53 marks the end of NPAPI plugin support in Firefox. The override preference is removed. Flash is the only plugin left standing. First half of 2018 (May) -- Firefox 60 ESR is released. So, Enterprise customers and users who rely on plugins may switch over to Firefox 52 ESR for the time being to extend support for another year. Starting today, new profiles that you create in Firefox 52 Nightly will block all plugins but Flash from being used by the browser. From tomorrow onward, this will also be the case for existing Firefox profiles. You can track the removal of NPAPI support on Bugzilla. (via Sören Hentzschel) Source Firefox 52: Skia Enabled By Default On Windows When Firefox detects your computer graphic card doesn’t support hardware acceleration, the browser turns it off by default. You can check whether Firefox browser using hardware acceleration or not by visiting ‘Graphics’ section in about:support page. Till now Mozilla has used its 2D graphics engine, Azure, which has multiple backends enabled for Windows such as Direct 2D, Direct2D 1.1, Skia and Cairo. The Firefox browser vendor has decided to use Google’s Skia as the default software rendering backend for content on Windows from Firefox 52 onwards when Direct2D is not in use. With this change, if you visit about:support page, you can notice the ‘Diagnostics’ section under ‘Graphics’ displays both AzureCanvasBackend and AzureContentBackend report skia has been used as backend. With Skia enabled, font rendering gets somewhat better when compared without it when HWA is off. Behind the scenes, Mozilla changes below the preferences values to Skia, Cairo. gfx.canvas.azure.backends = skia,cairo gfx.content.azure.backends = skia,cairo Check this bug link – Bug 1007702 – (skia-windows) Enable skia content on Windows by default when not using D2D,– for more details. Source Firefox 52 Devtools: New Responsive Design Mode The Responsive Design Mode available till now in Firefox browser has been redesigned and enabled by default in Firefox 52 Nightly. The new RDM looks awesome and even better when compared with Chrome’s, comes with redesigned UI, device selector and it has been completely rewritten using HTML, React and Redux and other technologies by Mozilla. Firefox 52 devtools: New Responsive Design Mode To see it in action, ensure e10s is enabled and you’re using latest version Nightly and press Ctrl+Shift+M to open or click on the Firefox menu, click Devtools and select Responsive Design Mode. Want to see how the old RDM looks? Change this preference in about:config “devtools.responsive.html.enabled’ to false. Restart the browser. To get new RDM back, change the above preference value to true again. Mozilla to add more features to RDM, including Network Throttling, Zoom to fit for working with large viewports and UI to change device pixelratio. Source
  20. Adobe Has Decided To Support Flash Player on Linux Again Flash — Ah-ahhh. Adobe has announced that it plans to start supporting Adobe Flash for Linux — 4 years after it abandoned Flash on Linux. Back in 2012 the company said it would not make newer versions of its NPAPI Flash player plugin available on Linux and would only provide security updates for Flash Player 11.2 until 2017. But, in a small announcement made on its blog last week, Adobe has done a u-turn on both decisions, and provided a beta build of Adobe Flash 23 for Linux. Wait, WHAT?! Yup, Adobe has announced that it is to resume support of the NPAPI Flash Player plugin on Linux. Furthermore, it will not stop providing security updates in 2017 as previously announced: “in the past, we communicated that NPAPI Linux releases would stop in 2017. This is no longer the case”, they write. A new beta of the NPAPI plugin has been made available to download. While it won’t work in apps that have deprecated or removed NPAPI plugins (like Google Chrome) it should play nice in Mozilla Firefox and other apps. Adobe says it plans to regularly update both the NPAPI and PPAPI versions of Flash Player for Linux. Wow! Go Adobe, Right?! Nah, not quite. See, while Adobe plans to keep these new builds up to date and in sync with major releases on Windows and Mac, it doesn’t plan to support or add any advanced features and capabilities, like DRM, GPU acceleration, Stage 3D, etc. to the NPAPI version on Linux. Those of you seeking that level of functionality are advised, say Adobe, to use the PPAPI version of Flash Player. Why has Adobe done this? Adobe says it is “… moving [the NPAPI Linux Flash player plugin] forward and in sync with the modern release branch” to “improve security and provide additional mitigation to the Linux community.” Which is a mature response — it’s never easy to (sort of) admit you were wrong! They go on to describe this change as “…primarily a security initiative” and say the “new NPAPI build represents a significant step forward in functionality, stability, and security.” I Think I Already Run New Flash on Linux? If you use Google Chrome, you do! Linux users have been able to use an up-to-date version of Flash (built as a PPAPI plugin) thanks to Google, who not only maintain it but ship it as part of Google Chrome and Chrome OS by default. Many Linux distributions, including Ubuntu, offer a “helper” package that downloads Chrome, extracts the PPAPI Flash plugin, and makes it available for other applications to use. Where Can I Download It? You can download binaries of the NPAPI Adobe Flash player beta from the Adobe Labs website. These are available as 32-bit and 64-bit binaries only (not an installer package) and are said to not work with Fedora (or Fedora-based distributions). <<< Download Adobe Flash Player Beta >>> For more on Adobe’s u-turn check out this post on the official Adobe Flash Player blog. Source Alternate - Main Source - Courtesy: Adobe Returns To Updating NPAPI/Linux Flash Player
  21. Ever since XP.. i have never installed Adobe Flash.. i've always used a portable browser... with portable flash.. But Windows 8 natively comes bundled with Adobe Flash! There are tools out there for pre-mastering Windows' images... But this tutorial will focus on already installed /Online installs.. which i just uninstalled IE.. and wanted Flash gone as well.. 1. Navigate here to get your flash package: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages 2. Start PowerShell. 3. enable unsigned PowerShell scripts: Set-ExecutionPolicy -ExecutionPolicy RemoteSigned 4. Now scroll below and verify "Adobe-Flash-For-Windows-Package~31bf3856ad364e35~amd64~~6.3.9600.16384" matches your registry key in Step 1. - if your package version is different.. edit all occurrence with your package version. 5. Now manually execute each command below.. 1 line at a time. $acl = get-acl -Path "hklm:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing"$inherit = [system.security.accesscontrol.InheritanceFlags]"ContainerInherit, ObjectInherit"$propagation = [system.security.accesscontrol.PropagationFlags]"None"$rule = new-object system.security.accesscontrol.registryaccessrule "Administrators","FullControl",$inherit,$propagation,"Allow"$acl.addaccessrule($rule)$acl | set-aclSet-ItemProperty -Path "hklm:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Adobe-Flash-For-Windows-Package~31bf3856ad364e35~amd64~~6.3.9600.16384" -Name Visibility -Value 1New-ItemProperty -Path "hklm:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Adobe-Flash-For-Windows-Package~31bf3856ad364e35~amd64~~6.3.9600.16384" -Name DefVis -PropertyType DWord -Value 2Remove-Item -Path "hklm:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Adobe-Flash-For-Windows-Package~31bf3856ad364e35~amd64~~6.3.9600.16384\Owners"dism.exe /Online /Remove-Package /PackageName:Adobe-Flash-For-Windows-Package~31bf3856ad364e35~amd64~~6.3.9600.16384If you followed the tutorial to a T.. you should see something similar to my output: Note: for extreme minimalists.. this procedure could be used to remove other packages.. dism.exe /Online /Remove-Package /packagename:Microsoft-Windows-Camera-Package~31bf3856ad364e35~x86~~6.3.9600.16384dism.exe /Online /Remove-Package /packagename:Microsoft-Windows-FileManager-Package~31bf3856ad364e35~x86~~6.3.9600.16384
  22. Flash is a dying technology in its plugin-form, and Google plans to push Flash a bit further to the graveyard by making two Flash-related changes in future versions of Chrome. The first change will block behind the scenes Flash content, which is usually used for page analytics and tracking. When Google made detect and run important plugin content the default plugin loading behavior Chrome back in 2015, it exempted elements smaller than 5x5 pixels, and elements larger than 400px in width or 300px in height from that. Back then you had to switch to "let me choose when to run plugin content" to block Flash entirely on the chrome://settings/content page. Basically, what it meant was that some Flash elements were still loaded like before. The change announced today on the official Chrome blog removes that exemption. Chrome Flash blocking Chrome will start to block these elements once the change goes live. This applies only to cross-origin plugin content, content that is loaded from third-party sites, and not the site the browser is connected to. Chrome displays an icon in its address bar to indicate that plugin content was found but is not running. You may interact with the icon to reload the page with plugin content enabled, or use it to add an exception to Chrome's plugin whitelist to have plugin content loaded automatically when the site is visited in the future. The change will go live in Chrome 53 according to Google. The second change will favor HTML5 over Flash by making it the default experience in Chrome. When Chrome notices that a site supports HTML5 and Flash, it will request the HTML5 content automatically. When a site supports only Flash for its content, Chrome will display a prompt to the user that allows for Flash content to be loaded on the site. This change will be integrated in Chrome 55 which will be out in December 2016 according to Google. Google is not the only company that pushes Flash out. Mozilla announced recently for instance that it will block Flash content used for fingerprinting in Firefox. Google's move marks another step in the slow process of removing Flash in the web browser. The main reason for this is that while Flash is in a downwards trend, it is still used on many Internet sites. Flash will continue to work in Google Chrome for the foreseeable future. The changes that Google plans to introduce later this year affect the default loading behavior only. Chrome users still have options to override most of it. Tip: if you rely on Flash content, consider using a secondary browser for that. Article source
  23. You’ve got your collection of Windows ISOs and maybe you’ve burned installation DVDs or flash drives for them. But why not make yourself a master installation drive that you can use to install any version of Windows? Setting up a bootable USB Drive that includes multiple ISOs is actually pretty easy, We’re going to do it using a clever little free tool named WinSetupFromUSB, so go ahead and download the latest version of that. You can even include some non-windows ISOs on the disk, like Linux distributions and antivirus rescue disks. For a complete list of what you can include on your USB drive, check out their supported sources page. There is one important note from that page worth calling out. The tool works with single Windows ISOs from Microsoft. If you have a dual ISO that includes both the 32-bit and 64-bit versions of Windows, you won’t be able to use it. But you can always download single ISOs (one for 32-bit and one for 64-bit) and stick them both on the USB if you need to. Next, make sure you have blank USB drive big enough to hold all the ISOs you want to install, along with a little extra space. A 16 GB drive should give you enough space for two or three versions of Windows. If you have a 32 GB drive, you should be able to fit all the versions of Windows you could want. If you want to include other ISOs as well, you might need a bigger drive. WinSetupFromUSB is a portable tool, so there’s no installation. Once you have it downloaded, double-click the archive to extract the files a new folder. If you’re running a 64-bit version of Windows, run the executable with “x64” in the name. If you’re running a 32-bit version of Windows, run the file without the “x64” in the name. If you already had your USB drive inserted when you launched the tool, it should be listed in the box at the top of the window. If you didn’t have it inserted already, go ahead and plug it in now and then click Refresh. Next, click the “Advanced Options” check box. Instead of working like a regular check box, clicking it opens an “Advanced Options” dialog box. In the Advanced Options dialog, select the “Custom menu names for Vista/7/8/10/Server Source” check box. This setting allows you to provide your own names for the folders in which the Windows ISOs are stored and the boot menu names you see when you start a computer using the USB drive. You can close the “Advanced options” dialog when you’re done. Now comes the somewhat tricky part. You’ll be adding Windows versions one at a time. The first time you add something to the USB drive (and only the first time), you’ll want to make sure that the “Auto format it with FBinst” check box is selected. This lets WinSetupFromUSB format the drive appropriately for booting. If you know you’ll be booting a computer in UEFI mode (or if you’re unsure), then select the “FAT32” option. Otherwise, you can use the “NTFS” option. Next, select your first Windows ISO. Select the check box next to the “Windows Vista / 7 / 8 / 10 /Server 2008/2012 based ISO” section and then click the browse button (“…”) to its right. Locate and open the ISO you want to add. If it’s a large ISO and you’re using the FAT32 file system, you may get a notification that the file is too large and will be split in two. That’s fine, so go ahead and click OK. Double-check that you have the correct USB drive selected at the top of the window and that the right ISO is shown in the box. Then, click “GO.” If you’re using a large USB drive, you may get a warning asking if you’re sure that’s the drive you want to use. Go ahead and click “Yes.” If the auto format option is enabled (and it should be for the first ISO you add to a disk), you’ll also get a warning letting you know that the drive will be formatted and anything on it will be erased. Click “Yes” to continue. WinSetupFromUSB will now format the drive and then pop up a window where you can enter a custom folder name for the ISO that’s between 1 and 7 characters. If you don’t type anything for 30 seconds, the default will be used automatically. A similar window will now open that lets you type a custom name that should appear in the boot menu. This time, the name can be between 5 and 35 characters, so you have a bit more room to be specific. And again, you have 30 seconds to type a new name before the default is used automatically. At this point, WinSetupFromUSB will begin creating folders, adding the ISO to your USB drive, and adding the options to the boot menu. This can take several minutes and you can gauge the progress in the window’s status bar. When WinSetupFromUSB is done, you’ll get a simple “Job done” confirmation window. Click “OK.” WinSetupFromUSB now returns you to the main window. You can exit the program or you can continue adding additional ISOs to your boot disk. You’ll add additional ISOs using the same process, but there are a couple of things to keep in mind as you do it: When you add additional ISOs to an existing boot disk, make sure the “Auto format it with FBinst” check box is not selected. It won’t be by default when you return to the window (or when you start the program again), but it doesn’t hurt to make sure. You only want to format the disk with the very first ISO you add. You’ll need to click “Advanced Options” and enable the “Custom menu names for Vista/7/8/10/Server Source” check box each time you add a new ISO. Make sure you don’t forget this step before clicking Go or you won’t be able to add a custom name for the ISO to your menu . But that’s it. Otherwise, just follow the same steps each time you want to add a new ISO to the boot disk. You don’t have to add them all in one session either. You can come back any time and add something new. When you’re done, you can boot up a computer using your USB drive (which you may be able to do even if your BIOS won’t let you) and be rewarded with a nice boot menu like this: While it doesn’t sport the most intuitive interface, WinSetupFromUSB is lightweight and works well. And once you get the hang of adding ISOs to the package, it’s a breeze to set yourself up with a powerful boot disk that will let you install whatever version of Windows you want, as well as a number of other bootable tools. Credit to
  24. That’s 10x cheaper than 3D NAND from the likes of Samsung, SanDisk, SK hynix and others. If you haven’t heard of BeSang Inc, it is the company that invented and licenses 3D monolithic chip technology to SK hynix. According to a report published by the EE Times, BeSang has become frustrated with SK hynix’s “slow implementation of its monolithic 3D technology,” and has thus started to open its doors to rival memory makers, and will now even contract-fab its latest architecture NAND memory chips for others. 2¢ per gigabyte Now here’s the eye catching part of this story: BeSang has announced (PDF) its 3D Super-NAND flash memory, which offers the lowest cost per bit in the NAND market by quite some margin. As you can see from the graphic reproduced below, BeSang claims this NAND provides a 10x cost advantage, with 10x less capital investment, and 10x more wafer throughput. Put into cost terms BeSang can facilitate 3D NAND production at about 2¢ per gigabyte, rather than the current industry norm of 20¢. Dr. Yohwan Koh, former SVP and head of NAND business at SK hynix, and currently advisor at BeSang Inc, explained how BeSang streamlines the 3D NAND manufacturing process: “Other 3D NAND has sequential manufacturing process to build stacked memory layers, staircase bit line contacts, and periphery logic. It takes usually more than 10 weeks to complete manufacturing process. However, 3D super‐NAND takes only 5 days to complete advanced 3D non‐volatile memory cells thanks to parallel manufacturing”. Samsung 48-layer 3D NAND (left), BeSang 3D Super-NAND (right). In the space that traditional 3-D NAND fits a single cell, BeSang claim to be able to fit up to 50 cells, thus its beats by 3X a 48-layer Sansung single cell with 150 cells for a five-layer BeSang 3-D NAND. Further explanatory quotes via EETimes reveal that BeSang’s new monolithic 3D Super-NAND fits 30 bits in the same area as one bit in competitor processes. BeSang’s design is simpler and more efficient, especially the way it implements staircase word-line architecture. BeSang’s new 3D Super-NAND isn’t some pie in the sky research project. It is licensing its technology now and also offering turnkey delivery of 3D Super-NAND. Commercial customers can order 15nm or 20nm 3D Super-NAND chips with a minimum order value of $30 million. Furthermore, BeSang promises single-chip 1-terabyte 3D Super-NAND modules will be developed within two years from now. SanDisk's 48-layer 3-D NAND costs more per bit than 2-D NAND according to ForewardInsights. The cell size of 3D NAND is about 10X bigger (31,000 square nanometers) than planar 2-D NAND due to the use of over 60 percent of its area for control logic (34 percent), a tungsten isolation slit (20 percent) and a word-line staircase (26 percent). BeSang claims its tiny normal-sized vias can pack millions of interconnects per 3-D chip layer resulting in a lower cost-per-bit than Samsung's 32-, 48- or 64-layer 3-D NAND. BeSang 3-D chips locate their interconnection, selection and read-write logic on the bottom and its vertically stacked NAND cells tightly packed on the top. View: Original Article Images and explanation of images from this.
  25. Etcher is a new cross-platform open source program to burn operating system images to SD cards and USB drives safely and securely. My Surface Pro 4 ships without optical drive, and so do quite a few modern laptops and desktop PCs. It seems that optical discs are on their way to a niche existence; but this may come with a couple of issues. For instance, it is no longer possible to burn an ISO image of Linux Mint, Windows, or other operating systems to disc to start the installation process. Since you cannot insert discs anymore, you need to rely on SD cards or USB Flash drives for that. Companies may provide you with tools to copy ISO images to removable drives. You may also use third-party tools like XBOOT or YUMI to burn ISO images to USB Flash drives or SD cards. Etcher Etcher is offered as a beta release for Windows, Linux and Mac devices currently. The download is quite large -- 81 Megabyte on Windows -- but the functionality that it provides may be worth it. Note: The program attempts to connect to Internet servers regularly. These appear to be maintained by resin.io, the company that created the project. It is unclear why those connections are made. Could be an automatic check for updates. The interface is streamlined for ease of use. The whole process consists of three steps that are outlined in the interface on start. It starts with the selection of an image. The application supports various image formats including iso, img, dsk as well as gz, bzz and xz. Etcher tries to identify the correct drive automatically after you have selected an ISO image. The program jumps to the third and final step -- flashing -- automatically in that case. You may change the drive, which is useful if more than one removable drive is connected to the PC, or if the automatic identification of the drive failed. Etcher displays progress information in percent, the current write speed, and the estimated time of completion. Validation The application validates the copying of data after the copy process to make sure everything copied correctly. This is an important step as it ensures that you won't run into corruption issues when running the operating system or installing it on a device. The complete process takes a bit longer because of the validation but it is worth it and should not take longer than a couple of minutes tops. You may disable validation in the settings if you don't require it. Also, you may display the reporting of errors, and that the drive is unmounted when the operating completes successfully. The final page displays whether the operation completed successfully. You find the CRC32 checksum on the page, and get options to flash the same image or a new image. Etcher Article source
  • Create New...