On 23/11/2011 19:01, Birgit Haas wrote: > Dear iText-team, > > We have implemented an abstraction of JCE security provider related > code (ASN.1, DER-encoding, ocsp, timestamp) so that iText may also be > used with other JCE security providers than Bouncy Castle. With these > changes more flexibility and the usage of more crypto algorithms can > be achieved. We would welcome any information on how the code changes > shall be contributed to iText. > > Best regards and many thanks for your kind consideration,
Thank you for your effort enhancing iText. You can find the policy for code contributions here: http://itextpdf.com/terms-of-use/policy.php In short: if more than 20 lines are involved, we ask you to sign a Contributor License Agreement, and send it to Bruno. The code itself (either diffs against the most recent version in SVN or the complete Java files that were changed) can be sent to Bruno too. ------------------------------------------------------------------------------ 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. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ 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
