From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Thu, 12 Mar 2015 16:10:13 +0100 Subject: [Buildroot] [PATCH] system: add option for standalone telnetd on target In-Reply-To: <1426170908.2639.25.camel@synopsys.com> References: <1426066527-23021-1-git-send-email-abrodkin@synopsys.com> <877funmrkw.fsf@dell.be.48ers.dk> <1426092262.2375.11.camel@synopsys.com> <87pp8flblh.fsf@dell.be.48ers.dk> <1426147462.2639.11.camel@synopsys.com> <1426170908.2639.25.camel@synopsys.com> Message-ID: <20150312161013.4b73baff@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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