Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable21] Fix encrypted version to 0 when finding unencrypted file #28604

Merged
merged 2 commits into from
Aug 26, 2021

Conversation

backportbot-nextcloud[bot]
Copy link

@backportbot-nextcloud backportbot-nextcloud bot commented Aug 26, 2021

⚠️ This backport had conflicts and is incomplete ⚠️

backport of #28373

Whenever the command is run and a "legacy cipher" seems to be detected
when the legacy option is disabled, it's highly likely that the file is
actually unencrypted but the database contains a encrypted version
higher than 0 for some reason.

The command now detects this case and automatically sets the encrypted
version to 0 so that the file can be read again.

Signed-off-by: Vincent Petry <vincent@nextcloud.com>
This prevents side effects in tests by properly cleaning up
even with expected exceptions.

Signed-off-by: Vincent Petry <vincent@nextcloud.com>
@PVince81 PVince81 force-pushed the backport/28373/stable21 branch from 4691836 to 2032ca7 Compare August 26, 2021 12:25
@PVince81
Copy link
Member

conflict solved by backporting from the stable22 PR

@PVince81 PVince81 self-assigned this Aug 26, 2021
@PVince81 PVince81 added the 3. to review Waiting for reviews label Aug 26, 2021
@MichaIng MichaIng merged commit 3f15061 into stable21 Aug 26, 2021
@MichaIng MichaIng deleted the backport/28373/stable21 branch August 26, 2021 21:43
@blizzz blizzz mentioned this pull request Sep 23, 2021
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants