Closed jnweiger closed 2 years ago
Expected behaviour: The encryption machinery does not get confused when keys are not initialized. To be safe, enabling encryption should log out all users immediately.
On a fresh machine https://oc1091rc1-wopi-151-20220110.jw-qa.owncloud.works - enable encryption via admin UI runs into different errors:
occ encryption:disable; occ encryption:enable; occ encryption:select-encryption-type masterkey -y
I believe the original issue is also related to confusion between user key encryption and master key encryption. Most likely I had mixed using the admin-UI and using the command line.
Do you have an owncloud.log for this?
Outcome from developers: Tried to reproduce it 5 times, issue didn't pop up
Do you have an owncloud.log for this?
yes, attached. You can log into root@oc1091rc1-wopi-151-20220110.jw-qa.owncloud.works and look around yourself. I'll leave that machine alone for now.
Outcome from developers: Tried to reproduce it 5 times, issue didn't pop up
Confirmed. The issue does not appear when striclty following the steps in my initial post. Feel free to close here as invalid and followup in #39671
Seen in 10.9.1RC1 (with encryption 1.5.1 initially disabled)
The file already got truncated to 0 size:
After logout, login, the file is still in a broken state:
A total of 11 corrupt versions are saved. The 12th one can be restored and has actually the latest content. Phew.