Hi,

I can confirm that wolfSSL 3.7.0 downloaded from the wolfssl.com download page compiles correctly on an Ubuntu 14.04 64-bit virtual machine.

I have the following aclocal version:

$ aclocal --version
aclocal (GNU automake) 1.14.1

What version of aclocal do you have installed?

Thanks,
Chris

Hi,

How and where did you download wolfSSL from?  Can you confirm what steps you are using to compile the library?  A normal build would be similar to:

unzip wolfssl-3.7.0.zip
cd wolfssl-3.7.0
./configure
make

Thanks,
Chris

Hi alex_b,

If you would like wolfSSL to hang on to the peer certificate after the SSL/TLS handshake, you can define KEEP_PEER_CERT when compiling wolfSSL.

With wolfSSL, by default the verify callback is only called upon verification failure.  wolfSSL handles certificate verification internally, which is unlike OpenSSL that forces the user to do the verification.  This means that on all failure cases, the preverify parameter will be zero. 

Optionally, you can force wolfSSL to call the verify callback on every verification - regardless if it is successful or a failure - by defining WOLFSSL_ALWAYS_VERIFY_CB.  In this case, if preverify is equal to "1", wolfSSL has already successfully verified the peer certificate.  We provide this option for those users who wish to do custom inspection of certificate elements past normal certificate verification measures.

Does this help clear things up?

Best Regards,
Chris

Hi cfarrin,

Great, thanks for the update.  Glad to hear you have it working!

Best Regards,
Chris

Hi jurkovi,

What Cortex-M4 processor are you using for your benchmarks?  And what public key size are you using (1024, 2048, 4096, ...)?

Are you using the wolfCrypt benchmark application to run the benchmarks?

Thanks,
Chris

Hi vittico,

wolfSSL proper has had ECC support for roughly three years now.  If you're starting off a new project with wolfSSL, I would recommend downloading the latest stable version (3.7.0) from our download page:

https://wolfssl.com/wolfSSL/download/downloadForm.php

We have a JNI wrapper for wolfSSL called "wolfSSL JNI".  We bundle this as a separate product, which also wraps the DTLS 1.2 support of wolfSSL.  You can find more info about this product at the below URL, and download it from the same download page as above.  FYI, we have a new version of wolfSSL JNI that will be compatible with the 3.7.0 release coming out this week.

https://www.wolfssl.com/wolfSSL/Product … sljni.html

Best Regards,
Chris

Hi cfarrin,

We just recently added the wolfSSL_get_jobject() function to better handle some of the internal callbacks in JNI.  You'll need to update the "wolfssl" git submodule to the current HEAD.

I'll work on updating our wolfssl-examples repository with this change as well.

Best Regards,
Chris

Hi gawiz,

As a follow-up, we have examples of using SHA-256 in our wolfCrypt test application.  This can be found in the wolfSSL package at the following location:

<wolfssl_root>/wolfcrypt/test/test.c

Specifically, inside of the sha256_test() function.  Do you mind if I ask what you are working on?

Thanks,
Chris

Hi Gareth,

The wolfSSL_SHA256_Init(), wolfSSL_SHA256_Update(), and wolfSSL_SHA256_Final() functions are part of the wolfSSL OpenSSL Compatibility layer.  Are you enabling that layer at compile time when you are building wolfSSL?  You can do that when using ./configure with "--enable-opensslextra", or if using preprocessor flags by defining OPENSSL_EXTRA.

If you don't want to use the OpenSSL Compatibility Layer, you can use our wolfCrypt SHA-256 functionality directly through the following header file:

<wolfssl/wolfcrypt/sha256.h>

Specifically the following functions:

int wc_InitSha256(Sha256* sha);
int wc_Sha256Update(Sha256* sha, const byte* data, word32 len);
int wc_Sha256Final(Sha256* sha, byte* out);

Best Regards,
Chris

Hi naftaliz,

We just finished integration and testing with the current VxWorks release (7).  This includes support for AES-256.

Best Regards,
Chris