-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
In-memory encryption of privkeys #74
Labels
Comments
@fluffypony has anyone taken this forward? |
@nanoakron no not yet |
+enhancement |
Partially done with jroelofs' patches above, still some left to do though. |
IIUIC the ringct code lumps the different kinds of data (pubkey/seckey/hash) into a single type |
stoffu
pushed a commit
to stoffu/monero
that referenced
this issue
Nov 5, 2018
Replace some Monero port numbers with Aeon's
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To prevent them ever being paged to disk unencrypted, they should be encrypted in-memory until they are needed.
Reference in terms of how Bitcoin does it (we don't have to follow their model 1:1) - https://bitcointalk.org/index.php?topic=8728.0
per @gmaxwell - "best effort mlocked, zeroized when the wallet is no longer unlocked or when freed."
The text was updated successfully, but these errors were encountered: