-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
remove libcrypto.so.1.1 dependency from the server #910
Comments
please install openssl 1.1 to make it available |
OK I did https://gist.github.com/joulgs/c8a85bb462f48ffc2044dd878ecaa786 and it's working SMP server v5.4.0.7 |
thank you! |
passes the tests for me - do you want to have it public? if so, you can simply remove password, in which case contacts of users can see it, and possibly, use (although we didn't yet make it convenient). If not, you should not share password publicly ;) - it's the part of the address after ":", your contacts won't see it via the app. |
Yep removed password , it can be used in public . see also https://smp.anchel.nl ;) |
The actual problem is that server code should not really depend on libcrypto, it's only needed in agent part. We need to remove this dependency from the server. |
I face the same issue with self hosting the xftp server. In release 5.4.0.beta.X it starts fine. With later release versions including 5.4.0 and 5.5.0-beta.0 it won't start due to issues finding I found the following lines in the logs that point to the root cause of the failure.
It turned out that I was using ubuntu 22.04, which introduced some issues with regard to the |
After installing 5.4.0 , I get on Ubuntu 22.04.3 LTS the error :
/opt/simplex/smp-server: error while loading shared libraries: libcrypto.so.1.1: cannot open shared object file: No such file or directory
on https://stackoverflow.com/questions/72133316/libssl-so-1-1-cannot-open-shared-object-file-no-such-file-or-directory there is a solution but not recommended.
Is there a way to avoid this problem?
The text was updated successfully, but these errors were encountered: