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

Add security section on dynamic information. #89

Merged
merged 1 commit into from
Nov 3, 2017

Conversation

msporny
Copy link
Member

@msporny msporny commented Oct 24, 2017

Fixes #18.

@msporny msporny changed the title Add security section on dynamic information. Add security section on dynamic information. Fixes #18. Oct 25, 2017
@msporny msporny changed the title Add security section on dynamic information. Fixes #18. Add security section on dynamic information. Oct 25, 2017
expressed by the credential is valid create a burden on <a>holders</a> and
<a>verifiers</a>. It is therefore important to set validity periods for
credentials that are appropriate to the use case and the expected lifetime
for the information contained in the credential.
Copy link
Contributor

Choose a reason for hiding this comment

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

Isn't this in direct contradiction to the recommendation to use short-lived credentials?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, perhaps we need more specific recommendations or a sliding scale -- or just a note that "if credentials are too short-lived the drawbacks are X and if they are too long-lived the drawbacks are Y." Followed by: "Use technology T or policy P for use cases where you can't compromise on either."

Copy link
Member Author

Choose a reason for hiding this comment

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

Can we raise a new issue for this? I agree with both of you, but I feel like we need to refactor/merge multiple sections (that don't exist in the spec if we don't pull in this PR) based on this discussion.

@msporny msporny merged commit f0bc276 into gh-pages Nov 3, 2017
@msporny msporny deleted the msporny-security-dynamic branch November 30, 2017 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants