The parameters file fix-ssh-on-pi.ini_example was presumably named this way so nobody would accidentally commit a plain text password to source control. This change renames that file to just fix-ssh-on-pi.ini and expects an encrypted password to be put in there instead. This still prevents any reasonable user from committing plain passwords to source control, but it removes the extra step of having to copy the example file to a "real" one.
The readme has been extended with instructions on how to generate an encrypted password string (which leads to a shell escaped output string). This method also prevents plain passwords from ending up in anyone's shell history.
The parameters file
fix-ssh-on-pi.ini_example
was presumably named this way so nobody would accidentally commit a plain text password to source control. This change renames that file to justfix-ssh-on-pi.ini
and expects an encrypted password to be put in there instead. This still prevents any reasonable user from committing plain passwords to source control, but it removes the extra step of having to copy the example file to a "real" one.The readme has been extended with instructions on how to generate an encrypted password string (which leads to a shell escaped output string). This method also prevents plain passwords from ending up in anyone's shell history.