Hello Kaleb J. Himes,

Thank you for your answer. Unfortunately, I can not agree with the results of your investigation.

Regarding i0.wp.com:

When you connect using TLS 1.2 then there is no TLS error, and you can get HTTP response as follow:

LD_LIBRARY_PATH=/mnt/raw/e2ibuildenv/wolfssl/out/i686/lib/ ./examples/client/.libs/client -S i0.wp.com -h i0.wp.com  -p 443 -d -x -C -g -i -v 3
Session Ticket CB: ticketSz = 192, ctx = initial session
peer's cert info:
 issuer : /C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certs.godaddy.com/repository//CN=Go Daddy Secure Certificate Authority - G2
 subject: /OU=Domain Control Validated/CN=*.wp.com
 altname = wp.com
 altname = *.wp.com
 serial number:68:86:4a:83:77:1a:bb:7d 
SSL version is TLSv1.2
SSL cipher suite is TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
SSL curve name is X25519
Client Random : F73F976937698B8DF04965E6B80D5AA158A4938A28B1153D881AA138E63BA8EB
SSL connect ok, sending GET...
HTTP/1.1 403 Forbidden
Server: nginx
Date: Tue, 11 Dec 2018 04:56:07 GMT
Con
tent-Type: text/html
Content-Length: 37
Connection: close

Direct IP/Hostna

Generally the problem is because you can NOT get HTTP response from i0.wp.com using  -v d, but you can when you manually force -v 3

Could you please take, a look once again on i0.wp.com host? In the browser, yes you got the message:

but this HTTP response and this is expected, there is NO SSL error.

With WolfSSL and option -v d or -v 4 ( when TLS 1.3 is used) it fails with:
SSL_read reply error -425, The security parameter is invalid
this is SSL error.

you will be able to get HTTP response also using WolfSSL when you force TLS 1.2, but in this case you must do this manually.

Regarding your question. Please find my answer in the following post:
https://www.wolfssl.com/forums/post4111.html#p4111

Thank you,
SamSam

Hello,

I used head. The information about this was in the first post:

Regards,
SSS

Hello,

Yes it works. Thank you very much.
However I had two compilation errors:

The first one was easy to fix by changing variable name from "min" to "mins".
The second one I simple commented. But as I understand there is problem with time_t overflow.

What will be the proper fix?

Best Regards,
SSS

Hello Kaleb,

No I don't have any timelines. I am using wolfSSL as a TLS backed for PyCurl (Python curl wrapper).
The project is OpenSource plugin for Set-Top-Boxes with Engima2 software.

Here is the link to the repository of this project:
https://gitlab.com/iptvplayer-for-e2/iptvplayer-for-e2

Thank you very much for all information and fix.

Best Regards,
SamSam

@embhorn

Your question is strange because in the first post you can find these informations.

As you can see the problem is with commands:

./examples/client/client -h 217.118.168.60 -p 443 -d -x -C -g -i -v d

and

./examples/client/client -h 217.118.168.60 -p 443 -d -x -C -g -i -t

So, the problem is when wolfSSLv23_client_method_ex  is used or when method wolfSSL_CTX_UseSupportedCurve was called.
In such situation wwolfSSL does not send information about elliptic_curves extension and this is a problem.
I checked this using wireshark.

I already wrote this two times. So, your question is really strange. Did you read my posts?

Regards,
SamSam