2015-02-22, 06:31
Hi;
I am connecting via SNIPROXY and it seems that the SSL connection is failing possibly due to the fact that the SSL connection is not including the servername in it's requests resulting in a handshake failure.
Would it be possible to enable SSI support in this addon ?
I can replicate the issue from the command line, the first request does not send the servername and fails:
The second attempt including the servername succeeds:
The error generated in the kodi.log file from netflixbmc shows a similar error so I suspect that the SSI servername is not beiong set in the requests ?
Thanks
I am connecting via SNIPROXY and it seems that the SSL connection is failing possibly due to the fact that the SSL connection is not including the servername in it's requests resulting in a handshake failure.
Would it be possible to enable SSI support in this addon ?
I can replicate the issue from the command line, the first request does not send the servername and fails:
Code:
# echo | openssl s_client -host www.netflix.com -port 443 -tls1
CONNECTED(00000003)
139746395104928:error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure:s3_pkt.c:1262:SSL alert number 40
139746395104928:error:1409E0E5:SSL routines:SSL3_WRITE_BYTES:ssl handshake failure:s3_pkt.c:598:
The second attempt including the servername succeeds:
Code:
# openssl s_client -servername netflix.com -connect netflix.com:443
CONNECTED(00000003)
depth=2 C = US, O = "VeriSign, Inc.", OU = VeriSign Trust Network, OU = "(c) 1999 VeriSign, Inc. - For authorized use only", CN = VeriSign Class 3 Public Primary Certification Authority - G3
The error generated in the kodi.log file from netflixbmc shows a similar error so I suspect that the SSI servername is not beiong set in the requests ?
Thanks