From: thomas <thomas.spitz@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Dropbear/SFTP
Date: Thu, 25 Apr 2013 12:41:34 -0700 (PDT) [thread overview]
Message-ID: <1366918894609-44233.post@n4.nabble.com> (raw)
In-Reply-To: <20130108130618.4991dff7@skate>
Dear Thomas Petazzoni,
I am in the same case as Ted Wood that is to say I can login using ssh from
a console ("ssh root at 192.168.1.5") however I am not able to connect to SFTP
server:("sftp root at 192.168.1.5" asks for a password but I got the following
error : sh: /usr/libexec/sftp-server: not found
Connection closed)
I am not using dropbear anymore (as it doesn't implement sftp) and enabled
openssh only. I would also want to use Buildroot/Eclipse integration (sounds
perfect) but I don't know which file the patch described here
"https://github.com/mbats/eclipse-buildroot-toolchain-plugin/blob/master/buildroot.patches/Integration-with-Buildroot-Toolchain-Eclipse-plugin.patch"
should apply to? Moreover I have a buildroot 201204 instead 201211 as
recommanded for the patch.
Hope you could help me
Best regards,
Thomas
--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Dropbear-SFTP-tp38207p44233.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
next prev parent reply other threads:[~2013-04-25 19:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 11:54 [Buildroot] Dropbear/SFTP Ted Wood
2013-01-08 12:06 ` Thomas Petazzoni
2013-01-08 12:59 ` Willy Lambert
2013-01-08 14:15 ` Will Moore
2013-01-08 14:31 ` Thomas Petazzoni
[not found] ` <alpine.DEB.2.02.1301081329510.17533@www.arte.unipi.it>
2013-01-08 15:10 ` Peter Korsgaard
2013-01-13 15:03 ` Thomas Petazzoni
2013-04-25 19:41 ` thomas [this message]
2013-04-25 19:44 ` Peter Korsgaard
2013-04-25 19:51 ` thomas
2013-04-25 20:54 ` Peter Korsgaard
2013-04-25 21:42 ` thomas
2013-04-25 21:58 ` Peter Korsgaard
2013-04-26 7:12 ` thomas
2013-04-26 7:46 ` thomas
2013-04-26 9:27 ` Peter Korsgaard
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=1366918894609-44233.post@n4.nabble.com \
--to=thomas.spitz@gmail.com \
--cc=buildroot@busybox.net \
/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.