-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
[Bug]: OpenSSL v1 is a undocumented requirement - Makes Komac unusable on modern systems #558
Comments
The builds from the GitHub releases are built with cross which installs the latest OpenSSL beforehand. I'll have a look into why it's expecting OpenSSL v1. |
The issue is that cross' Docker images use Ubuntu 20.04 where @michidk could you possibly confirm that the Linux builds from the nightly release are linking against OpenSSL v3? |
Yep, seems good:
Thanks a lot for the quick fix! Do you have a rough estimate of when the next release will be published? |
Probably tomorrow - I want to add automatic publishing to crates.io then I'll release 2.2.1. |
Is there an existing issue for this?
What happened?
Release https://github.com/russellbanks/Komac/releases/tag/v2.2.0 mentions that it now requires OpenSSL to be installed.
This is not documented in the readme.
However, even after installing OpenSSL via apt-get on Ubuntu 22.04 any trying to run https://github.com/russellbanks/Komac/releases/download/v2.2.0/KomacPortable-linux-x64.tar.gz, I get:
This is because Ubuntu 22.04 comes with
OpenSSL 3.2.1 30 Jan 2024 (Library: OpenSSL 3.2.1 30 Jan 2024)
Seems like OpenSSL v1 is required for the builds from GitHub releases:
OpenSSL v1.1.1 reached it's end of life 11th September 2023 (https://www.openssl.org/blog/blog/2023/09/11/eol-111/index.html). So is this really something we should do?
Interestingly it works fine when installing with
cargo install
. In that case it seems to link to OpenSSL v3:Is there any guidance on how to get it to run on Ubuntu 22 with the builds from GitHub releases?
The text was updated successfully, but these errors were encountered: