Closed PowerPress closed 8 years ago
I am currently assessing whether or not it is worth the effort to determine which OpenSSL versions are available (if any) on the fly, given how finicky OpenSSL is about version mismatches. Currently, the "devel" branch has the ability to build without OpenSSL at all. Simply uncomment the appropriate section of the Makefile:
I'm going to close this out without a specific patch. I just released a new version where the default profile in the Makefile is to build OpenSSL statically into the binary. Given the nature of this tool, I don't want it ever defaulting to plaintext if libssl isn't available. The Makefile also has a "compatability" build profile now without any crypto and that uses older libc networking calls.
Please consider if possible only loading a library if a argument is used for it.
./revsh: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory