I've put up a PR 196 to fix this and have added tests to cover this type of error.

Hi Messias,

I've fixed an issue and added a test for RSAES in a PR

Attached is a program I used to test against the website you linked. The output is binary. I tested against the website by converting the output to base64 `base64 out.bin` and copy-paste into RSA Decryption. To test against openssl I ran `openssl rsautl -decrypt -inkey rsa2k.pem -in out.bin`

Note: that for OAEP with SHA1, in order to be compatible you must change the default HASH of wolfTPM by adding `CFLAGS=-DWOLFTPM2_WRAP_DIGEST=TPM_ALG_SHA1` to configure. This is not needed for RSA/ECB/PKCS1Padding. For openssl with SHA256 (wolfTPM default) you can decrypt with `openssl pkeyutl -inkey rsa2k.pem -in out.bin -pkeyopt rsa_padding_mode:oaep -pkeyopt rsa_oaep_md:sha256 -decrypt`

Hi Preeti,

I understand your goals and you are correct that we don't currently have a VS solution. wolfTPM windows support is relatively new addition. We would be interested improving support but have limited resources. If you'd like to discuss in more detail please feel free to reach out to support@wolfssl.com

There is an experimental cmake branch that can be used with MSVC, but it doesn't have support for a static library currently.

Thanks,
Jeff

Hi jw,

I see that some other platforms also receive that error with that server under the handshake simulation section of the link you provided.

What version of wolfSSL are you using? Can you supply some additional information about how you have configured the client to connect to that server?

Thanks,
Jeff

Hi Messias,

I found a smaller example and will look a little closer for a solution. wolfTPM is including minwindef.h which defines WIN32 and results in the error.

#include <minwindef.h>
#include <curl/curl.h>    

The same error can be generated by compiling a file that includes curl.h under msys2 and using -DWIN32

As a work around I was able to add a line to undefine WIN32 before including curl.h although I had runtime errors then, so do not think this is the correct solution.

#undef WIN32
#include <curl/curl.h> 

Hi Messias,

I was able to reproduce the errors and have created a PR to address the initial error you reported. Thanks for the report.

I believe the new errors you are seeing may require you to rebuild and install wolfSSL if you wish to use `mingw64.exe`

Let me know if those address your build issues. Feel free to reach out to support@wolfssl.com if you have any questions or to discuss specific use-cases.

Cheers,
Jeff

Hi jy824212,

There are a few APIs that may be useful to you that start with `wc_ecc_export_`.  See the  header.

Hope that helps,
Jeff

Hi junioarssuncaolp,

Can you tell us more about your use-case?

I think for TPM2_CertifyCreation, the signHandle needs to be set and match the session auth. I was able to get a different error TPM_RC_SENSITIVE.

I'll try to get a working example.

Hi Hadrien,

As you are discovering the Windows support for TPM is by default quite restricted. Windows is our most recently added platform and we are aiming to improve the documentation and examples around it.

Can you explain more about your goals for authentication? Are you interested in the state of the machine or just that it is the machine with the specific TPM present?

The specification is the best source, but sometimes other sources can be good to understand the purpose at a higher level. Here are a few links I found helpful

• TPM interactive lesson

• credential Activation

• Windows Certificate

You may also be interested in looking at our TLS examples if you haven't yet.

If you are interested in unblocking TPM commands in Windows, proceed with caution. And read https://docs.microsoft.com/en-us/window … /using-tbs

Thanks for the feedback. We are always aiming to improve our documentation.

Hi Remy,

I was not able to reproduce. Can you share you configuration of wolfssl?

I've attached the program I used to build. I configured v4.7.0-stable with `./configure` (no options) and compiled `gcc -o forum_ec forum_ec.c -lwolfssl -I .` I used `wc_PemToDer`and did not get a matching DER buffer

Cheers,
Jeff

Hi dan9er,

We have someon working on updating the support for PPC and testing it for wii. After touching base with them I was able to compile.

For 3DS I was able to compile with

PATH=/opt/devkitpro/devkitARM/bin/:$PATH ./configure  --host=arm-none-eabi --disable-shared --disable-examples --disable-crypttests CFLAGS="-I/opt/devkitpro/libctru/include/ -march=armv6k -mtune=mpcore -mfloat-abi=hard -mtp=soft -mword-relocations -DNO_WRITEV" LDFLAGS="-L/opt/devkitpro/libctru/lib -lctru"
PATH=/opt/devkitpro/devkitARM/bin/:$PATH make -j1 V=1

For PKGBUILD this would reduce to something like

./configure CFLAGS="-DNO_WRITEV" LIBS="-lctru" --host=arm-none-eabi --disable-shared --disable-examples --disable-crypttests --enable-sp-math-all
make

I have not attempted to test actually using the library. I'll put up a draft PR for https://github.com/devkitPro/pacman-packages and update you.

Compiling the examples and tests I am seeing warnings.

c:/msys64/opt/devkitpro/devkitarm/bin/../lib/gcc/arm-none-eabi/10.2.0/../../../../arm-none-eabi/bin/ld.exe: warning: cannot find entry symbol _start; defaulting to 0000000000008020

Any ideas if it's possible to compile the examples and run on 3ds?

If you are able to test on hardware, can you share the results?

To clarify wolfSSL does support passpharse protected keys.

In the main wolfSSL repo the server example supports this with a call to SSL_CTX_set_default_passwd_cb when configured with --enable-enckeys.

See the callback implementation here. wolfSSL_CTX_set_default_passwd_cb_userdata is also useful for supporting these keys.