From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Jacques Samoun <jacques.samoun33@gmail.com>
Cc: Buildroot Mailing List <buildroot@buildroot.org>
Subject: Re: [Buildroot] Using an older package than the one provided by BR
Date: Mon, 27 Dec 2021 21:05:06 +0100 [thread overview]
Message-ID: <20211227210506.57dec8e0@windsurf> (raw)
In-Reply-To: <CACaKL1wTVS7C22y-p-Vnu1uBGYtbeaa+b=wj_mv4s+fEsK099Q@mail.gmail.com>
On Mon, 27 Dec 2021 18:18:16 +0200
Jacques Samoun <jacques.samoun33@gmail.com> wrote:
> I am using a quite recent version of BR (embedded platform, ARM base) which
> comes with openssh 8.6p1. However, as i have to support legacy connected
> devices, i discovered that "old" ssh clients (7.1, 7.3, etc ..) have
> sometimes problems connecting to ssh server 8.6p1.
> So i am contemplating the option of "downgrading" the openssh package to
> something like "7.6" but still keeping my BR at the same version.
> I also know that there might be compatibility issues with newer libs, etc
> .. However, this is worth a try.
>
> What do guys think is the best way to do so ?
For something such as openssh that doesn't have any (or very few)
reverse dependencies, you could create an old-openssh package in your
BR2_EXTERNAL, stuck to whatever version makes sense to you.
I'm not familiar with all the incompatibilities between OpenSSH
versions, but isn't there a way to convince your OpenSSH 8.x to support
the older cyphers/protocols used by OpenSSH 7.x ?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-12-27 20:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 16:18 [Buildroot] Using an older package than the one provided by BR Jacques Samoun
2021-12-27 20:05 ` Thomas Petazzoni [this message]
2021-12-27 20:30 ` Jacques Samoun
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=20211227210506.57dec8e0@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@buildroot.org \
--cc=jacques.samoun33@gmail.com \
/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