Add Encryption Feature
See original GitHub issueFeature request:
Add the ability to encrypt the .asar
archive with one or more algorithms based on client-submitted hash/seed/salt. Conversely, also add the ability read the encrypted .asar
file by providing the hash/seed/salt.
This would slow down reading times, but for an added benefit for those wanting to keep their code safer. A quick Google search for .asar
and instructions to unpack will be the first result.
Issue Analytics
- State:
- Created 8 years ago
- Comments:28
Top Results From Across the Web
Learn about encrypted messages in Outlook.com
To send a message with encryption, choose one of the two options available under the Encrypt button: Encrypt or Encrypt and Prevent Forwarding....
Read more >Use end-to-end encryption in Messages - Google Support
Chat features in Messages turned on. Confirm your verification code. Your conversation is end-to-end encrypted with a secret key that only you and...
Read more >How to Enable Email Encryption on Outlook - Trend Micro
Encryption 101: How to Enable Email Encryption on Outlook · Click the File Tab. · Click Options. · Click Trust Center. · Under...
Read more >How to Encrypt Emails in Outlook and Office 365 - LazyAdmin
How to Encrypt Emails in Outlook and Office 365 ; Compose a new email in Outlook Online; Select Encrypt in the toolbar; Click...
Read more >Encrypted Forms and How to Use Them - Jotform
Are Forms and Submissions Secure Without the Encryption Feature ... As soon as you upload the public key, it is added to your...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
how about a solution where electron-packager handles the encryption of the asar file with a random key and only electron executable is able to read it?
or a unified encryption key unknown to users for all asar files. and the key would be included with electron itself (though this is less secure)
I believe the best thing to do is to not implement this feature