Closed LeonardLaszlo closed 6 years ago
@LeonardLaszlo I am not sure, FYI this arm build was experimental, we are not using this yet in our daily build, so I can't help you to debug run time error :(
Here I've found some additional information about the problem:
https://github.com/Microsoft/openssl/commit/68886be7e2cd395a759fcd41d2cede461b68843d https://trac.macports.org/ticket/38015?cversion=0&cnum_hist=10
EDIT:
I checked the problematic file https://github.com/nwjs/node/blob/nw23/deps/openssl/openssl/crypto/ec/ecp_oct.c
The invocation of EC_POINT_is_on_curve(group, point, ctx) <= 0
seems correct. However the OpenSSL library of the Node fork used for NW.JS seems not to be updated in the last 8 moths.
I suggest to update the version of Node / OpenSSL to the latest version.
Hello @LeonardLaszlo I experiencing this problem too, I tried different versions and have always the same issue. I tried to use the version 22 but it gives-me an error like you reference on the issue https://github.com/LeonardLaszlo/nw.js-armv7-binaries/issues/9
With this ported version https://github.com/jalbam/nwjs_rpi I don't have this problem but have others due to the old version its on it.
Any ideas? I really need to use nw with an Rpi3 Thank's.
Well we need some enthuziast developer, who is able to debug Chromium and it's dependencies. Unfortunately I cannot help with that...
@LeonardLaszlo I've "fixed" the openssl issue, by disabling openssl assembly files I am currently testing it on nw24 beta, will patch nw23 later, I'll update you once I am done
thank you!
Apply these 3 patches on top of original nwjs/chromium.src repository
Apply these 3 patches on top of original nwjs/nw.js repository
if you curious, this is the actual node.js openssl patch that "fix" the https connection problem https://github.com/jtg-gg/node-webkit/commit/27537f1b8563b805eec1b3e327296a824cdd5f79#diff-63fcc6b9d8ae5bba928e573d8340e3c3
Fixed with release: NW.js ARMv7 v0.24.5
There is a problem with the OpenSSL in ARMv7 builds. When I run something like:
I get the following error:
@jtg-gg Any idea what is wrong?