Question regarding patch ee328f16bfceacd30361ad0f562929ebe88b9363

Question regarding patch ee328f16bfceacd30361ad0f562929ebe88b9363

[Peter Müller]

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

Hello Arne,

sorry for dropping in here.

Looking at the ipfire-2.x git repository (and the planet note
for the Core Update 116 testing), I assume commit ee328f16bfceacd30361ad0f562929ebe88b9363
should read "openssl" instead of "openssh".

Or am I missing something?

Just curious. :-)

Best regards,
Peter Müller

Re: Question regarding patch ee328f16bfceacd30361ad0f562929ebe88b9363

[Michael Tremer]

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

No, I guess Arne means OpenSSH.

This is because of some old habit when OpenSSH was linked against OpenSSL.
Replacing the library cause OpenSSH to behave weird and crash - I have no reason
why that was the case.

But since they are independent there is no need to ship OpenSSH when ever we
update OpenSSL any more.

-Michael

On Mon, 2017-11-06 at 19:29 +0100, Peter Müller wrote:
> Hello Arne,
> 
> sorry for dropping in here.
> 
> Looking at the ipfire-2.x git repository (and the planet note
> for the Core Update 116 testing), I assume commit
> ee328f16bfceacd30361ad0f562929ebe88b9363
> should read "openssl" instead of "openssh".
> 
> Or am I missing something?
> 
> Just curious. :-)
> 
> Best regards,
> Peter Müller

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]