how I can change it
No comment
Le 03/09/2014 18:13, md intekhab shaukat a écrit :
Reminder.
-- Forwarded message --
From: *md intekhab shaukat* shaukat.mdintek...@gmail.com
mailto:shaukat.mdintek...@gmail.com
Date: Thu, Aug 28, 2014 at 3:56 PM
Subject: Client Key
Well, I would be happy to assist you in keeping NO_FP_API alive and supply you
with adequate diffs and resources. However, I would first need to know what
exactly is not working for you and where and on which platform exactly it
breaks for you because actually it is *working* for us.
Please
I'm trying to receive the response of a signer of time and am getting the
erro:
root@digic:/opt/CaIC/tsa/tsa-0.2# openssl ts -verify -queryfile
teste.txt.tsq -in teste.txt.tsr -CAfile /opt/CaIC/tsa/tsa.crt
Verification: FAILED
3074406076:error:2107C080:PKCS7 routines:PKCS7_get0_signers:signer
Can I use ASN1_INTEGER_free directly to free the memory allocated by
ASN1_INTEGER_dup ?
Thanks Regards,
Sanju
So please tell me *exactly* what you require to get the NO_FP_API support
into a state that it is still acceptable for you. And please tell how and on
which
platform I can reproduce the problems you are seeing.
Any Linux platform. ./config no-stdio -DNO_FP_API should build clean.
--
Can I use ASN1_INTEGER_free directly to free the memory allocated by
ASN1_INTEGER_dup ?
Yes, absolutely.
--
Principal Security Engineer
Akamai Technologies, Cambridge MA
IM: rs...@jabber.me Twitter: RichSalz
:��IϮ��r�m
(Z+�K �+1���x ��h[�z�(Z+� ��f�y��
On Wed, Sep 03, 2014, Andy Schmidt wrote:
Great, thank you!
The problem is that the API call sequence generates different S/MIME
and/or PKCS7 output between 1.0.1h and 1.0.1i. The attached files are
generated from the same API call sequence, JohnHancock.smime.h with
1.0.1h and
