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

Anonymous and/or client gateway closures #125

Open
jcnelson opened this issue Feb 10, 2015 · 2 comments
Open

Anonymous and/or client gateway closures #125

jcnelson opened this issue Feb 10, 2015 · 2 comments

Comments

@jcnelson
Copy link
Member

Allow anonymous or client gateways to have closures.

  • add an MS handler for getting the "default" closure (i.e. by volume)
  • add a way for syntool to set one for a volume
@jcnelson
Copy link
Member Author

jcnelson commented Aug 5, 2015

Will be fixed by making drivers content-addressable, and separately downloadable. The code to verify will check to see if the gateway is anonymous, and if so, check for the volume owner's signature.

@jcnelson
Copy link
Member Author

jcnelson commented Oct 6, 2015

Drivers are content-addressable in my own tree, and driver signatures are checked against the volume owner for anonymous gateways.. Just need to evaluate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant