We likely have many users with short autogenerated passwords in their config files. These can actually be detected and automatically fixed, without user action.
We will want to do something like this:
When SD starts and hushd is NOT yet running (i.e. users that rely on SD autostarting the full node)
Find the config and look at the length of rpcpassword
If rpcpassword is at least 10 chars, do nothing
If rpcpassword is < 10 chars, make a backup of the config file
Generate a new password with the new randomPassword() function
Delete the line containing rpcpassword and add a new line containing the new password
Then allow SD to continue the process of autostarting the full node
We likely have many users with short autogenerated passwords in their config files. These can actually be detected and automatically fixed, without user action.
We will want to do something like this:
* When SD starts and hushd is NOT yet running (i.e. users that rely on SD autostarting the full node)
* Find the config and look at the length of `rpcpassword`
* If `rpcpassword` is at least 10 chars, do nothing
* If `rpcpassword` is < 10 chars, make a backup of the config file
* Generate a new password with the new `randomPassword()` function
* Delete the line containing `rpcpassword` and add a new line containing the new password
* Then allow SD to continue the process of autostarting the full node
We likely have many users with short autogenerated passwords in their config files. These can actually be detected and automatically fixed, without user action.
We will want to do something like this:
rpcpasswordrpcpasswordis at least 10 chars, do nothingrpcpasswordis < 10 chars, make a backup of the config filerandomPassword()functionrpcpasswordand add a new line containing the new passwordJust to clarify, since SDX never existed when this bug existed, this issue only affects SD (HUSH) users