All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: lpd-cdc-core-dev <lpd-cdc-core-dev@windriver.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] openssh: build support openssl 1.1
Date: Wed, 12 Sep 2018 12:30:15 +0200	[thread overview]
Message-ID: <CANNYZj90HLS4HZwtZK+9azCa1iMOjTXtWGy1RCBqCwRGPk+mfA@mail.gmail.com> (raw)
In-Reply-To: <0a2370ce-a756-5cf8-256b-929b70367e3a@windriver.com>

2018-09-12 11:59 GMT+02:00 Hongxu Jia <hongxu.jia@windriver.com>:
> It's a long term target, we should try to push upstream to accept
> openssl 1.1, such as split one patch to multiple sub patches step
> by step, make it more reviewable,  not only openssh, ideally any
> recipe depends on 1.0 should be turned to 1.1

The pull request has been open for two years now:
https://github.com/openssh/openssh-portable/pull/48

I don't think you'll get far with the pushing the upstream. They are
happy using libressl on *BSD, and don't particularly care about Linux
or openssl.

> Currently, use openssl10 as the standalone recipe to provide openssl,
> everything works well in oe-core + oe.

openssl10 upstream support ends at the end of 2019. We can no longer
afford to do nothing about the situation.

> As I mention before, there is still a issue at run time image. Even though
> openssh depends on `openssl10',  but the `openssl' is installed at do_rootfs
>
> It breaks DEPEND/RDEPENDS principle
>
> [local.conf]
> IMAGE_INSTALL_append = " openssh"
> [local.conf]
>
> $ bitbake core-image-minimal
>
> [log.do_rootfs]
>   Installing       : openssl-1.1.1~pre9-r0.core2_64
> [log.do_rootfs]
>
> The recipe depends on openssl10, but openssl10 will not be installed.

There is a library package split, so you should be seeing libcrypto10
or libssl10 installed as well. Can you provide the full log please?

> BTW, Is pre9 1.1.1 openssl a stable release?

Final 1.1.1 has been released yesterday, so I'll send a patch in a moment.

Alex


  reply	other threads:[~2018-09-12 10:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11  8:59 [PATCH] openssh: build support openssl 1.1 Hongxu Jia
2018-09-11  9:10 ` Hongxu Jia
2018-09-11 10:39 ` Alexander Kanavin
2018-09-11 15:18   ` Hongxu Jia
2018-09-12  9:26     ` Alexander Kanavin
2018-09-12  9:59       ` Hongxu Jia
2018-09-12 10:30         ` Alexander Kanavin [this message]
2018-09-12 14:22           ` Khem Raj
2018-09-13  1:13           ` Andre McCurdy
2018-09-13 12:27             ` Alexander Kanavin
2018-09-18 20:17               ` Randy MacLeod

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=CANNYZj90HLS4HZwtZK+9azCa1iMOjTXtWGy1RCBqCwRGPk+mfA@mail.gmail.com \
    --to=alex.kanavin@gmail.com \
    --cc=hongxu.jia@windriver.com \
    --cc=lpd-cdc-core-dev@windriver.com \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.