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

feat: add policy to relevant key-based functions #78

Closed
wants to merge 1 commit into from

Conversation

rjzak
Copy link
Contributor

@rjzak rjzak commented Sep 22, 2022

Is this about that you had in mind @npmccallum, @jedisct1?

Addresses #58.

Signed-off-by: Richard Zak richard@profian.com

Signed-off-by: Richard Zak <richard@profian.com>
@jedisct1 jedisct1 changed the title feat: add policy to relavent key-based functions feat: add policy to relevent key-based functions Sep 22, 2022
@jedisct1 jedisct1 changed the title feat: add policy to relevent key-based functions feat: add policy to relevant key-based functions Sep 22, 2022
$policy_invalid

;;; Not allowed by policy
$policy_unallowed
Copy link
Member

Choose a reason for hiding this comment

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

That seems to be redundant with $prohibited_operation

@jedisct1
Copy link
Member

Not sure that this is it.

In #58, there's a set of functions that don't inherit any existing handle. So we can't get back to the global context.

A context (or "policy") should be added to them.

This is a different thing than the get_*_metadata() function that we would add to public, secret and key pairs.

@jedisct1 jedisct1 closed this Sep 1, 2023
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.

2 participants