Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't use openssl > 1.9 and openssl version is defaulting to 1.0.1 #132

Open
nicklevenson opened this issue Sep 1, 2023 · 0 comments
Open
Labels
bug Something isn't working

Comments

@nicklevenson
Copy link

Orb version: 2.1.0

What happened:

Our CI builds started failing at the bundle step because there stopped being an openssl link when bundling. We tried to manually install openssl before installing ruby eg sudo apt-get update && sudo apt-get install -y openssl which installs the latest openssl version 3.

When rvm was installed via the ruby/install step, we noticed theres a check in the orb that looks for an existing ssl version to use in the opts flags, but it only looks for versions within the 1 range. eg if ! openssl version | grep -q -E '1\\.[0-9]+\\.[0-9]+'. If the version is outside of that regex, it installs openssl 1.0.1 by default. This version (less than 1.1.1) causes issues with ssl certs when using sidekiq-pro (and assuming other gems) and prevents bundling from happening

Expected behavior:

I would hope the system would use any openssl version that was already installed on the machine, or at least default to using the latest 1 version instead of the oldest.

@nicklevenson nicklevenson added the bug Something isn't working label Sep 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant