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

In-memory encryption of privkeys #74

Open
fluffypony opened this issue Aug 2, 2014 · 5 comments
Open

In-memory encryption of privkeys #74

fluffypony opened this issue Aug 2, 2014 · 5 comments

Comments

@fluffypony
Copy link
Contributor

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."

@ghost
Copy link

ghost commented Nov 10, 2016

@fluffypony has anyone taken this forward?

@fluffypony
Copy link
Contributor Author

@nanoakron no not yet

@dEBRUYNE-1
Copy link
Contributor

+enhancement

@moneromooo-monero
Copy link
Collaborator

Partially done with jroelofs' patches above, still some left to do though.

@stoffu
Copy link
Contributor

stoffu commented Feb 10, 2018

IIUIC the ringct code lumps the different kinds of data (pubkey/seckey/hash) into a single type rct::key, and thus the encryption for the secret key isn’t achieved yet.

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
Projects
None yet
Development

No branches or pull requests

5 participants