From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] system: add option for standalone telnetd on target
Date: Wed, 11 Mar 2015 17:22:55 +0100 [thread overview]
Message-ID: <877funmrkw.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1426066527-23021-1-git-send-email-abrodkin@synopsys.com> (Alexey Brodkin's message of "Wed, 11 Mar 2015 12:35:27 +0300")
>>>>> "Alexey" == Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:
> 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.
> 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.
> Note that telnetd won't auto-start on boot because of securilty concerns
> - until user manually starts telnetd while connected via serial console
> there's no chance for unexpected root access to the target (this is
> especially true if root has no password set - which is by defult).
Any specific reason why you don't just configure a root password and
enable dropbear instead?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-03-11 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 9:35 [Buildroot] [PATCH] system: add option for standalone telnetd on target Alexey Brodkin
2015-03-11 16:22 ` Peter Korsgaard [this message]
2015-03-11 16:44 ` Alexey Brodkin
2015-03-11 16:53 ` Peter Korsgaard
2015-03-12 8:04 ` Alexey Brodkin
2015-03-12 12:59 ` Mike Williams
2015-03-12 14:35 ` Alexey Brodkin
2015-03-12 15:10 ` Thomas Petazzoni
2015-03-12 20:26 ` Arnout Vandecappelle
2015-03-12 15:25 ` Peter Korsgaard
2015-03-11 16:56 ` Thomas Petazzoni
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=877funmrkw.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.