Some are even saying that it means you absolutely cannot trust the software it installs. What is a little worrying is that Adobe thinks it is OK to push stuff out on its users in this way. This update addresses a cross-site scripting vulnerability rated important that could potentially lead to JavaScript execution in the browser. Google had a look under the bonnet and found that the code and a JavaScript code execution bug that put the then 30 million systems the extension was installed on at risk.Īdobe has rushed out a security update for the Adobe Acrobat extension for Chrome after Google growled at it. Chrome's security mechanism did stop it being enabled automatically and users were asked if they wanted to enable the Adobe Acrobat extension in Chrome, or remove it.īut the Chrome extension that Adobe pushed out to user systems was more insecure than Woody Allen on stage with an army of underwear models. Open Chrome and enable the Chrome extension (if you did not do so in step 2). Now install either Acrobat DC Classic or Acrobat XI. The move angered more than a few because the “feature" was not mentioned in the changelog, and you could not block it. Install Acrobat Reader DC, and then opt in for the Adobe Acrobat Chrome extension on the first launch.
#Acrobat reader chrome extension pdf#
Adobe Acrobat Reader or FoxIt PDF reader). The extension downloads the PDF file in your default downloads directory and then executes the external command to open the downloaded file with the default PDF viewer (e.g.
But it also phones home with telemetry data. To use the extension, right-click on a PDF link and select the 'Open in PDF viewer' item. Have downloaded Acrobat Reader DC from the Reader download page with opted in Chrome Extension and have Acrobat Pro (DC/Classic 2015/11.x). The extension allows users to turn web pages into PDF documents. Have Enabled the Chrome Extension in January 2017 release, and then applied the QFE2 patch without any parameters (default scenario).
0 kommentar(er)
