you can improve fool proving by watching the db file for change and then uploading it
you can further improve it by checking if the uploaded file is the one which was there when you did download it last and only then upload your changed version
but yes, for many people that simple approach would be good enough by far I mean how often do you add new passwords?
Yeah, I thought about checking the md5 before wrapping and aborting the run if there was no change, but I like knowing that the process is still working and that nothing stupid happened to my cronfile at some point. Two instances of having a cronfile silently overwritten is two too many for one lifetime.
you can improve fool proving by watching the db file for change and then uploading it
you can further improve it by checking if the uploaded file is the one which was there when you did download it last and only then upload your changed version
but yes, for many people that simple approach would be good enough by far I mean how often do you add new passwords?