Support for Public Key (PK) callbacks with PSK

[dgarske]

Description

Support for Public Key (PK) callbacks with PSK in TLS v1.2 and TLS v1.3 (client and server).

Add support for returning USE_HW_PSK from the PSK callbacks:

• wolfSSL_CTX_set_psk_server_callback
• wolfSSL_CTX_set_psk_client_callback
• wolfSSL_CTX_set_psk_server_tls13_callback
• wolfSSL_CTX_set_psk_client_tls13_callback

Fixes ZD 17383

Testing

./configure --enable-psk --enable-pkcallbacks CFLAGS="-DTEST_PK_PSK"
make check

Checklist

• added tests
• updated/added doxygen
• updated appropriate READMEs
• Updated manual and documentation

[dgarske]

Retest this please

[JacobBarthelmeh]

On Mac OS with latest wolfSSL master branch + this PR I see a failure with the unit tests:

I hear you fa shizzle!
starting psk cipher suite tests
starting TLS 1.3 psk no identity extra cipher suite tests
trying server command line[2007]: SuiteTest -v 4 -s -l TLS13-AES128-GCM-SHA256 -d -2 -p 0 
trying client command line[2008]: SuiteTest -v 4 -s -l TLS13-AES128-GCM-SHA256 -2 -p 58037 
PSK Server TLS 1.3 using HW (Len 32, Hint Client_identitySHA256)
SSL_accept error -333, psk key callback error
wolfSSL error: SSL_accept failed
wolfSSL_connect error -313, received alert fatal error
wolfSSL error: wolfSSL_connect failed

This is with doing:

./configure --enable-psk --enable-pkcallbacks CFLAGS="-DTEST_PK_PSK" && make
./tests/unit.test

[dgarske]

On Mac OS with latest wolfSSL master branch + this PR I see a failure with the unit tests:

I hear you fa shizzle!
starting psk cipher suite tests
starting TLS 1.3 psk no identity extra cipher suite tests
trying server command line[2007]: SuiteTest -v 4 -s -l TLS13-AES128-GCM-SHA256 -d -2 -p 0 
trying client command line[2008]: SuiteTest -v 4 -s -l TLS13-AES128-GCM-SHA256 -2 -p 58037 
PSK Server TLS 1.3 using HW (Len 32, Hint Client_identitySHA256)
SSL_accept error -333, psk key callback error
wolfSSL error: SSL_accept failed
wolfSSL_connect error -313, received alert fatal error
wolfSSL error: wolfSSL_connect failed

This is with doing:

./configure --enable-psk --enable-pkcallbacks CFLAGS="-DTEST_PK_PSK" && make
./tests/unit.test

Yes that is expected. The PK callback is not setup to inject a master secret, so this failure occurs. This work is being done for a customer's HSM. I understand if we need to hold off on merging until that is completed.