Forwarded to openssl-users for discussion.
Having a glance on your report it seems that you have created a
certificate request which is to be submitted to CA for signing.
Only the certificate signed by the CA is a X.509 object that
can be handled with the openssl x509 application. To display the
Donny Dinh wrote:
* ./openssl s_client -connect www.google.com:443 -state*
[..]
*6709:error:140943FC:SSL routines:SSL3_READ_BYTES:sslv3 alert bad record
mac:s3_pkt.c:1057:SSL alert number 20*
*6709:error:140790E5:SSL routines:SSL23_WRITE:ssl handshake
failure:s23_lib.c:188:*
If I force
Hi everybody,
when experimenting with OpenSSL v0.9.9 (since that version allows
choosing the digest algorithm when creating a PKCS#7 structure) I
encountered an odd behaviour: no matter what argument was specified for
the -md parameter, the resulting PKCS#7 structure had the SHA-1 OID
set in all
A quick update on this issue. After digging through some untouched
code, I discovered that the server was writing data directly to the
port instead of the SSL_SOCK_Stream. Problem solved. Thanks for all
of your help.
On 12/11/06, Marek Marcola [EMAIL PROTECTED] wrote:
Hello,
Hrm... ssldump
I managed to get the solaris build to work properly by changing the
compiler flags
i.e. using config rule debug-solaris-sparcv8-cc instead of
solaris-sparcv8-cc
Why exactly does it work now...? I'm not too sure, but I reckon its some
kind of timing issue
(considering that Michael Stroder
Because Solaris has a loop unroll optimization bug.
Apply all the latest patches to SunStudio 11 and it should work. Please
check back in to let us know.
It's a really high level bug - because it hit both sparc and x86 :)
Donny Dinh wrote:
I managed to get the solaris build to work properly
