4 ms·
> 1) We should absolutely work towards allowing developers to sign their JavaScript. I've already been working on this for my own projects. It might be somethi
by some_furry 7y ago
> 1) We should absolutely work towards allowing developers to sign their JavaScript.
I've already been working on this for my own projects. It might be something that can be generalized for all Electron projects.
https://github.com/soatok/libvalence https://github.com/soatok/libvalence
https://github.com/soatok/valence-updateserver https://github.com/soatok/valence-updateserver
https://github.com/soatok/valence-devtools https://github.com/soatok/valence-devtools
This uses Ed25519 signatures and an append-only cryptographic ledger to provide secure code delivery. The only piece it's currently missing is reproducible builds.
For greater context: https://defuse.ca/triangle-of-secure-code-delivery.htm https://defuse.ca/triangle-of-secure-code-delivery.htm
- cjbprime 7y agoI think you need OS codesigning integration for this threat model. Otherwise whatever special app runtime check code you add just gets removed by the malicious overwrite of your app code.
- some_furry 7y agoI'm just doing this for secure updates, so that malware doesn't get delivered through the update mechanism. For precedent, see https://core.trac.wordpress.org/ticket/39309 https://core.trac.wordpress.org/ticket/39309 It isn't meant to mitigate a compromised endpoint.