Add SecureBytes for secure memory wiping of seed data#6
Open
r2ckstardev wants to merge 1 commit into
Open
Conversation
Uses ctypes.memset to zero seed bytes from memory after use. Prevents key material from lingering in RAM on air-gapped devices.
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
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.
Summary
Adds
SecureByteswrapper that usesctypes.memsetto zero sensitive seed bytes and share data from memory after use.Why
After Codex32 shares reconstruct the master seed, raw bytes stay in Python memory until GC runs. On an air-gapped SeedSigner, that leaves private key material exposed in RAM.
Usage
Context manager for automatic cleanup, or call
.wipe()manually. No changes to existing code - additive only.