mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #1022] Cloning entry with attachment fails, "Attachment is not owned by the cipher" #718
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#718
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jcklie on GitHub (Jun 5, 2020).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/1022
Cloning entry with attachment fails
When I clone an entry with attachment, then I get the error message "Attachment is not owned by the cipher".
Your environment
db53511855Steps to reproduce
Websockets enabled ,smtp works
Expected behaviour
No error, thing gets cloned
Actual behaviour
Error toast "Attachment is not owned by the cipher", bitwarden_rs returns 400, empty entry is created
Relevant logs
Bitwarden log:
JS console:

Failed to load resource: the server responded with a status of 400 ()@BlackDex commented on GitHub (Jun 6, 2020):
i can confirm the error.
And, if i check the upstream project it doesn't clone attachments at all.
So i think we should match that for now, but this bug causes those items to not being cloned at all.