Hi all.
I have been reading the code of openssl/apps/ts.c and there is no
possible for the TSA to sign using a private key stored in a
token/SmartCard/engine. I think this is interesting because it makes
possible to make a TSA compliant with RFC 3628 ("Requirements for
Time-Stamping Authorities").
Did you (re)try with a more recent snapshot? A fix to this area of the ENGINE
logic was made recently in response to bugzilla ticket 1668;
http://rt.openssl.org/Ticket/Display.html?id=1668
http://marc.info/?l=openssl-cvs&m=120942258326907&w=2
You indicate that you're using 0.9.8e which is a
I'm trying to solve a reproducible memory leak that manifests itself
with SSL + Apache2:
https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/224945
Valgrind, plus our own research, points to a possible memory leak in
crypto/comp/c_zlib.c in libssl0.9.8g.
We see:
struct zlib_state *
