MobileRead Forums - View Single Post - kindle touch 5.0.0 to kindle touch 5.1.0. Any reason I should not upgrade?

ixtab · 04-29-2012, 11:53 AM

Hi,

I can confirm that it does not work on my KT either. I tried poking around a bit to find out what is causing this (and why it would be different from previous versions).

First things first: I don't have a solution, only an explanation.

In the web browser source code, the error with internal code "net-ssl-certificate-failed" is handled, and displays the "Invalid certificate, do you still want to proceed?" dialog. Obviously, in previous firmware versions, this was also the error that was generated.

Not so on 5.1.0. In fact, we get a different error: "net-ssl-failed". Here's the relevant log entry:

Code:

120429:144136 wafapp[7722]: E com.lab126.browser:NetworkManager::requestFinishedCallback:HTTP failed: reason [6, SSL handshake failed]:

This is a much worse condition, because it indicates that the Kindle is unable to communicate with the other host at all. In fact, it won't even be able to retrieve the certificate for checking it. In a sense, this is as if the Kindle was trying to speak chinese with the server, but the server only understands flemish. Technically, the most common cause for such things is that the client and server cannot agree on a common protocol or cipher suite.

The message seems to originate from /usr/lib/libsoup-2.4.so.1.4.0, but I can't say much more than that.

Feel free to contact amazon with the above information. It may also be worthwile to contact your provider, because their servers aren't exactly in good shape either: https://www.ssllabs.com/ssltest/anal...mail.skynet.be

To conclude, there is probably nothing you can do about it at this time. Either Amazon, or Skynet, or both, need to fix something.

PS: The solution *may* be as simple as Skynet actually providing the entire certificate chain correctly ("Chain issues: Incomplete" in the abovementioned Server Test Report), but no guarantees.

04-29-2012, 11:53 AM	#16
ixtab (offline) Posts: 2,907 Karma: 6736094 Join Date: Dec 2011 Device: K3, K4, K5, KPW, KPW2	Hi, I can confirm that it does not work on my KT either. I tried poking around a bit to find out what is causing this (and why it would be different from previous versions). First things first: I don't have a solution, only an explanation. In the web browser source code, the error with internal code "net-ssl-certificate-failed" is handled, and displays the "Invalid certificate, do you still want to proceed?" dialog. Obviously, in previous firmware versions, this was also the error that was generated. Not so on 5.1.0. In fact, we get a different error: "net-ssl-failed". Here's the relevant log entry: Code: 120429:144136 wafapp[7722]: E com.lab126.browser:NetworkManager::requestFinishedCallback:HTTP failed: reason [6, SSL handshake failed]: This is a much worse condition, because it indicates that the Kindle is unable to communicate with the other host at all. In fact, it won't even be able to retrieve the certificate for checking it. In a sense, this is as if the Kindle was trying to speak chinese with the server, but the server only understands flemish. Technically, the most common cause for such things is that the client and server cannot agree on a common protocol or cipher suite. The message seems to originate from /usr/lib/libsoup-2.4.so.1.4.0, but I can't say much more than that. Feel free to contact amazon with the above information. It may also be worthwile to contact your provider, because their servers aren't exactly in good shape either: https://www.ssllabs.com/ssltest/anal...mail.skynet.be To conclude, there is probably nothing you can do about it at this time. Either Amazon, or Skynet, or both, need to fix something. PS: The solution may be as simple as Skynet actually providing the entire certificate chain correctly ("Chain issues: Incomplete" in the abovementioned Server Test Report), but no guarantees. Last edited by ixtab; 04-29-2012 at 11:56 AM.