Skip to content
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

Closed
jviotti opened this issue Jun 21, 2017 · 6 comments
Closed

Code-signing Node.js add-ons on Windows #1723

jviotti opened this issue Jun 21, 2017 · 6 comments
Labels

Comments

@jviotti
Copy link
Member

jviotti commented Jun 21, 2017

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.

@develar
Copy link
Member

develar commented Jun 22, 2017

Why do you unpack node files? It works in the asar.

@develar
Copy link
Member

develar commented Jun 22, 2017

Feature will be implemented in several days.

@jviotti
Copy link
Member Author

jviotti commented Jun 22, 2017

Why do you unpack node files? It works in the asar.

Oh, I didn't know this was possible! Thanks a lot for the advice!

jviotti added a commit to balena-io/etcher that referenced this issue Jun 22, 2017
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]>
@develar
Copy link
Member

develar commented Jun 22, 2017

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 :)

@develar
Copy link
Member

develar commented Jun 22, 2017

When even one file is unpacked, the whole module cannot be packed into asar. So, you should unpack only when it is really required.

@jviotti
Copy link
Member Author

jviotti commented Jun 22, 2017

See #1738. Looks like electron-builder unpacks the whole lzma-native when smartUnpack is enabled.

jviotti added a commit to balena-io/etcher that referenced this issue Jun 23, 2017
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]>
jviotti added a commit to balena-io/etcher that referenced this issue Jun 23, 2017
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants