Hi, Gregory!
This looks like a bug - please open a ticket on our GitHub tracker[1] to
keep track of this issue.
[1] https://github.com/OpenSIPS/opensips/issues
Best regards,
Răzvan Crainea
OpenSIPS Core Developer / SIPhub CTO
http://www.opensips-solutions.com / https://www.siphub.com
On 10/26/23 18:03, Gregory Massel via Users wrote:
Hello
I'm using OpenSIPS 3.4.2.
When using tls_wolfssl.so, $tls_peer_subject_cn appears to always be <null>.
However, when changing to tls_openssl.so, $tls_peer_subject_cn is then
set correctly.
Is this an issue within tls_wolfssl, or, is $tls_peer_subject_cn only
meant to work with OpenSSL?
--
Regards
*Gregory Massel*
*T* +27 87 550 0000
*F* +27 11 783 4877
*W* www.switchtel.co.za <http://www.switchtel.co.za/>
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
