Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2020-08-17 | Revert "Use domain-separated ChaCha20 for in-memory key encryption" | luigi1111 | 1 | -34/+0 | |
This reverts commit 921dd8dde5d381052d0aa2936304a3541a230c55. | |||||
2020-08-09 | Use domain-separated ChaCha20 for in-memory key encryption | Sarang Noether | 1 | -0/+34 | |
2020-05-06 | Update copyright year to 2020 | SomaticFanatic | 1 | -1/+1 | |
Update copyright year to 2020 | |||||
2019-03-05 | Update 2019 copyright | binaryFate | 1 | -1/+1 | |
2018-08-16 | store secret keys encrypted where possible | moneromooo-monero | 1 | -0/+71 | |
The secret spend key is kept encrypted in memory, and decrypted on the fly when needed. Both spend and view secret keys are kept encrypted in a JSON field in the keys file. This avoids leaving the keys in memory due to being manipulated by the JSON I/O API. |