Hi telina,

The most common culprit for seg faults during math operations is that the wolfSSL library and the application have not been compiled with the same preprocessor defines.

If you are using Autoconf (./configure) to configure and make the library, this will generate the <wolfssl/options.h> header with the defines used during compilation of wolfSSL.  Your application can then simply include <wolfssl/options.h> as the first wolfSSL header include, ie:

#include <wolfssl/options.h>
#include <wolfssl/wolfcrypt/dh.h>

Can you verify that you are using the same preprocessor defines when compiling both wolfSSL and your test app?

If that matches, can you please send me more details about the platform you are compiling on, how you are compiling wolfSSL, and a simple test app that demonstrates the seg fault?

Thanks!
Chris

Great, glad to hear, thanks for letting me know!

Hi Ravi,

To get this support added to wolfSSL, we can either:

A.  Add this to our internal desired features list.  There is no official timeline associated with features on this list, and they are added as they are received when we get free time in engineering.

B.  Accelerate this feature addition through wolfSSL engineering services.

Which option would you prefer?

Thanks,
Chris

Great, glad to hear you got it resolved!

Best Regards,
Chris

Hi,

wolfSSL doesn't support loading certificates in the .p7b format yet.  We do support loading them through .pem and .der files and/or buffers, and through PKCS#12 bundles.

Are you able to convert your .p7b certificate to a different format, or is .p7b mandatory for your use case?

Best Regards,
Chris

Hi,

In this case, "ant/" is a subdirectory under JUNIT_HOME, which then contains "ant-junit4.jar".

/etc/environment sets variables system-wide, whereas .bashrc will set it only for your user.  You can also set it manually when you open a shell using:

export JUNIT_HOME=/path/to/junit/dir

When WolfSSLTestSuite fails, there should be a report file generated at:

<wolfssl-jni-root>/build/reports/TEST-com.wolfssl.WolfSSLTestSuite.txt

Can you inspect that file and share what it tells you?

Thanks,
Chris

Hi muyouyuwan,

A rule of thumb is that the overhead of adding SSL/TLS to a connection will be about 30%, but this will vary depending on what cipher suite and key sizes you are using for the connection.

SSL/TLS also has a maximum record size of 16kB.  Depending on the size of your file being transferred, the more chunks being done will increase the overhead.

We typically run the wolfCrypt benchmarks as a gauge of performance, since the performance of the SSL/TLS layer is directly dependent on the underlying cryptography performance.

The benchmark application source is located in wolfcrypt/benchmark/benchmark.c. For *nix platforms, the benchmark can be ran using ./wolfcrypt/benchmark/benchmark. The benchmark is compiled by default.  If benchmarking on an embedded platform, define BENCH_EMBEDDED to reduce resource use.  For more details regarding benchmarking wolfSSL and reference numbers we have gathered in the past, please reference the wolfSSL and wolfCrypt Benchmarks webpage:

https://www.wolfssl.com/wolfSSL/benchmarks-wolfssl.html

Best Regards,
Chris

Hey Marco,

Thanks for letting us know about your issue.  I'll forward your question to our SSH expert for a response.

Thanks,
Chris

Hi savek,

As of the following commit, wolfSSL will now request the correct certificate type in the CertificateRequest message when using ECDSA-CHACHA cipher suites.  This will be included in our next stable release of wolfSSL.

https://github.com/wolfSSL/wolfssl/pull … 8489230ed3

Thanks,
Chris

Circling back around on this topic, wolfSSL 3.9.10 now has support for the TLS Extended Master Secret extension.  This is enabled by default.

Hi,

Correct, you will want to use wolfCrypt's API if only interested in doing encryption/decryption operations separate from SSL/TLS.

The wolfCrypt API reference can be found here:
https://wolfssl.com/wolfSSL/Docs-wolfss … rence.html

And, for code examples, one of the best places to look will be at the wolfCrypt test application (./wolfcrypt/test/test.c).  This file contains test code for all of wolfCrypt's crypto algorithms, and as such can act as a good usage example.  Each algorithm has it's own test function.  For example, for AES, the test function is called aes_test().

https://github.com/wolfSSL/wolfssl/blob … est/test.c

There are also a few examples in the "wolfssl-examples" repository on GitHub:

https://github.com/wolfSSL/wolfssl-exam … ter/crypto

Best Regards,
Chris

Hi,

Thanks for the bug report.  This has been fixed with the following commit:

https://github.com/wolfSSL/wolfssl/comm … a1a30f3c95

Thanks,
Chris