Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] busybox: add option for standalone telnetd on target
Date: Tue, 21 Apr 2015 13:38:26 +0000	[thread overview]
Message-ID: <1429623506.2624.12.camel@synopsys.com> (raw)
In-Reply-To: <1426152671-13125-1-git-send-email-abrodkin@synopsys.com>

Hi Peter,

On Thu, 2015-03-12 at 12:31 +0300, Alexey Brodkin wrote:
> If target has connection to the network it might be pretty useful to
> have telnet connection to it instead of serial console or even in
> addition to serial console.
> 
> Even though it's possible to add telnetd on target manually via:
>  [a] Busybox - with "make busybox-menuconfig" and in "Networking
> Utilities" select "telnetd"
>  [b] xinetd
> 
> Still additional manual steps will be required to allow root login over
> telnet and telnet daemon auto-start on boot.
> 
> With this change it will be possible to get telnetd built and installed
> on target with only enabling BR2_SYSTEM_STANDALONE_TELNETD option in
> Buildroot configuration utility or in boards defconfig.
> 
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: Peter Korsgaard <peter@korsgaard.com>
> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> 
> Changes in v2:
>  * STANDALONE_TELNETD option moved from "system" to Busybox package
>  * Added auto-start script for telnet daemon
>  * Added warning in Kconfig about possible Telnet security issues with mention
>    of SSH to be used instead on production systems
> 
> ---
>  package/busybox/Config.in  | 22 ++++++++++++++++++++++
>  package/busybox/S50telnet  | 20 ++++++++++++++++++++
>  package/busybox/busybox.mk | 14 ++++++++++++++
>  system/system.mk           | 17 +++++++++++++++++
>  4 files changed, 73 insertions(+)
>  create mode 100755 package/busybox/S50telnet

I've got a reminder about my pending Buildroot patches and that one is
one of them.

I'm still interested in this one and would like at least to discuss if
that updated version suits Buildroot or as we discussed in v1 comments
it's a no go in favor to ssh for debugging over network.

-Alexey

      reply	other threads:[~2015-04-21 13:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12  9:31 [Buildroot] [PATCH v2] busybox: add option for standalone telnetd on target Alexey Brodkin
2015-04-21 13:38 ` Alexey Brodkin [this message]

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=1429623506.2624.12.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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