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

Allow access to secure configuration or API keys in Chocolatey package scripts #346

Open
2 tasks done
pauby opened this issue May 11, 2023 · 0 comments
Open
2 tasks done
Labels
Enhancement Enhancements are things that are improvements or features.

Comments

@pauby
Copy link
Member

pauby commented May 11, 2023

Checklist

  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.

This is taken from chocolatey/choco#3101

To get access to a repository that needs credentials, the Chocolatey package scripts may need access to encrypted values. In the case of chocolatey/choco#3101, this is API keys, but I can see this being useful for encrypted config values too.

Describe The Solution. Why is it needed?

Allows access to encrypted values in the Chocolatey package scripts.,

Additional Context

On the surface this seems like a good idea, however there are many things security-wise to consider. For example you could create a package that simply dumps on the API keys to the screen which isn't going to be good. So maybe you add a field that allows the key to be used in a package script, or you just use encrypted values etc.

Thought needs to be put in here, and it could end up that we can't do this.

Related Issues

@pauby pauby added the Enhancement Enhancements are things that are improvements or features. label May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Enhancements are things that are improvements or features.
Projects
None yet
Development

No branches or pull requests

1 participant