Skip to content
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.

chefdk msi is not signed; publisher couldn't be verified #154

Closed
josephrdsmith opened this issue Sep 9, 2014 · 5 comments
Closed

chefdk msi is not signed; publisher couldn't be verified #154

josephrdsmith opened this issue Sep 9, 2014 · 5 comments

Comments

@josephrdsmith
Copy link

Attempting to install

https://opscode-omnibus-packages.s3.amazonaws.com/windows/2008r2/x86_64/chefdk-windows-0.2.1-1.windows.msi

Throws security warnings that "Publisher of this program couldn't be verified."

@irvingpop
Copy link

👍 same for 0.2.2.

@lamont-granquist
Copy link
Contributor

That would have to be a bug in omnibus, paging @opscode/release-engineers

@adamedx
Copy link

adamedx commented Sep 18, 2014

It's not an omnibus bug, it's a missing feature. :) This is also true of chef-client msi for the last 3 years. This is currently in our kanban backlog. If you're interested, I can go into more detail on what's involved.

You can get past the warnings, but obviously that's not the right thing.

@irvingpop
Copy link

Is this a recent change? When I download an older build (ex: chef-client-11.8.0) I don't get the same warnings. The "This program is not commonly downloaded" message is weird also.

windows-warnings

Edit: scratch that, both are unsigned :)

@danielsdeleo
Copy link
Contributor

The package is now signed.

@chef-boneyard chef-boneyard locked and limited conversation to collaborators Feb 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

5 participants