From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Roland Hieber <rhi@pengutronix.de>
Cc: distrokit@pengutronix.de, Holger Assmann <h.assmann@pengutronix.de>
Subject: Re: [DistroKit] [PATCH] ptxconfig: enable scp per default
Date: Mon, 1 Mar 2021 07:11:18 +0100 [thread overview]
Message-ID: <20210301061118.hdcckb6oxlfndggw@pengutronix.de> (raw)
In-Reply-To: <20210228213632.ypw7anowavwivkid@pengutronix.de>
On Sun, Feb 28, 2021 at 10:36:32PM +0100, Roland Hieber wrote:
> On Wed, Dec 16, 2020 at 04:38:18PM +0100, Robert Schwebel wrote:
> > On Wed, Dec 16, 2020 at 04:25:39PM +0100, Holger Assmann wrote:
> > > The secure copy program (scp) allows direct file access on the target
> > > via the ssh protocol. Since ssh is already turned on by default in
> > > ptxconfig, we might also enable scp as well.
> > >
> > > Signed-off-by: Holger Assmann <h.assmann@pengutronix.de>
> > > ---
> > > configs/ptxconfig | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Applied to next.
>
> This seems to have fallen through the cracks, I cannot find it on either
> master or next…
Could you rebase to current master? The patch doesn't apply any more,
and on master, selecting the option does also enforce
PTXCONF_OPENSSH_SSH=y
I'm not sure if this is correct. Is an ssh client necessary on the
target to scp something to it...?
rsc
--
Pengutronix e.K. | Dipl.-Ing. Robert Schwebel |
Steuerwalder Str. 21 | https://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
prev parent reply other threads:[~2021-03-01 6:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 15:25 Holger Assmann
2020-12-16 15:38 ` Robert Schwebel
2021-02-28 21:36 ` Roland Hieber
2021-03-01 6:11 ` Robert Schwebel [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=20210301061118.hdcckb6oxlfndggw@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=h.assmann@pengutronix.de \
--cc=rhi@pengutronix.de \
/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