From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Cc: buildroot@uclibc.org
Subject: Re: [Buildroot] sftp-server for use with dropbear?
Date: Thu, 8 Sep 2022 23:21:13 -0000 (UTC) [thread overview]
Message-ID: <tfdtd9$17g0$1@ciao.gmane.io> (raw)
In-Reply-To: tera67$v9n$1@ciao.gmane.io
On 2022-09-01, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> On 2022-09-01, Grant Edwards <grant.b.edwards@gmail.com> wrote:
>
>> The server doesn't need wchar support at all.
>
> I got gesftpserver's server to build without wchar support, and it
> works fine. But it's auto-selecting iconv. That makes the total rootfs
> size increase for the gesftpserver almost 1MB, and I can't justify
> that.
I looked at the iconv use, and it looks like it should be pretty easy
to make iconv a configurable option -- whether that would be accepted
upstream is another question.
But, I finally realized that my problem was triggered by an upgrade to
openssh's "scp" utility v8.8 which uses the SFTP protocol by default
instead of the SCP protocl. [If I wanted to use SFTP, I would have
typed "sftp" not "scp".] It turns out that with openssh 8.8 "scp -O"
works fine with dropbear. Unfortunately there's no config file or
environment variables for scp like there is for ssh.
--
Grant
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-09-08 23:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 18:41 [Buildroot] sftp-server for use with dropbear? Grant Edwards
2022-09-01 18:58 ` Yann E. MORIN
2022-09-01 19:25 ` Grant Edwards
2022-09-01 19:48 ` Yann E. MORIN
2022-09-01 20:06 ` Grant Edwards
2022-09-01 20:32 ` Grant Edwards
2022-09-01 22:02 ` Grant Edwards
2022-09-08 23:21 ` Grant Edwards [this message]
2022-09-01 20:51 ` Thomas Petazzoni via buildroot
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='tfdtd9$17g0$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.net \
--cc=buildroot@uclibc.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