StephenWall

I see the master branch has some SRTP code with support for AES_CM_128_HMAC_SHA1_80 and AES_CM_128_HMAC_SHA1_32. Any chance of getting support for AES_192_CM_HMAC_SHA1_32, AES_192_CM_HMAC_SHA1_80, AES_256_CM_HMAC_SHA1_32, and AES_256_CM_HMAC_SHA1_80? (See https://www.rfc-editor.org/rfc/rfc6188)

While OpenSSL 3 is now supported, there is no mechanism provided for setting which ciphers to use for TLS 1.3. OpenSSL sets these separately (via `SSL_CTX_set_ciphersuites()`) than for TLS 1.2...

Island nations are invisible, and unselectable, when the map is scaled sufficiently small to be usable (like the demo web page). Would it be possible to set the line thickness...

OpenSSL 1.1.x is soon to be deprecated. To keep current, jwt-cpp needs to support OpenSSL 3.