Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] openssh: add option to allow login as root
Date: Wed, 20 Mar 2019 10:26:58 +0100	[thread overview]
Message-ID: <20190320092658.GH2702@scaer> (raw)
In-Reply-To: <CADvTj4q9+uWVE-Yooj7gwVygHca0Y8KiKoHUBtRruf2jzyi8mQ@mail.gmail.com>

James, All,

On 2019-03-20 03:05 -0600, James Hilliard spake thusly:
> One reason for using openssh instead of dropbear without a custom
> config would be
> for sftp support.

So we have gesftpserver that can be used with dropbear to provide sftp,
and AFAICS, that works just out of the box.

I don't understand what you mean by "without a custom config".

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2019-03-20  9:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 11:41 [Buildroot] [RFC] openssh: add option to allow login as root Esben Haabendal
2019-03-19 15:23 ` Grant Edwards
2019-03-19 22:42 ` Peter Korsgaard
2019-03-20  0:23   ` Arnout Vandecappelle
2019-03-20  8:58     ` Peter Korsgaard
2019-03-20  9:05       ` James Hilliard
2019-03-20  9:23         ` Arnout Vandecappelle
2019-03-20  9:26         ` Yann E. MORIN [this message]
2019-03-20  9:32           ` James Hilliard
2019-03-20 16:25     ` Carlos Santos

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=20190320092658.GH2702@scaer \
    --to=yann.morin.1998@free.fr \
    --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