Note When enabled, PDFs display in a restricted environment (a “sandbox”) which which prevents embedded or tag-along malicious content from tampering with your system. Isolating PDFs in this way reduces the risk of security breaches in areas outside the sandbox. Adobe strongly recommends that you use Acrobat in Protected View if you are concerned about security or frequently interact with PDFs on the Internet. Standalone product vs browser functionality Feature Standalone Browser Drag-drop PDFs to the reading or navigation pane No No Printing No No Advanced Printing No No Saving No No Pan and Zoom No No Loupe Tool No No Reading mode No Yes Full screen mode No No. Trusting PDFs As described in, there are several ways to assign trust so that PDFs are exempt from Protected View: • Users can trust documents on-the-fly when the PDF opens: When the Yellow Message Bar appears, choose Enable All Features. Driver Not Intended For This Platform Windows 7 there.
• Create a privileged location via the UI for the file, folder, or host. • Deploy or set privileged location via the registry via any method. • Choose Trust sites from my Win OS security zones. Jboss Eap 6.1.0 Installer Jar on this page. Trust is assigned when PV is set to Potentially Unsafe locations. When set to All Files, then OS trusted sites does allow PDFs to open outside of PV. Verifying PV is on While you can verify whether the application has Protected View enabled by viewing the Enhanced Security panel, it is also possible to verify the document you are currently viewing is subject to Protected View’s protections. When using the standalone application, verification should be obvious since a document that opens in Protected View displays the Yellow Message Bar.
To verify if the browser-based document you are viewing is opened in Protected View: • Open a PDF in a browser. • Right click on the document.
• Choose Document Properties >Advanced tab. When Protected Mode or View is invoked, the status will be Protected Mode: On. Unsupported configurations When Protected View cannot launch due to an unsupported configuration, a dialog alerts the user of the incompatibility and provides the user with the option to disable Protected View.
Unsupported configurations for Acrobat running in Protected View change across releases as the product evolves. For example, Protected Mode supports Citrix and Windows Terminal Services deployments with 10.1. For a list of unsupported configurations and workarounds, see.
Unsupported configuration dialog for 10.x Unsupported configuration dialog for 11.x. FAQs Design principles Some of the high-level design criteria for Protected View include the following: • PDFs in a browser are more functional than PDFs in a Reader’s sandbox: For PV in a browser, the UI provides access to all of the features provided by Reader as well as the features that are available for any rights enabled document when viewed in Reader. • As secure as sandboxed Reader: Acrobat leverages the same technology and implementation as Reader and is just as secure. • Transitioning out of PV should be simple: In PV, exiting the read-only mode is as simple as choosing Enable All Features. • Disabled features should not be hidden: If a feature is not enabled in the sandbox, the UI still displays the disabled feature in the menu as a greyed out item. • Trust can be assigned to documents so that they bypass PV restrictions: Because of its integration with enhanced security, users can specify files, folders, and hosts as privileged locations that are not subject to PV trust restrictions.