Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: thomas <thomas.spitz@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Dropbear/SFTP
Date: Thu, 25 Apr 2013 12:51:22 -0700 (PDT)	[thread overview]
Message-ID: <1366919482310-44235.post@n4.nabble.com> (raw)
In-Reply-To: <87ip3a9yzi.fsf@dell.be.48ers.dk>

Hello Peter,

As I wrote, I'm not using dropbear anymore but openssh alone.

Here below my simple test:
thomas at thomas-laptop:~/Armadeus/armadeus-5.2$ sftp root at 192.168.1.5
root at 192.168.1.5's password: 
sh: /usr/libexec/sftp-server: not found
Connection closed

Effectively, I have no /usr/libexec/sftp-server folder on my target. Openssh
didn't create it... Is there something manual to do in order to activate
sftp?

Thanks for your quick reply

Best regards,
Thomas




--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Dropbear-SFTP-tp38207p44235.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.

  reply	other threads:[~2013-04-25 19:51 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
2013-04-25 19:44     ` Peter Korsgaard
2013-04-25 19:51       ` thomas [this message]
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=1366919482310-44235.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox