Henrik Maier

I have the same issue with verion 4.0.8. I believe this bug makes it impossible to use the Ethernet server accepting Ethernet client connections using the standard implementation: client =...

@michaelthomasj Thank you. It almost looks like the code for padding the last block is missing in the implementation of the CCM decrypt routine. I had a look at FSP's...

@michaelthomasj Thank you for looking into this issue. > The spec states that all data should be 16-bit aligned : We are not violating the spec because we are not...

Microsofts spec is probably based on the standard AES modes like CBC which requires a 16-byte blocksize. Looking at [RFC4309 section 3.2 ](https://www.rfc-editor.org/rfc/rfc4309.html), AES-CCM does seem to not require plaintext...

I extracted our code into a smaller test program. It can be used to connect to the following OpenSSL test server: openssl s_server -dtls -accept 1337 -nocert -psk deadbeef -psk_identity...

We have been using the Renesas Ethernet drivers and never had that issue, FSP related issues can be logged here https://github.com/renesas/fsp

@elrafoon I read your reasoning but I also know that we had no issues with running TCP/IP protocol on Ethernet and that's the experience I wanted to share as fellow...

You can see the existing ports here: https://github.com/eclipse-threadx/threadx/tree/master/ports and Intel x86 or x64 processors are not listed here. There is only a win32 port which runs on 32-bit Windows and...

It appears you are using `g++` to compile ThreadX code. ThreadX is written in C not C++, so try using `gcc` instead of `g++`. In case you want to compile...

This is an interesting discussion and like to share some thoughts on this topic. The effort which is required to implement hardware accelerated crypto routines must not be underestimated. I...