![]() ![]() ![]() Click Remove from Chrome and you can continue viewing PDFs and using Adobe Reader normally. You don’t even need to enable the extension to use Adobe Reader normally. Automatically installed plugins, even if those plugins are not enabled, would be just the kind of unwanted behavior that generates skepticism around security fixes. Google Chrome has an integrated PDF reader, and the Adobe Acrobat Reader PDF-reading plugin is separate from the extension. But the decision to install the extension apparently unprompted, as part of a security update, has provoked plenty of complaint from security-minded users. The general feeling is that security fixes are too important to be made intrusive, and that users should never be wary of installing a security fix for fear of that fix including unwanted features that are coming along for the ride. VIEW, DOWNLOAD, PRINT, and STORE PDFs Get the best PDF viewing experience with the Acrobat PDF reader. Regardless of whether users enable the extension or not, the security fixes are applied correctly. Install the Acrobat extension for Chrome. Given how long it has been available, it's likely that the extension itself is harmless enough and serves its official purpose. With latest Reader update, Adobe is automatically prompting users to install a Chrome extension which includes telemetry. Adobe states that this information is anonymous and does not include URL data. This tracking appears to be on by default, though it can be disabled through the extension's options page. On Windows, it is still possible to change the Chrome default PDF viewing behavior by configuring plugins (chrome://plugins). Here's a blog post that describes their decision - Chromium Blog: The Final Countdown for NPAPI. The extension also collects basic information and sends this to Adobe. The Chromium team has decided to remove support for NPAPI plugins like Adobe Reader. The plugin seeks permission to do three things "read and change all data on the websites you visit," "manage your downloads," and "communicate with cooperating native applications." The level of access required appears to be consistent with the plugin's stated purpose: as it can make a PDF of any page, it needs to have access to any page, and Chrome does not distinguish between extensions that read from pages and those that modify them. The new, more aggressive distribution is new, however. The extension has existed for some years. This is occasionally useful for using PDF features that the browser-based support doesn't offer. The extension does a couple of things it provides a quick way to convert a Web page into a PDF if you have a full, paid version of Acrobat, and it lets you choose to open PDFs in Adobe Reader rather than using Chrome's built-in PDF support. Select Portable Document Format (PDF) from the Content Type Column. After updating their systems, they found that Chrome was prompting them to enable an extension from Adobe. Adobe rolled out a set of patches for Acrobat, Adobe Reader, and Flash on Patch Tuesday this week, and the update had an unwelcome surprise in store for Chrome users. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |