-
Notifications
You must be signed in to change notification settings - Fork 17
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
Privacy Considerations: Editorial Improvements #286
Conversation
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.
See comment above.
This does not make the comment any less useful, I would rather keep this. Co-authored-by: Steve Lasker <[email protected]>
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.
Lets not assert properties of verifiable data structures beyond append only and inclusion proofs
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.
Orie's suggestion makes sense
Co-authored-by: Orie Steele <[email protected]> Co-authored-by: Henk Birkholz <[email protected]> Co-authored-by: Orie Steele <[email protected]>
Co-authored-by: Orie Steele <[email protected]> Co-authored-by: Henk Birkholz <[email protected]> Co-authored-by: Orie Steele <[email protected]>
Co-authored-by: Orie Steele <[email protected]> Co-authored-by: Henk Birkholz <[email protected]> Co-authored-by: Orie Steele <[email protected]>
Co-authored-by: Orie Steele <[email protected]> Co-authored-by: Henk Birkholz <[email protected]> Co-authored-by: Orie Steele <[email protected]>
Co-authored-by: Orie Steele <[email protected]> Co-authored-by: Henk Birkholz <[email protected]> Co-authored-by: Orie Steele <[email protected]>
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.
Suggestion to leave this section and close.
Co-authored-by: Henk Birkholz <[email protected]> Co-authored-by: Hannes Tschofenig <[email protected]>
Co-authored-by: Henk Birkholz <[email protected]> Co-authored-by: Hannes Tschofenig <[email protected]>
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.
Lets merge #294 first, and then address conflicts and see if anything remains
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.
I see this change as constructive, I asked Steve for clarification on his comments too.
Co-authored-by: Yogesh Deshpande <[email protected]>
this is okay, but maybe other parts in the pr will keep it from being merged Co-authored-by: Hannes Tschofenig <[email protected]>
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.
Suggest we incorporate Option 1 suggestion from Steve!
@OR13, @henkbirkholz, PTAL at the latest if they resolve your requested changes. |
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.
Changes as of cdd13a4 improve the previous text.
LGTM
Transparency Services MAY support anonymous access. | ||
Issuers SHOULD ensure Signed Statements submitted to public access services are acceptable for public disclosure. | ||
In this case, Signed Statements MUST NOT carry confidential information. | ||
Once a Signed Statement is inserted into the Append-only Log maintained by a Transparency Service, it cannot be removed from the Log. |
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 a strange way to say that Log integrity is tamper protected.
Co-authored-by: Orie Steele <[email protected]>
Transparency Services MAY support anonymous access. | ||
Issuers SHOULD ensure Signed Statements submitted to public access services are acceptable for public disclosure. | ||
Publicly accessible Signed Statements MUST NOT carry confidential information. | ||
Once a Signed Statement is inserted into the Append-only Log maintained by a Transparency Service, it cannot be removed from the Log. |
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.
Once a Signed Statement is inserted into the Append-only Log maintained by a Transparency Service, it cannot be removed from the Log. | |
Once a Signed Statement is registered it cannot be removed from the Log. |
Optional brevity
No description provided.