Op 13/09/2012 19:37, Birgit Haas schreef: > Hi, > > This topic has already been discussed in the thread "Verify certified > (with transform method DocMDP) signatures" but I couldn't find a > satisfying answer. > Is there a best practice approach for checking whether the changes in > a certified PDF are permitted according to the P value in the DocMDP > transform parameters? Or is it necessary to somehow analyse the > incremental updates?
Yesterday, a new class was added to check Signature Permissions (not just DocMDP, but also FieldMDP: starting with PDF 2.0 you can also lock a document using Approval signatures): http://sourceforge.net/p/itext/code/5409/tree/trunk/itext/src/main/java/com/itextpdf/text/pdf/security/SignaturePermissions.java However, there is no 'convenience' method yet to check whether or not the permissions have been respected. It's on the long-term TODO list. It would require to compare the current revision with the previous one, checking what types of annotations were added (fields: yes/no; signatures: yes/no) and if there's also other content in the new revision. We don't have code that does this 'automatically' yet. ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ iText-questions mailing list iText-questions@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/itext-questions iText(R) is a registered trademark of 1T3XT BVBA. Many questions posted to this list can (and will) be answered with a reference to the iText book: http://www.itextpdf.com/book/ Please check the keywords list before you ask for examples: http://itextpdf.com/themes/keywords.php
