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

Release v3 #72

Merged
merged 28 commits into from
Apr 19, 2024
Merged

Release v3 #72

merged 28 commits into from
Apr 19, 2024

Conversation

sleeyax
Copy link
Owner

@sleeyax sleeyax commented Apr 19, 2024

This is a major release which removes patches that no longer work and simplifies the encryption process. Going forward, asarmor will focus more on the encryption aspect.

This patch no longer works because the latest version of `@electron/asar` now skips files with an invalid offset or size.
Previously, the bloat patch would still partially leak actual file contents. This commit fixes that so it only writes nonsense that is useless to an attacker.
The key is unique per asarmor installation and should be the exact same from both the JS and C/C++ side. To prevent user error we should not expose the `key` property to the user in the library API or CLI. Instead, we always use the randomly generated key. If a user wishes to rotate the key, they can do so by manually reinstalling `asarmor` or by deleting the `key.txt` file and regenerating it using a script.
@sleeyax sleeyax merged commit b299a1a into master Apr 19, 2024
3 checks passed
@sleeyax sleeyax deleted the v3 branch April 19, 2024 17:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant