Thank you Vlad,
I confirm that I was able to load the certificate using wolfssl by setting the
protocol version to TLSv1.
Regards,
Adrian
> On 12 Aug 2021, at 18:12, Vlad Patrascu wrote:
>
> Hi Adrian,
>
> The wolfSSL implementation does not support a TLS method range, such as
> "TLSv1-",
Hi Adrian,
The wolfSSL implementation does not support a TLS method range, such as
"TLSv1-", so that could be one of the causes. What seems strange is that
there is no warning message: "WARNING:tls_wolfssl:tls_get_method:
wolfSSL does not support method range specification" which should be
th
I loaded both modules and I just switch between them via the
tls_library parameter and it loads ok:
loadmodule "tls_openssl.so"
loadmodule "tls_wolfssl.so"
loadmodule "tls_mgm.so"
modparam("tls_mgm", "tls_library", "openssl")
# modparam("tls_mgm", "tls_library", "wolfssl")
I did not test with th
On 12.08.2021 22:17, Adrian Georgescu wrote:
I set it up explicitly now but I get the same result, I tried different domains
or combination but any definition fails to load.
Hi gents,
IIRC (Vlad: please correct me if I'm wrong), this initial version of the
tls_wolfssl module does not have fu
H Ovidiu,
I set it up explicitly now but I get the same result, I tried different domains
or combination but any definition fails to load.
Aug 12 21:10:30 live01 /usr/sbin/opensips[10920]:
ERROR:tls_mgm:init_tls_domains: Failed to init TLS domain 'msteams-server'
Aug 12 21:10:30 live01 /usr/sbi
Hello Adrian,
I managed to use wolfssl by forcing it:
modparam("tls_mgm", "tls_library", "wolfssl")
I haven't tested the auto mode ...
-ovidiu
On Thu, Aug 12, 2021 at 2:59 PM Adrian Georgescu wrote:
>
> After more digging I discovered that this behaviour does not happen when
> loading tls_o
This line looks suspicious as I have not loaded or specified anywhere
tls_openssl.
Aug 12 18:51:15 live01 opensips[6455]: Aug 12 18:51:15 [6455]
DBG:core:solve_module_dependencies: module tls_mgm soft-depends on module
tls_openssl, and it was not loaded — continuing
Adrian
> On 12 Aug 2021,
After more digging I discovered that this behaviour does not happen when
loading tls_openssl module.
tls_openssl loads fine this configuration but tls_wolfssl does not.
> On 12 Aug 2021, at 14:12, Adrian Georgescu wrote:
>
> Hi,
>
> I am using the latest 3.2.0 build with the old TLS configur
Hi,
I am using the latest 3.2.0 build with the old TLS configuration, with the aim
to try out Wolf SSL stack.
But while the config check passed, the server does not start with the old
configuration:
loadmodule “tls_mgm.so"
loadmodule “tls_wolfssl.so"
modparam("tls_mgm", "client_tls_domain_avp"
