From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] system: add option for standalone telnetd on target
Date: Thu, 12 Mar 2015 16:25:30 +0100 [thread overview]
Message-ID: <87wq2mi6fp.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1426147462.2639.11.camel@synopsys.com> (Alexey Brodkin's message of "Thu, 12 Mar 2015 08:04:33 +0000")
>>>>> "Alexey" == Alexey Brodkin <Alexey.Brodkin@synopsys.com> writes:
Hi,
> Well probably it was in days of WinXP when Telnet was pre-installed.
> Still as you may see from the article - there's a way to install
> "native" Telnet client from Windows update/software sources.
Yes, but it doesn't seem significantly easier than google + pytty + "I
feel lucky".
>> Don't they ask the same about the serial login password?
> That's exactly the point for serial port as well as for Telnet we may
> not use password for root - which is a default case in Buildroot.
With ssh you could use a ssh key instead.
>>
>> > Indeed your proposal may work if my motivation is not convincing enough.
>>
>> I can still be convinced, but my initial thought is that it isn't
>> really a common enough use case / we should promote ssh instead.
> I tried your proposal with Dropbear but frankly with not much luck.
> What I did:
> [1] Enabled "dropbear": BR2_PACKAGE_DROPBEAR=y
> [2] Set root password: BR2_TARGET_GENERIC_ROOT_PASSWD="xxx"
> What's nice Dropbear auto-starts on boot. But...
> Now on attempt to ssh to the target I see:
---> 8---
> $ ssh root at 192.168.218.2
> root at 192.168.218.2's password:
> PTY allocation request failed on channel 0
> shell request failed on channel 0
---> 8---
Odd, I'm using it every day. Anything of interest in syslog? Perhaps you
are missing a kernel config. Do you have CONFIG_UNIX98_PTYS=y?
> Another inconvenience I discovered with SSH - every time I boot my
> target it gets new fingerprint and then on attempt to ssh to the target
> I see:
Yeah, that's part of the extra security of ssh. Either drop the cached
key or add pregenerated keys in your rootfs.
> I may assume this is because I have filesystem built-in kernel (vmlinux)
> so between boots filesystem doesn't preserve any information - but in
> case of simulators we usually don't have any other options.
You could always add a static set of keys in your rootfs overlay. Not
really ideal from a security POV, but still better than telnet.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2015-03-12 15:25 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
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 [this message]
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=87wq2mi6fp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox