Hi, did you get your answer to this? I just discovered 134 messages in the
folder I'd set up for receiving said messages...and promptly forgot to check
for same.
I just went through this exercise and have set up my configuration files and
bash script to generate certificates.
-TN (Tim)
Hi All,
In ssl3_write_bytes, if (len < tot) we are returning failure with
SSL_R_BAD_LENGTH error. In this place I hope we should set “tot” back to
“s->s3->wnum”. Otherwise when application calls back SSL_write with correct
buffer, it causes serious problem (“tot” is 0 and iLeft is not NULL). I
Also consider using the functions that the "openssl verify"
command uses (source file: apps/verify.c), perhaps from a
bulk process that can be run on each CPU node on your
compute cluster. With a little thought, these can be done
efficiently, with lots of reused (i.e. not repeated) actions,
such
Thank you, sir. I was attacking this from the standpoint of needing to generate
several thousand certificates for testing purposes and so unique certificates
went to unique files. I think I must have used -out by itself, though I believe
I tried the -outdir option at the end when I tried to
A lot depends on what you mean by "verify", too. TLS endpoints should perform
a large number of checks on certificates; some of them aren't relevant for your
purposes, and others might not be.
For example, a TLS client such as a browser will check whether the received
entity certificate
