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.

Sign up for GitHub

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

Jump to bottom

Disable 'trusted' in favor of setting the repo key #3

Open
rhass-r7 opened this issue Nov 4, 2015 · 1 comment
Open

Disable 'trusted' in favor of setting the repo key #3

rhass-r7 opened this issue Nov 4, 2015 · 1 comment
Labels
Status: Good First Issue An issue ready for a new contributor. Type: Enhancement Adds new functionality.

Comments

@rhass-r7
Copy link

rhass-r7 commented Nov 4, 2015

Rather than using trusted, we should use key node['apt-chef']['gpg']. This ensures the package and repo signatures are respected. If for some reason this doesn't bode for Chef Software internally, it should default to using signed repos and packages with optional attribute to force trusted instead.
@rhass-r7 rhass-r7 changed the title Disable 'trusted' on debian in favor of setting the repo key Disable 'trusted' in favor of setting the repo key Nov 4, 2015
@tas50 tas50 added the Type: Enhancement Adds new functionality. label Dec 22, 2016
@tas50
Copy link
Contributor

tas50 commented Sep 9, 2017

I’m adding the Type: Jump In GitHub label to this issue. This is a great issue for someone to get their feet wet with and we’d love a PR to resolves the issue.

@tas50 tas50 added Status: Good First Issue An issue ready for a new contributor. and removed Help: Good First Issue labels Jan 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: Good First Issue An issue ready for a new contributor. Type: Enhancement Adds new functionality.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tas50 @rhass-r7