https://issues.apache.org/ooo/show_bug.cgi?id=121782
--- Comment #7 from Ariel Constenla-Haile <[email protected]> --- The following document is also rather informative: http://www.adobe.com/devnet-docs/acrobatetk/tools/DigSig/Acrobat_DigitalSignatures_in_PDF.pdf See 6.3.13 Enabling features via document-based permissions "PDF enables a fully featured client with rich PDF interaction to grant document-specific permissions to less capable clients so that they can also use some of those features. Using this mechanism, a client that does not have digital signature capability may be granted that ability. When the permission is granted at the language level for a particular document, any associated signature related user interface elements would become enabled." "For example, an author using Acrobat can grant permissions to enable additional features in Adobe Reader, using public-key cryptography. It uses certificate authorities to issue public key certificates to document creators with which it has entered into a business relationship. Adobe Reader verifies that the rights-enabling signature uses a certificate from an Adobe-authorized certificate authority. Thus, an Adobe Reader user that opens a reader enabled document can sign, fill in form fields, and otherwise perform actions that would otherwise be prohibited." -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
