-
Notifications
You must be signed in to change notification settings - Fork 170
OSX ruby executable has an invalid signature #258
Comments
Pretty sure this is a dup, but i think you've got better information and a fix, so the other issues should probably be hunted down and closed with a pointer to this one. Also paging in @opscode/release-engineers because this most likely is properly a bug against omnibus and needs a patch there. |
Retested this on ChefDK 0.5.15 - this is still an issue when using chef-zero and/or chef-provisioning which opens a port to listen on |
I take it back! The pop-up happens the first time, but not on subsequent runs which is a considerable improvement. Considering this closed. |
seems like this happening at all is still bad tho? |
It's a little bad, but not as bad as before. To go into more detail:
Yes it would be better if the binaries were signed (that's tracked in chef/omnibus#431 ) but the specific issue reported here (invalid signatures) is gone and the inconvenience is massively reduced. |
Hm, this appears to have returned in ChefDK 0.16.28
|
I'm seeing "code object is not signed at all" again in both 1.1.16 and 1.2.20 closing again in favor of chef/omnibus#431 |
Using ChefDK 0.3.5 (and earlier versions) on OSX (tested with Yosemite) you'll frequently see the following pop-up message:
This happens because the signature is invalid:
I'm able to fix it using these instructions signing like so:
The text was updated successfully, but these errors were encountered: