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

Include the extension policies into STR #115

Open
vqhuy opened this issue Nov 1, 2016 · 3 comments
Open

Include the extension policies into STR #115

vqhuy opened this issue Nov 1, 2016 · 3 comments

Comments

@vqhuy
Copy link
Member

vqhuy commented Nov 1, 2016

Does the directory need to include its extension policies in the STR so the client can check that policies against its current pining policies?
E.g., the Policies struct could have a field SignedPromiseType: string to indicate what kind of promise the directory is using (e.g., "TemporaryBinding" or "None"). This check could be used to detect misconfig from the client-side (say, when the directory's useTBs is true but the client's useTBs is false).

@arlolra
Copy link
Member

arlolra commented Nov 1, 2016

Yes

@masomel
Copy link
Member

masomel commented Nov 1, 2016

I agree, the STR Policies are the right place to indicate the server's extension settings.

This check could be used to detect misconfig from the client-side

Is the idea that the client would simply change its configuration if it doesn't match the server's policy?

@vqhuy
Copy link
Member Author

vqhuy commented Nov 2, 2016

Is the idea that the client would simply change its configuration if it doesn't match the server's policy?

Maybe we should notice to users and let them open new issue instead?

@vqhuy vqhuy added this to the 0.2.0 milestone Nov 2, 2016
@masomel masomel modified the milestones: 0.2.0, 0.2.2 Aug 3, 2017
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

3 participants