From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Packages for next Core Update
Date: Mon, 28 Jan 2019 19:32:28 +0100 [thread overview]
Message-ID: <d0497878-2fe1-d97a-9537-88c490e268c8@ipfire.org> (raw)
In-Reply-To: <2e3ef6e5-6956-de82-ff32-b87b2cdab633@ipfire.org>
[-- 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
next prev parent reply other threads:[~2019-01-28 18:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 13:55 Peter Müller
2019-01-23 17:42 ` Matthias Fischer
2019-01-27 9:06 ` Matthias Fischer
2019-01-28 11:39 ` Michael Tremer
2019-01-28 17:17 ` Matthias Fischer
2019-01-28 18:32 ` Matthias Fischer [this message]
2019-01-29 16:00 ` Michael Tremer
2019-01-29 17:39 ` Matthias Fischer
2019-01-29 17:57 ` Arne Fitzenreiter
2019-01-29 18:15 ` Matthias Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d0497878-2fe1-d97a-9537-88c490e268c8@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox