1 Reply by luanxbach

(7 replies, posted in wolfSSL)

chrisc wrote:

Hi luanxbach,

It looks like "dl-media.integration.viber.com:443" requires SNI (Server Name Indication) to be used.  You can compile wolfSSL with SNI support using the --enable-sni configure option.  After adding that, you can connect using the example client by doing:

./examples/client/client -h dl-media.integration.viber.com -p 443 -d -g -S dl-media.integration.viber.com

Best Regards,
Chris

Thank you, may I ask how did you find that info ?

Go to forum: wolfSSL

2 Reply by luanxbach

(7 replies, posted in wolfSSL)

chrisc wrote:

Hi Semih,

Can you try enabling the "supported curves" extension when compiling wolfSSL?  We recently noticed that this is required to connect to some implementations using an ECC based cipher suite.

You can enable this using the "--enable-supportedcurves" ./configure option, ie:

./configure --enable-supportedcurves

Thanks,
Chris

Hi,

I'm getting very similar problem with dl-media.integration.viber.com. I've built wolfSSL with the following options:

./configure --enable-opensslextra --enable-ecc --enable-psk --enable-aesccm --enable-supportedcurves --enable-curve25519

But still got the -313 error:

./examples/client/client -h dl-media.integration.viber.com -p 443 -d -g -x
err = -313, revcd alert fatal error
wolfSSL error: wolfSSL_connect failed

Does anyone have any idea as to what am I missing ?

Thanks.

Go to forum: wolfSSL