1 Reply by toe

(10 replies, posted in wolfSSL)

Thank you for the hint, with the hint with the 16-bit to byte  assignment.

Here is the the error throughing code of DTLS 1.0 and the correct output of DTLS 1.2 for comparison:

DTLS 1.0

received record layer msg

wolfSSL Entering DoDtlsHandShakeMsg()

wolfSSL Entering DoHandShakeMsgType

processing client key exchange

wolfSSL Leaving DoHandShakeMsgType(), return 0

wolfSSL Leaving DoDtlsHandShakeMsg(), return 0

More records in input

received record layer msg

got CHANGE CIPHER SPEC

More records in input

received record layer msg

wolfSSL Entering DoDtlsHandShakeMsg()

wolfSSL error occured, error = -210

ERROR

wolfSSL Entering SSL_accept()

received record layer msg

wolfSSL Entering DoDtlsHandShakeMsg()

wolfSSL error occured, error = -210

ERROR


****************
DTLS 1.2
received record layer msg

wolfSSL Entering DoDtlsHandShakeMsg()

wolfSSL Entering DoHandShakeMsgType

processing client key exchange

wolfSSL Leaving DoHandShakeMsgType(), return 0

wolfSSL Leaving DoDtlsHandShakeMsg(), return 0

More records in input

received record layer msg

got CHANGE CIPHER SPEC

More records in input

received record layer msg

wolfSSL Entering DoDtlsHandShakeMsg()

wolfSSL Entering DoHandShakeMsgType

processing finished

wolfSSL Leaving DoHandShakeMsgType(), return 0

wolfSSL Leaving DoDtlsHandShakeMsg(), return 0

accept state  ACCEPT_SECOND_REPLY_DONE

growing output buffer


accept state  CHANGE_CIPHER_SENT

growing output buffer

The line with text ERROR is given on application layer.

Go to forum: wolfSSL

2 Reply by toe

(10 replies, posted in wolfSSL)

Hey,
I already got the cookie callback to work. 

/* 
 *Creates a simple pseudo Cookie, easy to find in hexdump
 */
int MyEmbedGenerateCookie(WOLFSSL* ssl, byte *buf, int sz, void *ctx) {
  int i;
  
  for (i=0; i<sz; i++)
  buf[i]= 0xDADA;
  return sz;
}

I was interested in the arguments and the expected return value. What is delivered in buf? I don't use it, but I'm intrested.

It's also interesting now, that everything works fine with DTLS1.2 but I receive an error when I use DTLS1.0, somewhere at the ChangeCipferSpec message. But that's another story which I won't follow up.
KR

Go to forum: wolfSSL

3 Reply by toe

(10 replies, posted in wolfSSL)

Hey,
I finally got everything working on my stm32f4 evaluation board, where I use FreeRTOS 7.4.0 and wolfSSL embedded SSL 2.6.1 for DTLSv1.2.
Because I'm using the USART Interface for communication, I have now the problem with the missing cookie callback.
Would you provide me some infos, what is needed. Since I'm not affected to DoS attacks, I just need something trivial to walk through.
KR Thomas

Go to forum: wolfSSL