Hi bstraehl,

Thanks for contacting wolfSSL!

This sounds like a reasonable request to add a function that can convert time to a human-readable format.

We are tracking this request internally.

If there is a timeline associated with this please let me know so we can try to expedite the request.

Thanks,
Tesfa

Hi Derry,

I'm glad to hear that you got it working.
If you are interested in contributing your changes, you can open a pull request at https://github.com/wolfSSL/wolfssl.

Cheers,
Tesfa

Hi EPT,

The basic configurations for wolfSSL and wolfSSH are as follows:

cd wolfssl
./configure --enable-ssh && make && sudo make install

cd wolfssh
./configure && make && sudo make install

You can see the default configurations in the autogenerated wolfssl/options.h.

Hope this helps.

Hi EPT,

Thanks for contacting wolfSSL!

Could you please elaborate on what you want to accomplish with unifdef?

You can use autotools or cmake to build wolfSSL library. wolfSSL is configured with some default configurations and they can be changed with `./configure --disable-funoption`.  You can display the list of options with `./configure -h`.  Configure auto-generates `wolfssl/wolfssl/options.h` containing the #define/#undef of features. 

You can run the wolfcrypt, benchmark, or client/server examples.

./wolfcrypt/test/testwolfcrypt
./wolfcrypt/benchmark/benchmark
./examples/server/server
./examples/client/client

Let me know if this helps.

Hi Derry,

Thanks for reaching out to wolfSSL with your question.

I think you have a couple of options to add the ARIA cipher.

1. You can create a new file `wolfssl/wolfcrypt/src/aria.c` similar to `wolfssl/wolfcrypt/src/aes.c`, add a build/configure option in configure.ac, update include.am, cipher suite names and etc. I would suggest your search for AES GCM to narrow down your search results.

Or

2. You can consider adding a new macro (e.g. WOLFSSL_ARIA_CRYPT)  and create new file `wolfcrypt/src/port/aria/aria-aes.c` similar to `wolfcrypt/src/port/ti/ti-aes.c` with your implementations. You can edit wolfssl/wolfcrypt/src/aes.c and choose your implementations similar to the way we handle hardware acceleration support. 

If you need the cipher name changed then you would have to go with option #1. Otherwise, option #2 is easier and cleaner but the cipher name shows AES but you are really doing ARIA cipher.

Please let me know if this helps or you can also send us any follow-up questions to support@wolfssl.com.

Thanks,
Tesfa

Hi stroebeljc,

Thanks for contacting wolfSSL!

We have made some improvements in our CMake build and that feature was likely missed.

I'll discuss this "enhancement" request with my colleague next week and get back to you.

Thanks,
Tesfa

Hi Scotty2541,

Sorry to hear that you are having issues building wolfSSL library.

It looks like you are running into a common problem with Eclipse performing a wildcard search of *.c and *.s files and building all source code.

I think your proposed solution to add `#ifdef WOLFSSL_ARMASM` is good.

The preferred alternative solution is to remove source codes that are not relevant to your platform.
Specifically, you need to remove platform-specific assembly source files in
    -   wolfssl/wolfcrypt/src/port/*`dir
    -   wolfsslPort/wolfcrypt/src/aes_asm.asm
    -   wolfsslPort/wolfcrypt/src/aes_asm.S

Please let me know if this helps.