What you describe is not possible - it cannot have happened. There is nothing in the Profile related to any password.
| Edit: But see post below where a scenario not involving the User Profile could allow it to happen |
See
Re: Unable to open p/word protected file anymore for a description of how passwords work and you will appreciate why it could not have happened as you describe.
Basically you decide to encrypt a file with, say,
zebra, as your password.
When you save with a password, AOO generates some random numbers which are stored in manifest.xml in the .ods file. AOO hashes these numbers with your
zebra to produce the final_password, which will look something like sk8"<¬*5dT£oH^%*~ ... etc, but which is not stored anywhere. Hence, even if you use
zebra for all your password protected files, every file will actually be encrypted with different final_password, and a different final_password will be used each time you save the same file.
This final_password is then hashed with the file to encrypt it and the encryption is stored.
When you open the file, AOO reads the stored numbers and hashes them with the
zebra you supply to recreate the final_password
sk8"<¬*5dT£oH^%*~ ... etc which is then used to decrypt the file.
The only things stored in the .ods file are the random numbers and the name of the method (Blowfish CFB) used to do the encryption. Neither
zebra nor
sk8"<¬*5dT£oH^%*~ ... etc are stored.
Resetting the profile deletes registrymodifications.xcu which holds the list of the last saved files so when you opened AOO, your list of recently saved files was empty. What may have happened is that you then navigated to the wrong file which was not password protected.