Packages for next Core Update

Packages for next Core Update

[Peter Müller]

[-- Attachment #1: Type: text/plain, Size: 634 bytes --]

Hello,

just a quick footnote:

I am currently building
- OpenSSH 7.9p1
- Apache 2.4.38
- Postfix 3.3.2
- dmidecode 3.2
- Tor 0.3.5.7
for the next Core Update (128).

The Apache and Postfix updates are minor ones and mainly add TLS 1.3
support (I forgot to submit these with OpenSSL 1.1.1a, and accidentally
deleted the local branch :-\ ).

Just in case somebody else thought about building these... :-)

Thanks, and best regards,
Peter Müller
-- 
Microsoft DNS service terminates abnormally when it recieves a response
to a DNS query that was never made.  Fix Information: Run your DNS
service on a different platform.
		-- bugtraq

Re: Packages for next Core Update

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 790 bytes --]

On 23.01.2019 14:55, Peter Müller wrote:
> Hello,

Hi Peter,

> just a quick footnote:
> 
> I am currently building
> - OpenSSH 7.9p1
> - Apache 2.4.38

Me too... ;-)

Building Apache was ok, it looks as if only the rootfile needs to be
adjusted. But I won't have the time today to fix this. Perhaps on weekend.

So I'll wait for your version for proofreading... ;-) Ok?

> - Postfix 3.3.2
> - dmidecode 3.2
> - Tor 0.3.5.7
> for the next Core Update (128).
> 
> The Apache and Postfix updates are minor ones and mainly add TLS 1.3
> support (I forgot to submit these with OpenSSL 1.1.1a, and accidentally
> deleted the local branch :-\ ).
> 
> Just in case somebody else thought about building these... :-)

Good idea! :-)

Best,
Matthias

> Thanks, and best regards,
> Peter Müller
> 

Re: Packages for next Core Update

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]

On 23.01.2019 14:55, Peter Müller wrote:
> Hello,

Hi,

> just a quick footnote:
> 
> I am currently building
> - OpenSSH 7.9p1
> - Apache 2.4.38
> ...

FYI:
While building Apache 2.4.38 I encountered a problem that I can't really
explain to myself.

I started the first build under current 'next', adjusted the 'rootfile'
and tested it on my testmachine. Logically 'httpd' refused to start -
system is too old.

So I changed 'Devel'-branch to current 'Core 126', built again with a
clean build and 'httpd' started. GUI came up - everything seemed to be
OK. But looking at '/var/log/httpd/error_log' I found:

...
[Sat Jan 26 17:20:47.617067 2019] [ssl:warn] [pid 3574:tid 1275335360]
AH01882: Init: this version of mod_ssl was compiled against a newer
library (OpenSSL 1.1.0j  20 Nov 2018, version currently loaded is
OpenSSL 1.1.0i  14 Aug 2018) - may result in undefined or erroneous behavior
...

The next try with Core 125 was successful, no errors in log anymore. Now
this version - built under Core *125* - is running on my productive
machine (Core *126*) without *seen* problems.

The 'openssl' version check on this machine gives me:

...
OpenSSL 1.1.0j  20 Nov 2018 (Library: OpenSSL 1.1.0i  14 Aug 2018)
...

Output in 'error_log':

..
Apache/2.4.38 (Unix) OpenSSL/1.1.0i configured -- resuming normal operations
...

I a bit puzzled because of the two different OpenSSL version-numbers.

Did I miss something?

Best,
Matthias

Re: Packages for next Core Update

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]

Yeah, you seem to have an old version of openssl on your system.

Any idea why?

> On 27 Jan 2019, at 09:06, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> On 23.01.2019 14:55, Peter Müller wrote:
>> Hello,
> 
> Hi,
> 
>> just a quick footnote:
>> 
>> I am currently building
>> - OpenSSH 7.9p1
>> - Apache 2.4.38
>> ...
> 
> FYI:
> While building Apache 2.4.38 I encountered a problem that I can't really
> explain to myself.
> 
> I started the first build under current 'next', adjusted the 'rootfile'
> and tested it on my testmachine. Logically 'httpd' refused to start -
> system is too old.
> 
> So I changed 'Devel'-branch to current 'Core 126', built again with a
> clean build and 'httpd' started. GUI came up - everything seemed to be
> OK. But looking at '/var/log/httpd/error_log' I found:
> 
> ...
> [Sat Jan 26 17:20:47.617067 2019] [ssl:warn] [pid 3574:tid 1275335360]
> AH01882: Init: this version of mod_ssl was compiled against a newer
> library (OpenSSL 1.1.0j  20 Nov 2018, version currently loaded is
> OpenSSL 1.1.0i  14 Aug 2018) - may result in undefined or erroneous behavior
> ...
> 
> The next try with Core 125 was successful, no errors in log anymore. Now
> this version - built under Core *125* - is running on my productive
> machine (Core *126*) without *seen* problems.
> 
> The 'openssl' version check on this machine gives me:
> 
> ...
> OpenSSL 1.1.0j  20 Nov 2018 (Library: OpenSSL 1.1.0i  14 Aug 2018)
> ...
> 
> Output in 'error_log':
> 
> ..
> Apache/2.4.38 (Unix) OpenSSL/1.1.0i configured -- resuming normal operations
> ...
> 
> I a bit puzzled because of the two different OpenSSL version-numbers.
> 
> Did I miss something?
> 
> Best,
> Matthias

Re: Packages for next Core Update

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 251 bytes --]

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.

Best,
Matthias

Re: Packages for next Core Update

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]

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

Re: Packages for next Core Update

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]

Didn’t it look like you just had an old version of OpenSSL on your system?

> On 28 Jan 2019, at 18:32, Matthias Fischer <matthias.fischer(a)ipfire.org> 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

Re: Packages for next Core Update

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 2103 bytes --]

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 <matthias.fischer(a)ipfire.org> 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
> 
> 

Re: Packages for next Core Update

[Arne Fitzenreiter]

[-- Attachment #1: Type: text/plain, Size: 2312 bytes --]

looks like you run an i586 system and the sse2 version of the lib was 
missing in the updater...

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 
>>> <matthias.fischer(a)ipfire.org> 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
>> 
>> 

Re: Packages for next Core Update

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 3428 bytes --]

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 
>>>> <matthias.fischer(a)ipfire.org> 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
>>> 
>>> 
>