Hi,
I can give some more details of my problem, which turns to be really weird.
It's still about client/server application that performs DSA authentication,
DH key-exchange and 3DES symmetric encryption. This application is deployed
on several platforms (at the moment Windows, Linux and Solaris).
And let me say it again, this time with a bit more information.
Windows runs on x86, which is little endian, Linux I assume you are also
running on little-endian (x86). Solaris I assume you are running on
UltraSPARC which if I remember correctly is big-endian. You are not
transferring your keys
Thanks a lot Joe,
I changed the code and now I transfer the DH public value (struct BIGNUM) in
the binary form and it works fine.
Most probably it was not endian-normalized (even though I put attention to
it, because it's a multi platform application).
I am too embarrassed to admit that I sent
"Bruker, Ohad" wrote:
Hello,
I can give some more details of my problem, which turns to be really weird.
It's still about client/server application that performs DSA authentication,
DH key-exchange and 3DES symmetric encryption. This application is deployed
on several platforms (at the
It's ok, we all make mistakes. I've had similar bugs, probably 3 dozen
times, with various amounts of time to find them.
Joe
- Original Message -
From: "Bruker, Ohad" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, February 16, 2001 2:09 PM
Subject: RE: symmetric
- Original Message -
From: "Bruker, Ohad" [EMAIL PROTECTED]
All the basic stuff you mentioned is implemented right.
It is already *WORKING* on Linux and Windows platforms without any
problems.
I encounter this problem probably because Solaris does not support random
device !!!
The
Hi everybody,
I am using the DH algorithm to produce a symmetric key (based on DSA private
and public keys).
There was no problem on Linux and Windows platforms as long as I had a
random device.
On Solaris platform, the routine DH_generate_key(dh) fails, because there is
no random device (and the
If all you're callling is DH_generate_key(...) then it should create
different keys. That function call only generates the public and private
keys. What you need to do is:
DH_generate_parameters(...)
transfer the parameters between machines so that they are both working in
the same field
Of course I'm calling the DH_compute_key(...) after sharing the DH public
key both sides.
The symmetric keys are already produced successfully on Windows and Linux.
Thanks, Ohad.
-Original Message-
From: Joseph Ashwood [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 14, 2001 6:14
Most likely these will sound like really stupid questions, but honest
they're the same questions I've had to ask myself to find the answers. Have
you verified that the parameters used by both sides are the same? Have you
verified that the public key is transferred correctly? I'm just trying to
Hi Joe.
All the basic stuff you mentioned is implemented right.
It is already *WORKING* on Linux and Windows platforms without any problems.
I encounter this problem probably because Solaris does not support random
device !!!
The manual seeding of the PRNG probably cause this problem (symmetric
"Bruker, Ohad" wrote:
Hi Joe.
All the basic stuff you mentioned is implemented right.
It is already *WORKING* on Linux and Windows platforms without any problems.
I encounter this problem probably because Solaris does not support random
device !!!
The manual seeding of the PRNG probably
12 matches
Mail list logo
