-
Notifications
You must be signed in to change notification settings - Fork 11
Refactor note about controller property usage. #87
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
Conversation
are authorized to perform certain actions associated with the resource with | ||
which it is associated. To ensure explicit security guarantees, the | ||
[=controller=] of a [=verification method=] cannot be inferred from the | ||
[=controller document=]. It is necessary to explicitly express the identifier of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this statement asserting that if a verification method does not have a controller property one cannot assume the controller is the controller of the document itself? that does not seem correct
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rather, I think it says that the lack of a controller property, and any assumption that might be made stemming from this lack, is an inherent security issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is far less confusing what the text that it replaces.
a57d66c
to
bce3f0d
Compare
Editorial, multiple reviews, changes requested and made, no objections, merging. |
This PR is an attempt to address issue #57 by refactoring the note about how the controller property is used.
Preview | Diff