Dan DeLeo

Appears to be an upstream issue, will keep this ticket here to track getting the fix in once it becomes available.

FYI, when authenticating API requests using signed header auth, Supermarket fetches the key via oc-id, but then it verifies the request on its own, here: https://github.com/chef/supermarket/blob/0f0ee705c396578f3be0cebd9cc0bea6a5fb584f/app/controllers/api/v1/cookbook_uploads_controller.rb#L158-L202 I'm not sure exactly...

The code I referenced didn't change, so I'm pretty sure the behavior will be the same (unless of course I'm wrong about that section of code being the important thing)....

BTW, here's the erchef code for validating requests. When there are multiple keys, it takes the path that goes to `validate_sigs` (plural). https://github.com/chef/chef_authn/blob/defae88f9ea9f9875b1148947bbdf38c867c8ec7/src/chef_authn.erl#L561-L662

Does it work if you give the `-c CONFIG_FILE` option? Trying to figure out if it's skipping the config file load if you don't pass the option explicitly.

Thanks for that, I wanted to make sure this wasn't the same thing as a different bug where the config file simply wasn't getting loaded. This seems to be an...

Yes, we are looking at whether Ruby 2.2 would fix it, or if we could build Ruby on Windows ourselves rather than relying on RubyInstaller/DevKit builds (this would allow us...

If you make a policyfile and upload it with `chef push` does that fail in the same way? Can you `knife cookbook upload` the same cookbook?

Also, what chef server are you using, and have you modified its SSL configuration?

Are you specifically seeing `SSL_read: cert already in hash table` ? If not, it may be a different issue.