It is, although in this case it's more that a previous bug has been fixed.
The getInstance method should never have accepted the tagged object. Using
the getInstance() method with two parameters will work in both 1.47 and
earlier versions of BC though.
Regards,
David
--
View this message in con
getContent call in
envelopedData = recipientInfo.getContent(certificateKey,
certificateKeyProvider);
Should be:
getContent(new
JceKeyTransEnvelopedRecipient(certificateKey).setProvider(certificateKeyProvider));
I'd also suggest allowing people to specify a content provider, the original
BC app
Hi,
the short answer is to avoid classes in org.bouncycastle.ocsp and to only
use classes in org.bouncycastle.cert.ocsp
The slightly longer answer is both classes use the same underlying ASN.1
encoding. So if you call getEncoded on the old class, use it to create a
BasicOCSPResponse (in 1.47 get
Hi Paulo,
if the deprecated method is still been used in the latest svn version, let
me know the details and I'll help you get it sorted out.
Regards,
David
--
View this message in context:
http://itext-general.2136553.n4.nabble.com/iText-5-2-1-and-Bouncycastle-1-47-tp4544704p4556602.html
Sen
