Could not validate SSL request (error -40)

[Student007]

Hi,
using Tessel and RFID-Modul I get this error also while using no ssl:
Could not validate SSL request (error -40)

Frijol/rfid-process-tracker#1

[Student007]

do I have to use a different url without ssl ? (I didn't find one)

[josephwegner]

@Student007 My best guess here is that this is related to us removing SSLv3 support. The POODLE vulnerabilities were announced in October, which forced us (and most of the rest of the internet) to stop supporting SSLv3 because it's not secure.

It looks like you can ask Tessel which version of Node you're running. TLS became the default protocol in Node in 0.10.33 - if you're using anything less than that, you might have troubles.

I also found one article that suggested completely restarting your Tessel - I have no idea why that would help, but one user reported that fixing his SSL issues.

One last thing - the rfid-process-tracker project uses keen.io, which is our old deprecated Node tracking library. That is not longer supported, and we strongly suggest that you migrate to keen-js, which is a CommonJS module for both web and server uses.

[dustinlarimer]

@Student007 also check out this quick overview of the key differences to be aware of when switching from our old Node SDK: https://github.com/keenlabs/KeenClient-Node#deprecation-notice

[Student007]

I try to use keen-js by protocol: "http" what should nullify the problem with tls on Tessel. But it hangs by calling
client.addEvent("purchases", purchaseEvent, function(err, res){...}
Is there a debugging mode for keen-js ?
You can see my code here
https://forums.tessel.io/t/could-not-validate-ssl-request-error-40/1727/7

[Student007]

solved
It is a transcompiler problem causes from JS2Lua ... solution is to rewrite the keen-js lib by removing/commenting all ssl/tls stuff.
(this also was the reason I couldn't see the debugging output of keen-js ... it simple freezed)

[dustinlarimer]

@Student007 can you elaborate on that a bit more? Anything we can do on our end?

[Student007]

I would say, your shouldn't do something. Your code is well done. If your want to provide support for transcompiler in general it would be interesting to put all ssl into a separate module instead of a lot of if ssl ... else and that things. But as I said, it isn't necessary - your code is well done :-) ... you can close this issue.

[dustinlarimer]

Cool, thanks for helping us understand this issue better @Student007 👍

[gracekoerber]

Any chance you could post the rewritten keen-js lib? I'm running into this same issue and would be very grateful for the help. Thanks!

[dustinlarimer]

@gracekoerber you can find previous releases here: https://github.com/keen/keen-js/releases, however this seems to be a deeper issue than our library can address. Check @josephwegner's comment above (#269 (comment)).. do you think this is a probable cause?

The browser build has undergone lots of changes over this past year, but the node build is essentially the same as it's always been, leaning on superagent for HTTP requests.

We're still researching this on our end, so any other clues you can send our way would be most helpful :)