1 Topic by blink

(2 replies, posted in wolfSSL)

I found that the 'a' and 'b' param in " const ecc_set_type ecc_sets[]" is no-use.So I change them to some other numbers , the result is also correct!
So,In wolfssl, how does the 'a' and 'b' param influence the results?
smile  smile  smile

Go to forum: wolfSSL

2 Reply by blink

(2 replies, posted in wolfSSL)

Thank you your help!
I found the segment error's reason is that my PC is x86_64,when I using command "linux32" to enter x86 mode and rebuild ,the error goes away!

Go to forum: wolfSSL

3 Topic by blink

(1 replies, posted in wolfSSL)

1.Use wc_ecc_make_key() I can get a new private-key,but I don't find the mothod that generate a new pub-key from the private-key.Does it means that just make two  key ,one for private-key, one for pub-key ,and transmit the pub-key to others to generate the share-key?
2.Now I have two machine ,A and B. A use openssl to generate private-key, pub-key , share-key and B use wolfssl to do that,how can I make A and B generate the same share-key?
smile  smile  smile

Go to forum: wolfSSL

4 Topic by blink

(2 replies, posted in wolfSSL)

When I build the benchmark.c within the project, tests works well.
But when I copy the benchmark.c to a new project,and create a makefile to build it, I got some errors.
1.the definition of HAVE_ECC
    Even I include ecc.h in the source file, I have to add "#define HAVE_ECC" to avoid the compile error.
2.segment err
    I modify the benchmark.c only to test the ECC function.In bench_eccKeyGen(),the var "i" in the for loop is always zero,so I get a dead loop
    If I move the local var "i" to a global var, it seems work ,but got a segment err!
So,It seems that ,only include the HeadFiles and load the Lib file cannot use the wolfssl correct!
Is there any step I missed or something need to pay attention？
smile  smile  smile

Go to forum: wolfSSL