All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Boge <joerg.boge@gmx.de>
To: Otavio Salvador <otavio@ossystems.com.br>,
	meta-freescale@yoctoproject.org
Subject: Re: sftp fsl-image-gui
Date: Sun, 04 Aug 2013 21:36:41 +0200	[thread overview]
Message-ID: <51FEAD49.80700@gmx.de> (raw)
In-Reply-To: <CAP9ODKqLxhPF2Hb7G_egncgJA8=+WSuNXQPL0+tu1y=B+-avVg@mail.gmail.com>

On 08/04/2013 09:07 PM, Otavio Salvador wrote:
> On Sun, Aug 4, 2013 at 8:05 AM, Joerg Boge <joerg.boge@gmx.de> wrote:
>> I want to connect via sftp without success.
>>
>> On FAQ openssh.org I find some information about.
>>
>> 2.9 - sftp/scp fails at connection, but ssh is OK.
>>
>> sftp and/or scp may fail at connection time if you have shell initialization
>> (.profile, .bashrc, .cshrc, etc) which produces output for non-interactive
>> sessions. This output confuses the sftp/scp client. You can verify if your
>> shell is doing this by executing:
>>
>> ssh yourhost /usr/bin/true
>>
>> If the above command produces any output, then you need to modify your shell
>> initialization.
>>
>>
>> I think that is a major problem witch should be solved generally for the
>> images produced by yocto.
> We need more information about the issue. Are you using OpenSSH / Dropbear?
>
> Please reproduce it with an smaller image (core-image-base) so we can
> really see what's going on and work to fix it.
>

EXTRA_IMAGE_FEATURES = "debug-tweaks ssh-server-openssh"

it is the same on core-image-base

dropbear also not work, but I think that could be normal, not sure that 
sftp is implemented on dropbear





  reply	other threads:[~2013-08-04 19:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-04 11:05 sftp fsl-image-gui Joerg Boge
2013-08-04 19:07 ` Otavio Salvador
2013-08-04 19:36   ` Joerg Boge [this message]
2013-08-04 19:59     ` Otavio Salvador
2013-08-04 21:02       ` Joerg Boge
2013-08-05 17:06       ` Joerg boge
2013-08-05 17:07         ` Otavio Salvador

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=51FEAD49.80700@gmx.de \
    --to=joerg.boge@gmx.de \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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.