-
Notifications
You must be signed in to change notification settings - Fork 22
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
OpenSSL issue #7
Comments
@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: microsoft/openssl@68886be EDIT: I checked the problematic file https://github.com/nwjs/node/blob/nw23/deps/openssl/openssl/crypto/ec/ecp_oct.c The invocation of 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 #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 |
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 |
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 |
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?
The text was updated successfully, but these errors were encountered: