From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fischer To: development@lists.ipfire.org Subject: Re: Packages for next Core Update Date: Tue, 29 Jan 2019 19:15:23 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7550710933123870872==" List-Id: --===============7550710933123870872== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hi, On 29.01.2019 18:57, Arne Fitzenreiter wrote: > looks like you run an i586 system ... Correct. Profile: https://fireinfo.ipfire.org/profile/5f68a6360ffbecb6877dcac75f5b8c8030f43ce8 > ...and the sse2 version of the lib was > missing in the updater... Hm. Anything I can do about it? I ran a clean Core 126 build this night. Everything went ok. I created several *.tar.gz-archives: openssh-7.8p1-for-ipfire.tar.gz openssl-1.1.0j-for-ipfire.tar.gz openssl-compat-1.0.2q-for-ipfire.tar.gz But if I get you right then these won't help!? During testing I just bungled my testmachine (needed an update, anyway), but I don't want to do that with my productive machine. ;-) Searching for 'sse2' I found a '.../build/usr/lib/sse2' directory on the 'Devel'-machine: root(a)Devel: /home/matz/ipfire-2.x/build/usr/lib/sse2 # ls -l total 3200 -rwxr-xr-x 1 root root 2760172 Jan 29 00:37 libcrypto.so.1.1 lrwxrwxrwx 1 root root 16 Jan 28 19:15 libgmp.so.10 -> libgmp.so.10.3.2 -rwxr-xr-x 1 root root 513596 Jan 29 00:37 libgmp.so.10.3.2 Are these the files I would need? Would that be sufficient? Best, Matthias > Arne > > > On 2019-01-29 18:39, Matthias Fischer wrote: >> Hi, >> >> On 29.01.2019 17:00, Michael Tremer wrote: >>> Didn’t it look like you just had an old version of OpenSSL on your >>> system? >> >> What puzzles me is that when I query the openssl version, I get the >> version number 1.1.0j for openssl on the one hand and the version >> number >> 1.1.0i for the library on the other hand: >> >> ... >> root(a)ipfire: ~ # openssl version >> OpenSSL *1.1.0j* 20 Nov 2018 (Library: OpenSSL *1.1.0i* 14 Aug 2018) >> ... >> >> And I can't find the reason for the *1.1.0i* version. IMHO I have only >> 1.1.0j installed. Where does the 1.1.0i come from!? >> >> Best, >> Matthias >> >>>> On 28 Jan 2019, at 18:32, Matthias Fischer >>>> wrote: >>>> >>>> On 28.01.2019 18:17, Matthias Fischer wrote: >>>>> Hi, >>>>> >>>>> On 28.01.2019 12:39, Michael Tremer wrote: >>>>>> Yeah, you seem to have an old version of openssl on your system. >>>>>> >>>>>> Any idea why? >>>>>> ... >>>>> >>>>> Nope. No clue. I didn't change or test anything regarding openssl. >>>>> >>>>> But I'll try to find out. >>>>> ... >>>> >>>> I didn't find the reason. Right now I'm recompiling Core126 with a >>>> clean >>>> build. >>>> >>>> The only 'openssl' files on my Core 126 productive machine seem to be >>>> from the same "1.1.0j" version and I can't find a string leading me >>>> to >>>> "1.1.0i": >>>> >>>> ... >>>> root(a)ipfire: / # find -name openssl -ls >>>> 10896 4 drwxr-xr-x 3 root root 4096 Mar 3 2016 >>>> ./usr/lib/openssl >>>> 6551 600 -rwxr-xr-x 1 root root 613832 Dec 11 05:44 >>>> ./usr/bin/openssl >>>> ... >>>> >>>> ... >>>> root(a)ipfire: / # find -name libcrypto.so.1.1* -ls >>>> 10513 2692 -rwxr-xr-x 1 root root 2755616 Aug 30 02:02 >>>> ./usr/lib/sse2/libcrypto.so.1.1 >>>> 19763 2640 -rwxr-xr-x 1 root root 2699976 Dec 11 05:45 >>>> ./usr/lib/libcrypto.so.1.1 >>>> ... >>>> >>>> ... >>>> root(a)ipfire: / # find -name libssl.so.1.1* -ls >>>> 20588 504 -rwxr-xr-x 1 root root 512236 Dec 11 05:44 >>>> ./usr/lib/libssl.so.1.1 >>>> ... >>>> >>>> I can't even find something regarding the given date for "1.1.0i", >>>> "14 >>>> Aug 2018". >>>> >>>> Does anyone has a clue where to search? >>>> >>>> Best, >>>> Matthias >>> >>> > --===============7550710933123870872==--