Topic: i2o_ECPublicKey Not Working... (Read 1647 times)
I'll give you the 100 reputation bounty tomorrow when it lets me.
Woohoo, I finally got some reputation on SO...
Thank you!
Should have figured that myself...
Should have figured that myself...
I've spent the last week working on testing the scripts and improving the code quote dramatically.
Now I've been able to install OpenSSL 1.0.1c successfully and link it correctly but...
It still doesn't work. Does anyone know why i2o_ECPublicKey doesn't work? It works in the C++ bitcoin client so why not my code?
http://stackoverflow.com/questions/10906524/openssl-i2o-ecpublickey-not-working
Now I've been able to install OpenSSL 1.0.1c successfully and link it correctly but...
It still doesn't work. Does anyone know why i2o_ECPublicKey doesn't work? It works in the C++ bitcoin client so why not my code?
http://stackoverflow.com/questions/10906524/openssl-i2o-ecpublickey-not-working
I know why it doesn't work and I posted a solution for you. Enjoy.
I've spent the last week working on testing the scripts and improving the code quote dramatically.
Now I've been able to install OpenSSL 1.0.1c successfully and link it correctly but...
It still doesn't work. Does anyone know why i2o_ECPublicKey doesn't work? It works in the C++ bitcoin client so why not my code?
http://stackoverflow.com/questions/10906524/openssl-i2o-ecpublickey-not-working
Now I've been able to install OpenSSL 1.0.1c successfully and link it correctly but...
It still doesn't work. Does anyone know why i2o_ECPublicKey doesn't work? It works in the C++ bitcoin client so why not my code?
http://stackoverflow.com/questions/10906524/openssl-i2o-ecpublickey-not-working
@2112: I think I know what you meant now. To use weak linking? I might do that actually.
I haven't had time to sort out the OpenSSL headers yet but I still think the i2o_ECPublicKey won't work. If anyone understands it better please explain what might be wrong. Maybe the correct headers suddenly solves everything but I think that is a long shot.
I haven't had time to sort out the OpenSSL headers yet but I still think the i2o_ECPublicKey won't work. If anyone understands it better please explain what might be wrong. Maybe the correct headers suddenly solves everything but I think that is a long shot.
I must be dumb for not realising OPENSSL_VERSION_TEXT is a macro so it is being received by the old headers. I'll include the correct headers and look again later.
But no doubt the right library binaries are being loaded.
And yes I've always hated this linking nonsense.
But no doubt the right library binaries are being loaded.
And yes I've always hated this linking nonsense.
Does anyone know what on earth is going on?
"man dyld" knows. In the other thread about pointers to functions I expressed the suspiction that you simply don't understand the concepts of dynamic linking. Now I have a confirmation of that suspiction.I'm so sorry.
Well I verified that the dylib and a files were for OpenSSL 1.0.1c by searching for the version in the files. Indeed I had libcrypto and libssl files for 1.0.1c. So I tried adding them to Xcode. First I ensured the -lssl and -lcrypto flags were removed and I tried the dylibs first. This is what I got:
I found this odd. Surely the dynamic libraries can be loaded from any directory?
Well I tried moving them to /usr/local/ssl/lib/ and I get this:
Erm... So a 1.0.1c dylib that gives the version 0.9.8r? Clearly something is corrupted. I get similar problems with the static libraries. "0.9.8r" is not anywhere in the library files but "1.0.1c" is. Does anyone know what on earth is going on?
Code:
warning: Unable to read symbols for /usr/local/ssl/lib/libcrypto.1.0.0.dylib (file not found).
warning: Unable to read symbols from "libcrypto.1.0.0.dylib" (not yet mapped into memory).
warning: Unable to read symbols for /usr/local/ssl/lib/libssl.1.0.0.dylib (file not found).
warning: Unable to read symbols from "libssl.1.0.0.dylib" (not yet mapped into memory).
[Switching to process 1266 thread 0x0]
dyld: Library not loaded: /usr/local/ssl/lib/libcrypto.1.0.0.dylib
Referenced from: /Users/matt/Library/Developer/Xcode/DerivedData/cbitcoin-bdkcvvuopgevvwcciljkluzxqser/Build/Products/Debug/testKeyHash
Reason: image not found
I found this odd. Surely the dynamic libraries can be loaded from any directory?
Well I tried moving them to /usr/local/ssl/lib/ and I get this:
Code:
OpenSSL version: OpenSSL 0.9.8r 8 Feb 2011
Erm... So a 1.0.1c dylib that gives the version 0.9.8r? Clearly something is corrupted. I get similar problems with the static libraries. "0.9.8r" is not anywhere in the library files but "1.0.1c" is. Does anyone know what on earth is going on?
Hello. To get anywhere with my bitcoin library I clearly need to have a cryptography library working. OpenSSL is playing up big time.
I have this test program:
But i2o_ECPublicKey corrupts the pubKey memory block. See here: http://stackoverflow.com/questions/10906524/openssl-i2o-ecpublickey-not-working
I'm using OpenSSL 1.0.1c.
Until this is sorted there is a major problem with developing cbitcoin.
Thanks.
I have this test program:
Code:
#include
#include
#include
int main(){
printf("OpenSSL version: %s\n",OPENSSL_VERSION_TEXT);
EC_KEY * key = EC_KEY_new_by_curve_name(NID_secp256k1);
if(!EC_KEY_generate_key(key)){
printf("GENERATE KEY FAIL\n");
return 1;
}
u_int8_t pubSize = i2o_ECPublicKey(key, NULL);
if(!pubSize){
printf("PUB KEY TO DATA ZERO\n");
return 1;
}
u_int8_t * pubKey = malloc(pubSize);
if(i2o_ECPublicKey(key, &pubKey) != pubSize){
printf("PUB KEY TO DATA FAIL\n");
return 1;
}
u_int8_t * hash = malloc(SHA256_DIGEST_LENGTH);
SHA256(pubKey, pubSize, hash);
for (int x = 0; x < 32; x++) {
printf("%.2x",hash[x]);
}
EC_KEY_free(key);
free(pubKey);
free(hash);
return 0;
}
But i2o_ECPublicKey corrupts the pubKey memory block. See here: http://stackoverflow.com/questions/10906524/openssl-i2o-ecpublickey-not-working
I'm using OpenSSL 1.0.1c.
Until this is sorted there is a major problem with developing cbitcoin.
Thanks.
Jump to: