search

pmq20 / ruby-packer

Packing your Ruby application into a single executable.
MIT License
1.56k stars 99 forks source link

ruby-packer fails with SSL error #141

Open d4rky-pl opened 3 years ago

d4rky-pl commented 3 years ago

When trying to build the application with latest ruby-packer, it fails on running the bundle install step with Could not verify the SSL certificate.

This happens both locally and on CI.

-> CI=true PATH=/var/folders/kc/w3zg_rmd6vnd_5w22fw154yh0000gn/T/rubyc/ruby_install/bin:/__enclose_io_memfs__/lib/ruby/gems/2.7.0/bin:/Users/matyas/.asdf/shims:/usr/local/opt/asdf/bin:/Users/matyas/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Users/matyas/.ht/bin ENCLOSE_IO_USE_ORIGINAL_RUBY=true ENCLOSE_IO_RUBYC_1ST_PASS=true ENCLOSE_IO_RUBYC_2ND_PASS='' /var/folders/kc/w3zg_rmd6vnd_5w22fw154yh0000gn/T/rubyc/ruby_install/bin/bundle install
Fetching source index from https://rubygems.org/

Retrying fetcher due to error (2/4): Bundler::Fetcher::CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.
There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.

Retrying fetcher due to error (3/4): Bundler::Fetcher::CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.
There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.

Retrying fetcher due to error (4/4): Bundler::Fetcher::CertificateFailureError Could not verify the SSL certificate for https://rubygems.org/.
There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'.

Could not verify the SSL certificate for https://rubygems.org/.
There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA
certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect
without using SSL, edit your Gemfile sources and change 'https' to 'http'.
Failed running [{"CI"=>"true", "PATH"=>"/var/folders/kc/w3zg_rmd6vnd_5w22fw154yh0000gn/T/rubyc/ruby_install/bin:/__enclose_io_memfs__/lib/ruby/gems/2.7.0/bin:/Users/matyas/.asdf/shims:/usr/local/opt/asdf/bin:/Users/matyas/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Users/matyas/.ht/bin", "ENCLOSE_IO_USE_ORIGINAL_RUBY"=>"true", "ENCLOSE_IO_RUBYC_1ST_PASS"=>"true", "ENCLOSE_IO_RUBYC_2ND_PASS"=>nil}, "/var/folders/kc/w3zg_rmd6vnd_5w22fw154yh0000gn/T/rubyc/ruby_install/bin/bundle", "install"]

It seems that RubyGems have been messing with their certificates (rubygems/rubygems/pull/4105, rubygems/rubygems/pull/4100, rubygems/rubygems/issues/4099) which may be causing this isssue

64kramsystem commented 3 years ago

@d4rky-pl Closed by #154.