Skip to content
This repository has been archived by the owner on Oct 17, 2022. It is now read-only.

rfc(per-doc-access): first draft #424

Closed
wants to merge 9 commits into from
Closed

rfc(per-doc-access): first draft #424

Changes from 1 commit
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
e5a54a2
rfc(per-doc-access): first draft
janl Jul 7, 2019
0e12884
fix: typos
janl Jul 7, 2019
1077dbc
feat: add extra notes about security issues
janl Jul 8, 2019
a08438f
fix: typo h/t @jaydoane
janl Jul 15, 2019
b1d6a59
fix typo
janl Jul 19, 2019
2b8f941
clarify
janl Jul 19, 2019
748828d
fix format
janl Jul 19, 2019
e52b3da
fix format
janl Jul 21, 2019
a0cfaea
allow distribution of design docs
janl Jul 21, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fix format
  • Loading branch information
@janl
janl committed Jul 21, 2019
commit e52b3dac0f4a919a7b3d736e047e316a26726ff5
4 changes: 3 additions & 1 deletion rfcs/010-per-document-access-control.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -163,7 +163,9 @@ An access-enabled database behaves like this:
* if compaction hasn’t run yet, they get access to all previous
revision bodies that still exist.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the _access field exist as revision-specific metadata? If it does, then with this implementation we're saying that the _access field on a given revision may not be accurate with respect to who can view this revision. That feels hard to reason about.

Perhaps we are imaging that applications may typically deal with this by creating a document copy with the altered _access?


* all conflicted versions will also be visible to the new user, unless there are conflicting usernames in conflict’s `_access` property.
* all conflicted versions will also be visible to the new user,
unless there are conflicting usernames in conflict’s `_access`
property.

* regardless of compaction, they get access to the full list of
revision ids for the document. Extremely crafty people could try
Expand Down