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

Enforcing tombstones instead of deleting documents #19

Closed
2 tasks
benlongstaff opened this issue Aug 29, 2021 · 1 comment
Closed
2 tasks

Enforcing tombstones instead of deleting documents #19

benlongstaff opened this issue Aug 29, 2021 · 1 comment
Assignees
Labels
architecture bug Something isn't working
Milestone

Comments

@benlongstaff
Copy link

benlongstaff commented Aug 29, 2021

From the confidential storage working group discussion and spec

"Delete Resource (Document or Stream): Deletes the encrypted resource (note that a tombstone object should remain behind for replication purposes)."

  • Verify how tombstones is currently enforced.
  • Check that the database access permissions don't allow users / applications to delete documents
@tahpot tahpot self-assigned this Aug 30, 2021
@tahpot tahpot added architecture bug Something isn't working labels Aug 30, 2021
@tahpot tahpot added this to the MVP Release milestone Aug 30, 2021
@tahpot
Copy link
Contributor

tahpot commented Nov 16, 2022

CouchDb uses _deleted property, this ensures replication of deletions occurs across nodes. No action required.

Database owners can complete whole databases, but not hard delete individual docs.

@tahpot tahpot closed this as completed Nov 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants