You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lukewwww
changed the title
Drop-in upgrade & auto upgrade for the Windows version
Drop-in replacement & auto upgrade for the Windows version
Jun 7, 2024
lukewwww
changed the title
Drop-in replacement & auto upgrade for the Windows version
Drop-in replacement support for the binary packages
Jun 7, 2024
I think moving the private key to a separate file that doesn't exist in our released package will be enough.
It is better to give the private key file as much protection as possible.
To encrypt it with a passphrase provided by the user will be too much trouble, the user will have to enter the passphrase every time starting the node. It might be OK for the users who start the node manually on their local devices, it will not be possible to start the node automatically on system start.
Encrypt the private key file with a fixed private key written into a binary, every time the node starts, decrypt the private key using the binary. It is still possible to extract the private key from the binary, but it will not be worth it given that there are not much funds in the wallet under the hot/cold wallet architecture.
No description provided.
The text was updated successfully, but these errors were encountered: