Hi,
We have been used to CRC via MD5 hash algorithm for a file to be
transferred in socket we kepp below steps.
*At Client side:*
1.Md5 Init()
2.MD5 Update
MD5 Update
MD5 Update
MD5 Update
.
.
.
3.MD5 Final
4.Get Checksum *C1*
*At Server side:*
1.Md5 Init()
2.MD5 Update
M
Thanks Stephen,
That was my suspicion, but I couldn't be sure.
Gerald Collins
Senior Member Technical Staff, Programmer / Analyst
CSC
8 Executive Drive, Suite 300, Fairview Heights, IL 62208 North American
Public Sector | p: +1-618-632-9252 x410 | | gcoll...@csc.com |
www.csc.com
This is
On Wed, Jan 25, 2012, Gerald L Collins wrote:
> Hello all,
> I've been tasked to look at some security issues for our OpenSSL
> implementation. We are currently at FIPS 1.2.2 and openssl 0.9.8k. Most
> of the issues I was asked to look at were no issue for us, but the below
> item I'm less
On Tue, Jan 24, 2012, Kelvin Brown wrote:
> I had stunnel working on this machine but then I moved it to a remote server
> and got this error:
>
>
> 2012.01.24 17:03:04 LOG7[3236:2044]: Remote FD=348 initialized
> 2012.01.24 17:03:04 LOG3[3236:2044]: error queue: 14098077:
> error:14098077:SSL r
I had stunnel working on this machine but then I moved it to a remote server
and got this error:
2012.01.24 17:03:04 LOG7[3236:2044]: Remote FD=348 initialized
2012.01.24 17:03:04 LOG3[3236:2044]: error queue: 14098077:
error:14098077:SSL routines:SSL3_SEND_CLIENT_KEY_EXCHANGE:bad rsa encryp
General reminder: If you (mis)use the "Reply" button
in your e-mail program to start a new topic, many
recipients and automated e-mail archiving systems will
file your e-mail under the case/topic of the mail you
"replied" to.
This is because your e-mail program (correctly) includes
the unique me
Hello all,
I've been tasked to look at some security issues for our OpenSSL
implementation. We are currently at FIPS 1.2.2 and openssl 0.9.8k. Most
of the issues I was asked to look at were no issue for us, but the below
item I'm less certain about. Since we are FIPS does this have any chan
