LTV standard has requirements to add verification information for signature
embedded timestamp and OCSP responses.
Are there plans to add support for it to LtvVerification class?
If not, would you consider changing field visibility to protected for this
entry:
private Map<PdfName,ValidationData> validated = new
HashMap<PdfName,ValidationData>();
to enable adding such or similar functionality w/o completely rewriting
LtvVerificationclass? Or does it break some common iText policy rules?
When i read iText code i notice that it is extremely hard (or impossible) to
extend iText classes. I'm not sure if it is done on purpose or it just happens.
:)
From Pades-LTV standard:
NOTE 1: For a document signature the bytes that are hashed are those of the
signature's DER-encoded PKCS#7 (and
its derivatives) binary data object (base-16 decoded byte string in the
Contents entry in the signature
dictionary). For the signatures of the CRL and OCSP response, it is the
respective signature object
represented as a BER-encoded OCTET STRING encoded with primitive encoding. For
a Time-stamp's
signature it is the bytes of the Time-stamp itself since the Time-stamp token
is a signed data object.
--
Erik
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
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
