From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Question regarding patch ee328f16bfceacd30361ad0f562929ebe88b9363
Date: Mon, 06 Nov 2017 18:34:50 +0000 [thread overview]
Message-ID: <1509993290.4838.288.camel@ipfire.org> (raw)
In-Reply-To: <20171106192929.409c6059.peter.mueller@link38.eu>
[-- 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 --]
prev parent reply other threads:[~2017-11-06 18:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 18:29 Peter Müller
2017-11-06 18:34 ` Michael Tremer [this message]
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=1509993290.4838.288.camel@ipfire.org \
--to=michael.tremer@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