From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] system: add option for standalone telnetd on target
Date: Thu, 12 Mar 2015 16:10:13 +0100 [thread overview]
Message-ID: <20150312161013.4b73baff@free-electrons.com> (raw)
In-Reply-To: <1426170908.2639.25.camel@synopsys.com>
Dear Alexey Brodkin,
On Thu, 12 Mar 2015 14:35:08 +0000, Alexey Brodkin wrote:
> Even though I may use this hint myself locally I'm afraid it's not the
> best solution if others want to use the same Buildroot configuration.
>
> Because to make their life easier I'll need to push those SSH keys in
> public repository - and this won't work for upstreaming the board
> support in Buildroot.
>
> So at least for now SSH doesn't look as an equally simple option as
> Telnet.
>
> Once again - this is because my particular corner-case when rootfs is
> built in kernel image. If there is some real non-volatile storage on
> target SSH might be a good option still.
FWIW, I also do kernel development only with an initramfs, and I still
use SSH. I simply remove the key from my system using ssh-keygen -R, as
suggested by modern OpenSSH versions when you connect to a host for
which you have an invalid key locally.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-12 15:10 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 [this message]
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=20150312161013.4b73baff@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.