-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible SDK 2.2.1 HTTP Module Regression #2538
Comments
0x7200 is |
I can only build using |
The test was repeated using the srv = tls.createConnection()
srv:connect(443,"149.154.167.220")
srv:on("connection", function(sck, c)
print("connected")
end) The debug information seems to indicate the same problem: client handshake start.
client handshake failed!
Reason:[-0x7200]
pm open,type:2 0 |
Could the returned message length be exceeding the maximum value as it appears to happen only when connecting to certain servers ? |
Ok, @marcelstoer, my time has come, I am giving your Docker NodeMCU build a try in order to get more SSL debugging data. I am struggling to find the tls.setDebug switch to enable the generation debugging information before building. Please help. Hopefully this will shed more information on the |
Did you check |
Thanks, I will change |
@djphoenix @nwf I can now build image using docker, struggling to find the debug switches in mbedtls to provide SSL debuging info. Any suggestions I can try ? |
If I recall correctly:
|
The mbedTLS needs to be compiled with debug support. That is the switch I need to find. I have the following options in |
Ok, it is solved. |
I'm glad there's an issue reference in the config file pointing at hints why we came up with that magic number. I think it's safe to assume that over time we'll only ever have to increase that buffer size as certificates and cipher suites evolve. |
@marcelstoer I will reduce the size further to find the minimum I need for telegram. Larger sizes cause low memory panic. Thanks for your docker facility, i am now proficient. Next is to try the LFS route. |
Hopefully as ECC cryptography slowly trickles into pervasive support, we won't need such huge fragments, because we won't be carting around RSA public keys. But LFS does relieve some of the pressure against big SSL buffers. |
Expected behavior
I am trying to connect to the Telegram API, "api.telegram.org" as was successfully reported by @FrankX0 in #1707 after the SDK 2.2.0 update as reported in #2269.
The following behavior indicating a successful client handshake is expected:
Actual behavior
The actual behavior indicating a handshake failure is as follows:
Test code
NodeMCU version
Hardware
NodeMCU devkit v2
The text was updated successfully, but these errors were encountered: