twain,

twain wrote:
> so iText excludes the new entry but Adobe Reader doesn't accept this.
> Right?

Right.

Actually I have not tested whether iText properly excludes your additional
exclusion range but Adobe Reader definitively does not accept signed ranges
with exclusions other than the signature container. (Of course with the
applicable document revision considered...)

twain wrote:
> Just a consideration.
> Unsigned attributes are "unsigned" :-).
> So if someone is skilled enough to remove some data from my "excluded" pdf
> portion, he will also
> succeeded to eliminate an unsigned attribute.

Obviously. But those unsigned attributes cannot be mis-used to make the
document appear different (at least that should not be possible). Unsigned
parts in the PDF on the other hand might be (unless an individual in-depth
analysis proves the contrary) and, thus, should not be approved of by PDF
signature verification tools.

Regards,   Michael

--
View this message in context: 
http://itext-general.2136553.n4.nabble.com/Problem-with-preClose-function-and-exclusion-hashmap-tp3903958p3904143.html
Sent from the iText - General mailing list archive at Nabble.com.

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
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

Reply via email to