You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If no suitable certificate is available, the client MUST send a certificate message containing no certificates. That is, the certificate_list structure has a length of zero.
That enables an server to decide to continue or abort.
Any opinions?
The text was updated successfully, but these errors were encountered:
Use empty client certificate, if a certificate is requested but no
certificate is available.
Issue eclipse#186
Signed-off-by: Achim Kraus <achim.kraus@cloudcoap.net>
Use empty client certificate, if a certificate is requested but no
certificate is available.
Issue eclipse#186
Signed-off-by: Achim Kraus <achim.kraus@cloudcoap.net>
Use empty client certificate, if a certificate is requested but no
certificate is available.
Issue #186
Signed-off-by: Achim Kraus <achim.kraus@cloudcoap.net>
I'm currently on testing the interoperability of the OpenSSL - RPK PR.
If the client has "no suitable certificate", the current implementation in "main" branch aborts the handshake.
dtls.c: check_server_hellodone
An alternative approach would be, to implement RFC 5246 - 7.4.6 - Client Certificate :
That enables an server to decide to continue or abort.
Any opinions?
The text was updated successfully, but these errors were encountered: