Unsigned error while using gem

[johnnyramos]

Seems when using the gem on macOS Catalina, it resolved the following error.

/opt/chef/embedded/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require': dlopen(/opt/chef/embedded/lib/ruby/gems/2.6.0/gems/rugged-0.28.4.1/lib/rugged/rugged.bundle, 9): no suitable image found.  Did find: (LoadError)
	/opt/chef/embedded/lib/ruby/gems/2.6.0/gems/rugged-0.28.4.1/lib/rugged/rugged.bundle: code signature in (/opt/chef/embedded/lib/ruby/gems/2.6.0/gems/rugged-0.28.4.1/lib/rugged/rugged.bundle) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed. - /opt/chef/embedded/lib/ruby/gems/2.6.0/gems/rugged-0.28.4.1/lib/rugged/rugged.bundle

This is on a fresh install of macOS 10.15.3 and the product using the gem is using Ruby 2.6.0.

[carlosmn]

What's that error about? I haven't used macOS (let alone a recent version) in a long time. This project only provides source code, could we do anything here?

Are you using rugged directly? From the path it looks like you're using chef and it in turns happens to use rugged for something. As chef would be the ones providing rugged and presumably unsigned code to you, contacting them about it might yield results.

[johnnyramos]

Since the code can also run on a macOS operating system, Apple has made it more difficult to consume binaries/bundles and such without being signed by a developer.

We have other methods to continue using it but if macOS isn't a supported OS for this gem, then we can close this.

[wonderer007]

I having exactly same issue on Macbook M1. Any solution ?

[carlosmn]

It looks like the solution is for you to sign the code when you deploy it in your use-case. I've no idea what the restrictions or limits are there, or whether signing our compiled code for the user on rake compile is expected or a good idea.