Re: Packages for next Core Update

[Michael Tremer <michael.tremer@ipfire.org>]

[-- 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