Hi delphiwolf,

In January our library underwent a name change from CyaSSL to wolfSSL the cyassl and ctaocrypt directories now contain bakwards-compatibility files for clients who had the library prior to the name change. This way if they update to our newest release any existing projects they have will still compile with the old API calls.

If you are starting fresh with the latest API and do not need backwards compatibility in most cases they will not be needed.
Cases when they would be needed:
      1. Some of our example projects if you decide to use them may reference an old API call that was left in place for
          compatibility testing.
      2. If working in a Unix/Linux environment and building our library with auto tools, Makefile.am will expect cyassl and
          ctaocrypt directories to be there and will fail if they are not.
      3. Some files have the line "#include <cyassl/ssl.h>" for backwards compatibility. If you get an error saying the file cannot
          be opened simply remove that line if you do not need that functionality.

While working on your projects should you decide to remove cyassl/ and ctaocrypt/ directories and you come across an error like the following: "Undefined reference to CyaSSL_get_cipher did you mean wolfSSL_get_cipher?" that is an example of the compatibility layer not being in place simply change the name and you will be linking against the new API. for a complete list of the name changes reference cyassl/ssl.h.

Kind Regards,

Kaleb