fix: Implement Backblaze bucket restoration on server recovery #324

Merged
NaiJi merged 5 commits from backblaze-fetch into master 2023-09-06 00:36:50 +03:00
Collaborator

Resolves issue 320.

Resolves issue [320](https://git.selfprivacy.org/SelfPrivacy/selfprivacy.org.app/issues/320).
NaiJi added the
Bug
Priority
Critical
Severity
High
labels 2023-09-05 20:44:09 +03:00
NaiJi self-assigned this 2023-09-05 20:44:09 +03:00
NaiJi added 1 commit 2023-09-05 20:44:10 +03:00
NaiJi requested review from inex 2023-09-05 20:44:15 +03:00
inex requested changes 2023-09-05 20:49:55 +03:00
@ -182,0 +206,4 @@
bucketId: rawBucket['bucketId'],
bucketName: rawBucket['bucketName'],
encryptionKey: configuration.encryptionKey,
applicationKeyId: credentials.keyId,

Won't be correct, this is the key ID for the application key, which is the subkey generated using the primary key entered by user during restoration

Won't be correct, this is the key ID for the *application* key, which is the subkey generated using the primary key entered by user during restoration
Poster
Collaborator

And what does it mean? Should I force it to '' as well?

And what does it mean? Should I force it to '' as well?

yes

yes
NaiJi marked this conversation as resolved
NaiJi added 2 commits 2023-09-05 21:03:50 +03:00
NaiJi requested review from inex 2023-09-05 21:04:30 +03:00
NaiJi added 1 commit 2023-09-05 21:20:37 +03:00
NaiJi added 1 commit 2023-09-05 22:14:29 +03:00
inex approved these changes 2023-09-05 22:57:38 +03:00
NaiJi merged commit 82dfdf04f9 into master 2023-09-06 00:36:50 +03:00
NaiJi deleted branch backblaze-fetch 2023-09-06 00:36:50 +03:00
Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: SelfPrivacy/selfprivacy.org.app#324
There is no content yet.