feat(config): add key migration and file-based key storage#4
Open
matteotrubini wants to merge 1 commit intoCodeToTime:mainfrom
Open
feat(config): add key migration and file-based key storage#4matteotrubini wants to merge 1 commit intoCodeToTime:mainfrom
matteotrubini wants to merge 1 commit intoCodeToTime:mainfrom
Conversation
Implements secure key management for encrypted preferences: - Adds file-based key storage in ~/.eppclient/local.key instead of hardcoded key - Automatically migrates old preferences to new key on first access - Generates unique encryption key per installation for improved security BREAKING CHANGE: Encrypted preferences from previous versions will be re-encrypted with the new key on first access. The old hardcoded key is retained only for reading during migration.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements secure key management for encrypted preferences:
BREAKING CHANGE: Encrypted preferences from previous versions will be re-encrypted with the new key on first access. The old hardcoded key is retained only for reading during migration.