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

Jump to bottom

Vault structure not properly initialized during vault creation #9816

Closed
cyberduck opened this issue Jan 20, 2017 · 1 comment
Closed

Vault structure not properly initialized during vault creation #9816

cyberduck opened this issue Jan 20, 2017 · 1 comment
Assignees
@dkocher
Labels
bug cryptomator Cryptomator Vault fixed
Milestone
5.3.4

Comments

@cyberduck
Copy link
Collaborator

f76c45b created the issue

When I create a vault on a WebDAV backend, this is what happens:

MKCOL foo - 201
PUT foo/masterkey.cryptomator - 201

Note that neither the "d" directory nor anything encrypted inside it gets created.

When I want to unlock the newly created vault, the aforementioned directories cannot be found:

PROPFIND foo/ - 207
GET foo/masterkey.cryptomator - 200
PROPFIND d/PU/ILTCZ2TTFODHEDSNBJ5SJZESLVXJIC/ - 404
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Add test in 51ce52e. Fix in 856c02b.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug cryptomator Cryptomator Vault fixed
Projects
None yet
Milestone
5.3.4
Development

No branches or pull requests
2 participants
@dkocher @cyberduck