4395 2013-04-23 08:39:35 +0000 [FRI2] ssh keys cannot be loaded 2013-09-25 06:41:05 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 1.4 FRI2 Multiple VERIFIED WORKSFORME Medium normal 1.5 1 alexandrux.palalau sgw dvhart jessica.zhang meta.mr.watcher meta.watcher tom.zanussi --- --- No (bug/feature does not impact docs) oldest_to_newest 32512 0 alexandrux.palalau 2013-04-23 08:39:35 +0000 sshd fails to start on the FRI2 due to the fact that the RSA keys cannot be loaded. Removing the ssh_host_dsa_key, ssh_host_rsa_key and ssh_host_ecdsa_key and regenerating them at sshd start starts the ssh service. Branch: dylan Commit ID: 789b2b7e0cca404ff8ba8ed5ba823d215e6ba5b4 Meta intel Commit ID: 76f70c337e5daa9593153dfdf5107aec08610a44 32531 1 dvhart 2013-04-23 14:16:37 +0000 Surely this is not BSP specific? 32537 2 alexandrux.palalau 2013-04-23 15:05:53 +0000 It was only encountered on the FRI2 until now. Other BSPs that I've tested on this test run (NUC) did not show this behavior 32561 3 dvhart 2013-04-24 03:01:18 +0000 I just booted my FRI2 today using a minimal and sato image created using mkefidisk.sh from the respective hddimg and both start ssh successfully. Please provide a complete description of how you are creating the image and how you are booting it. 32562 4 dvhart 2013-04-24 03:01:27 +0000 . 32565 5 alexandrux.palalau 2013-04-24 08:41:38 +0000 This was reproduced with an autobuilder image: http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20130418-2/machines/fri2/core-image-sato-sdk-fri2.hddimg dd on USB stick and install on the FRI2. 32689 6 sgw 2013-04-26 20:44:38 +0000 Ok, I tested with the image listed below along with my own generated image both using the HDD Image boot direct from USB stick, no issues with sshd starting and running on either of my images. Can you please verify your setup and if needed send more details about this. 32755 7 alexandrux.palalau 2013-04-30 09:19:28 +0000 Checked it with the same image on another FRI2 with Fast Boot and everything works fine. 33112 8 sgw 2013-05-16 13:02:44 +0000 Alex confirmed! 37153 9 alexandrux.palalau 2013-09-25 06:41:05 +0000 Switching to verified as per last comments. The behavior was not again encountered.