[PATCH openbmc] Set dropbearkey service to start on boot

[OpenBMC Patches]

From: Brad Bishop <bradleyb at us.ibm.com>

Before this patch it isn't started until the first
client connection which is not the desired behavior.
---
 .../common/recipes-core/dropbear/dropbear/dropbearkey.service | 11 +++++++++++
 .../common/recipes-core/dropbear/dropbear_%.bbappend          |  2 ++
 2 files changed, 13 insertions(+)
 create mode 100644 meta-phosphor/common/recipes-core/dropbear/dropbear/dropbearkey.service
 create mode 100644 meta-phosphor/common/recipes-core/dropbear/dropbear_%.bbappend

diff --git a/meta-phosphor/common/recipes-core/dropbear/dropbear/dropbearkey.service b/meta-phosphor/common/recipes-core/dropbear/dropbear/dropbearkey.service
new file mode 100644
index 0000000..623f73e
--- /dev/null
+++ b/meta-phosphor/common/recipes-core/dropbear/dropbear/dropbearkey.service
@@ -0,0 +1,11 @@
+[Unit]
+Description=SSH Key Generation
+ConditionPathExists=|!/etc/dropbear/dropbear_rsa_host_key
+
+[Service]
+Type=oneshot
+ExecStart=@SBINDIR@/dropbearkey -t rsa -f /etc/dropbear/dropbear_rsa_host_key
+RemainAfterExit=yes
+
+[Install]
+WantedBy=multi-user.target
diff --git a/meta-phosphor/common/recipes-core/dropbear/dropbear_%.bbappend b/meta-phosphor/common/recipes-core/dropbear/dropbear_%.bbappend
new file mode 100644
index 0000000..36c0dcd
--- /dev/null
+++ b/meta-phosphor/common/recipes-core/dropbear/dropbear_%.bbappend
@@ -0,0 +1,2 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+SRC_URI += "file://dropbearkey.service"
-- 
2.6.3