From: Patrick Ohly <patrick.ohly@intel.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: how to *securely* do a remote install of an OE image?
Date: Tue, 28 Feb 2017 13:42:30 +0100 [thread overview]
Message-ID: <1488285750.7785.43.camel@intel.com> (raw)
In-Reply-To: <c784e8d2-afd8-b4d3-1cd3-75d1d398dea8@mlbassoc.com>
On Tue, 2017-02-28 at 13:32 +0100, Gary Thomas wrote:
> > For ssh keys, there's rootfsdebugfiles.bbclass. In local.conf:
> >
> > INHERIT += "rootfsdebugfiles"
> > ROOTFS_DEBUG_FILES += "/home/pohly/.ssh/id_rsa.pub
> ${IMAGE_ROOTFS}/home/root/.ssh/authorized_keys ;"
> >
> > This copies my id_rsa.pub into authorized_keys and thus let's me log
> > into images that I create via ssh.
> >
>
> Does this work for dropbear or only openssh?
Should also work with dropbear. From
https://matt.ucc.asn.au/dropbear/dropbear.html:
"Compatible with OpenSSH ~/.ssh/authorized_keys public key
authentication"
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-02-28 12:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 10:28 how to *securely* do a remote install of an OE image? Robert P. J. Day
2017-02-28 12:27 ` Patrick Ohly
2017-02-28 12:32 ` Gary Thomas
2017-02-28 12:42 ` Patrick Ohly [this message]
2017-02-28 15:20 ` Robert P. J. Day
2017-02-28 16:52 ` Bryan Evenson
2017-02-28 16:33 ` Enrico Scholz
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=1488285750.7785.43.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.org \
/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