It will be nice to have the option to configure more secure alternatives to HMAC-SHA1. Like HMAC-SHA256.
In general, SHA2 will be nice and SHA3 will e perfect!
RFC: https://datatracker.ietf.org/doc/html/draft-uberti-behave-turn-rest-00#section-2.2
HMAC-SHA1 is one HMAC algorithm that can be used, but any algorithm that incorporates a shared secret is acceptable, as long as both the web server and TURN server use the same algorithm and secret.
It will be nice to have the option to configure more secure alternatives to HMAC-SHA1. Like HMAC-SHA256.
In general, SHA2 will be nice and SHA3 will e perfect!
RFC: https://datatracker.ietf.org/doc/html/draft-uberti-behave-turn-rest-00#section-2.2
HMAC-SHA1 is one HMAC algorithm that can be used, but any algorithm that incorporates a shared secret is acceptable, as long as both the web server and TURN server use the same algorithm and secret.