Steve,
It is word aligned. I tried different ways to prepend the value in DH-d but
it is not working. When I dump the memory it shows leading zeros but when I
print the same DH-d using BN_print_fp it does not show zeros which is
expected but leading zeros are not increasing the num_bytes
it is BIGNUM-d not DH-d
--
View this message in context:
http://openssl.6102.n7.nabble.com/DH-compute-key-query-tp13943p48184.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
__
OpenSSL Project
Thanks Steve. Issue is fixed please ignore my previous email.
--
View this message in context:
http://openssl.6102.n7.nabble.com/DH-compute-key-query-tp13943p48186.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
Steve,
I am also facing a similar issue. In my case the key generated by
DH_compute_key need to be used by hash function for authentication purpose.
Even after prepending the key with zeros, hash'd value is not same as the
other end.
Is there any built-in or openSSL function that will prepend
Sindya,
Looking at the hexdump issue earlier in the thread, I have a question for
you. Is your memory buffer block or word aligned? Some mismatch here may
cause some block computation issues.
- Steve
Steve,
I am also facing a similar issue. In my case the key generated by
DH_compute_key
On Thu, Jul 21, 2011, Prashant Batra wrote:
Hello,
I am using DH exchange in ikev2 for generating secret key b/w 2 parties.
I am observing some awkward thing,
in some of the cases, the secret calculated by both the parties is not the
same, although the input (public key, private key and
Thanks Steve a ton. I think I was missing some basic design understanding.
-Prashant
On Fri, Jul 22, 2011 at 5:08 PM, Dr. Stephen Henson st...@openssl.orgwrote:
On Thu, Jul 21, 2011, Prashant Batra wrote:
Hello,
I am using DH exchange in ikev2 for generating secret key b/w 2 parties.
Hello,
I am using DH exchange in ikev2 for generating secret key b/w 2 parties.
I am observing some awkward thing,
in some of the cases, the secret calculated by both the parties is not the
same, although the input (public key, private key and peer public key ) is
same.
Hexdump: Length [128]