pwd.sh.safe can be edited and corrupted about pwd.sh HOT 4 CLOSED

Thanks for your input. I agree with you that backups are a good way to protect your data integrity.

However, on the off-chance someone failed to back up their passwords, a "game over" error could result from a bash one-liner: cd ~/pwd.sh && echo ":/" > pwd.sh.safe. I view this as a weakness in pwd.sh because such a crucial component can be corrupted so easily. My suggestion would be to change permissions using chmod, like so:

{START}
chmod +r+w pwd.sh.safe (Adds read and write permissions so pwd.sh can do its thing)
{OLD PWD.SH SCRIPT}
chmod -r-w pwd.sh.safe (Removes read and write permissions to thwart shenanigans)
{EXIT}

I've attached some logs from my terminal that show how changing permissions can hopefully make your program safer. Hope that helps!
demo.txt

from pwd.sh.

Please try the new beta release and let me know what you think:
https://github.com/drduh/pwd.sh/releases/tag/2.0b

from pwd.sh.

The only thing what helps against ransomware is external backup and backup of the backups which are stored externally…

The described problem is not a problem of pwd.sh but of your data integrity. You should generally think about this and organize a working backup plan for your data.

from pwd.sh.

Write protection and versioning/backups sound like great ideas. I'm already working on new features and will include your suggestions in an upcoming release. Thanks for sharing!

from pwd.sh.