Hi,
Having issues with plugins which use libssl

Sublime Text 3 3064 on Fedora 20 64bit.

reloading plugin Mediawiker.mediawiker Mediawiker: enabling custom linux ssl module Mediawiker: _ssl module import error - libssl.so.1.0.0: cannot open shared object file: No such file or directory Mediawiker: _ssl module import error - libssl.so.1.0.0: cannot open shared object file: No such file or directory Mediawiker: _ssl module import error - libssl.so.1.0.0: cannot open shared object file: No such file or directory Mediawiker: http_compat reloaded. HTTPS is not available in this python environment, trying http: 'module' object has no attribute 'HTTPSConnection' reloading plugin Print to HTML.PrintToHTML reloading plugin SFTP.SFTP SFTP: enabling custom linux ssl module SFTP: _ssl module import error - libssl.so.1.0.0: cannot open shared object file: No such file or directory SFTP: _ssl module import error - libssl.so.1.0.0: cannot open shared object file: No such file or directory SFTP: _ssl module import error - libssl.so.1.0.0: cannot open shared object file: No such file or directory

Any help is highly appreciated. If you need further information just ask

Thanks

Silberling

I’d like to bump this post as with rev. 3066 this is still present

I just took some time playing around with symlinks

In /usr/lib64

ln -s libssl.so.10 libssl.so.1.0.0

ln -s libcrypto.so.10 libcrypto.so.1.0.0

Yeah, okay this is 1.0.1e-40.fc20

Okay. Now i tried to compile by hand:

wget https://www.openssl.org/source/openssl-1.0.0o.tar.gz ./config shared && make && make test && sudo make install

I created symlinks with the correct filenames in /usr/local/lib64.
Sublime did not notice them

I creates symlinks in /usr/lib64 and I got this:

Strange thing that SFTP complains because of Mediawiker. I removed it temporarily.

Same thing here.

Now I don’t really know what to do now :-S

Bug is still active and I can’t install older libssl-libs.

Error-Pop-Up says: “Package Control just installed or upgraded the missing Python _ssl module for Linux since Sublime Text does not include it.”

Console however says:
Package Control: Downloading bootstrapped dependency ssl-linux
Package Control: Successfully downloaded bootstraped dependency ssl-linux
Linux SSL: _ssl module import error - libssl.so.1.0.0: cannot open shared object file: No such file or directory
Linux SSL: successfully loaded _ssl module for libssl.so.10
Linux SSL: unloading http module so ssl will be available
Linux SSL: unloading urllib module so ssl will be available

So it seems this thing is working and the error message is not needed. Is this correct or am I missing something?

If you see “Linux SSL”, that is a shim Package Control tries to install.

OpenSSL on Linux is usually either 0.9.8 or 1.x.x. However, some distros like Fedora link OpenSSL 1.0.0 differently, so there are 3 different shared libraries that I have to build _ssl.so against (and two different architectures: x32 and x64):

• libssl-1.0.0

• libssl-10

• libssl-0.9.8

These are all published at github.com/codexns/sublime-ssl- … /loader.py.

When the shim is loaded, it tries each of those in order. It is ok if one errors out, as long as it is able to successfully load one of them, you should have SSL functionality.

I should note, as of Package Control 3.0, the hope is that the Package Control shim will deal with SSL on linux so we don’t have 15 different packages all trying to shim in SSL.