tags 844503 upstream forwarded 844503 https://github.com/saltstack/salt/pull/37772 thanks
Am Donnerstag, den 17.11.2016, 21:50 +0100 schrieb Sebastian Andrzej Siewior: > control: tags -1 patch > > On 2016-11-16 12:14:43 [+0100], Filip Pytloun wrote: > > To reproduce the issue simply install salt-master and run salt- > > call: > > > > apt-get install salt-master > > salt-call > > > > Following exception will occur: > > > > Traceback (most recent call last): > > File "/usr/bin/salt-call", line 11, in <module> > > salt_call() > > … > > File "/usr/lib/python2.7/dist-packages/salt/utils/rsax931.py", > > line 63, in _init_libcrypto > > libcrypto.OPENSSL_no_config() > > File "/usr/lib/python2.7/ctypes/__init__.py", line 375, in > > __getattr__ > > func = self.__getitem__(name) > > File "/usr/lib/python2.7/ctypes/__init__.py", line 380, in > > __getitem__ > > func = self._FuncPtr((name_or_ordinal, self)) > > AttributeError: /lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined > > symbol: OPENSSL_no_config > > the problem is that salt/rsax931.py loads the library manually and > expects certain symbols which are no longer available in OpenSSL > 1.1.0. > And it loads the first libcrypto it finds plus has no dependency on > openssl. Instead of forcing salt to use OpenSSL 1.0, let's try to make it work with OpenSSL 1.1. Adjusting the initialization to work with OpenSSL 1.1 was quite easy. I forwarded the patch upstream to https://github.com/saltstack/salt/pull/37772 to get it reviewed and accepted. -- Benjamin Drung System Developer Debian & Ubuntu Developer ProfitBricks GmbH Greifswalder Str. 207 D - 10405 Berlin Email: benjamin.dr...@profitbricks.com URL: https://www.profitbricks.de Sitz der Gesellschaft: Berlin Registergericht: Amtsgericht Charlottenburg, HRB 125506 B Geschäftsführer: Achim Weiss