1 Reply by mark doyle

(6 replies, posted in wolfSSL)

I've written RSA with OAEP public key encryption and private key decryption functions for Wolfcrypt. It's not fully tested, but is intended for a commercial product. I've tried it on an embedded Linux board running an Arm in little endian mode. If anyone wants the beta code, send me an email. Usual warning about no warranty of any kind applies, but eventually, I have to be sure it works in my product, at least. Anybody that want's to test / improve it is welcome.

Go to forum: wolfSSL

2 Reply by mark doyle

(6 replies, posted in wolfSSL)

Could you give me the status of this? I also need RSA with OAEP for an embedded implementation of the DNP3 Secure Authentication Version 5 specification.

Go to forum: wolfSSL

3 Reply by mark doyle

(2 replies, posted in wolfSSL)

Thanks for your quick reply Kaleb. The explanation of options.h and settings.h makes sense to me, but I'm even more confused now by the presence in many files like aes.c of
#ifdef HAVE_CONFIG_H
   #include <config.h>
#endif

What got me concerned originally was I noticed when I built the library using make, I got an mp_digit size of 4 because SIZEOF_LONG_LONG was defined as 8. Then when I moved the code to the OEM build system, I got an mp_digit size of 2 because SIZEOF_LONG_LONG was undefined. That's when I found that SIZEOF_LONG_LONG was defined in config.h, which seems like a strange place for it to be anyway. The library worked with my test code built either way, but the difference worried me. To get the OEM build to give me an mp_digit of 4, I had to define HAVE_CONFIG_H.

Thanks again for your help.
Mark

Go to forum: wolfSSL

4 Topic by mark doyle

(2 replies, posted in wolfSSL)

I'm building for two platforms: one is Linux, the other is bare-metal with an OEM board support package, and they both use the same processor (Arm 926 EJS). I've got the Linux version working fine and am about to move to the bare-metal version. I'm confused about the various configuration files such as config.h, settings.h, and options.h. I was particularly surprised that rerunning the configure script did not seem to modify config.h.

When I go to the non-Linux make system of the OEM BSP (that will not use the makefile generated by the configure script), which header files do I need to be concerned with to make sure all the required #define's are correct? More generally, what are the outputs of the configure script.

Thanks.

Go to forum: wolfSSL