-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Code-signing Node.js add-ons on Windows #1723
Comments
Why do you unpack node files? It works in the asar. |
Feature will be implemented in several days. |
Oh, I didn't know this was possible! Thanks a lot for the advice! |
Turns out add-ons are loaded just fine from the asar now. See: electron-userland/electron-builder#1723 Change-Type: patch Signed-off-by: Juan Cruz Viotti <[email protected]>
Yes — my sample app has 2 native deps and it works. To be check — is electron unpack it on the fly or not. Anyway — trust electron-builder. Do not disable smart unpack without reason and corresponding issue in th electron-builder project :) |
When even one file is unpacked, the whole module cannot be packed into asar. So, you should unpack only when it is really required. |
See #1738. Looks like |
Turns out add-ons are loaded just fine from the asar now. See: electron-userland/electron-builder#1723 Change-Type: patch Signed-off-by: Juan Cruz Viotti <[email protected]>
Turns out add-ons are loaded just fine from the asar now. See: electron-userland/electron-builder#1723 Change-Type: patch Signed-off-by: Juan Cruz Viotti <[email protected]>
What are your thoughts on code-signing
*.node
files on Windows?See balena-io/etcher#1519. This is not the first time we encounter an anti-virus software that detects a
*.node
file as malicious. We've been manually asking these companies to whitelist such files, however code-signing could solve the problem entirely.I tried manually code-signing add-ons with
signtool sign
and they load fine.The text was updated successfully, but these errors were encountered: