<div class="gmail_quote">Hi <div><br></div><div>I have copied the generated rsa key and placed it in my nfs root filesystem. I find the problem still persists</div><div><br></div><div>Please see the last leg of the logs below</div>
<div><br></div><div><div class="im">
<div><font color="#3366ff"><i>eth0: link up (100/Full)</i></font></div><div><font color="#3366ff"><i>VFS: Mounted root (nfs filesystem) on device 0:12.</i></font></div></div><div>
<font color="#3366ff"><i>Freeing init memory: 128K</i></font></div><div class="im"><div><font color="#3366ff"><i>Starting network...</i></font></div><div><font color="#3366ff"><i>ip: RTNETLINK answers: File exists</i></font></div>
</div><div><font color="#3366ff"><i>Starting dropbear sshd: OK</i></font></div><div><font color="#3366ff"><i><br></i></font></div><div>I feel the already generated key has been detected. And still the initab doesn't execute. Please advice</div>
<div><div></div><div class="h5">
<br><div class="gmail_quote">On Tue, Jun 21, 2011 at 11:15 AM, Vladimir Murzin <span dir="ltr"><<a href="mailto:murzin.v@gmail.com" target="_blank">murzin.v@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, Jun 20, 2011 at 10:24 AM, Prajosh Premdas<br>
<div><div></div><div><<a href="mailto:premdas.prajosh@gmail.com" target="_blank">premdas.prajosh@gmail.com</a>> wrote:<br>
> Hi Dave and Mulyadi<br>
> Can you tell me where to place the previously generated RSA key. I even<br>
> suspected this but this line<br>
> Starting dropbear sshd: generating rsa key... generating dsa key... OK<br>
><br>
> and the OK pulled me off the track. One more thing can you tell me what<br>
> does the OK mean there...<br>
> My mask is mask=255.0.0.0 so it is able to get the NFS server location<br>
> I typed a wrong command after changing the commands i find no difference<br>
> On Sun, Jun 19, 2011 at 11:22 PM, Dave Hylands <<a href="mailto:dhylands@gmail.com" target="_blank">dhylands@gmail.com</a>> wrote:<br>
>><br>
>> Hi Projish,<br>
>><br>
>> On Sun, Jun 19, 2011 at 8:24 AM, Prajosh Premdas<br>
>> <<a href="mailto:premdas.prajosh@gmail.com" target="_blank">premdas.prajosh@gmail.com</a>> wrote:<br>
>> > Hi<br>
>> > Please find the entire boot sequence here<br>
>> > RomBOOT<br>
>> ...snip...<br>
>> > TCP cubic registered<br>
>> > NET: Registered protocol family 17<br>
>> > rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock<br>
>> > IP-Config: Guessing netmask 255.0.0.0<br>
>> > IP-Config: Complete:<br>
>> > device=eth0, addr=10.220.4.200, mask=255.0.0.0, gw=10.220.4.35,<br>
>> > host=10.220.4.200, domain=, nis-domain=(none),<br>
>> > bootserver=255.255.255.255, rootserver=10.0.0.1, rootpath=<br>
>> > eth0: link up (100/Full)<br>
>> > VFS: Mounted root (nfs filesystem) on device 0:12.<br>
>><br>
>> So it looks like your root file system was mounted successfully.<br>
>><br>
>> > Freeing init memory: 128K<br>
>><br>
>> All message from this point onwards come from init.<br>
>><br>
>> > Starting network...<br>
>> > ip: RTNETLINK answers: File exists<br>
>> > Starting dropbear sshd: generating rsa key... generating dsa key... OK<br>
>><br>
>> And since sshd is starting, it's actually processing stuff from your<br>
>> root file system.<br>
>><br>
>> You may want to try disabling ssh. Generating the rsa key can take<br>
>> several minutes, depending on how fast your target is. So it may look<br>
>> like the system is hung, but it will actually continue to boot.<br>
>><br>
>> You may want save away the generated RSA key and include it in your<br>
>> generated image so that this step is faster. For a given filesystem,<br>
>> it only happens the first time, and once the generated key is stored,<br>
>> ssh will just use the previously generated key. But if you're<br>
>> constantly rebuilding your filesystem without any generated keys then<br>
>> the first time you boot the new filesystem you'lll gget a long delay.<br>
>><br>
>> --<br>
>> Dave Hylands<br>
>> Shuswap, BC, Canada<br>
>> <a href="http://www.davehylands.com" target="_blank">http://www.davehylands.com</a><br>
><br>
><br>
><br>
> --<br>
> Regards,<br>
><br>
> Prajosh Premdas<br>
><br>
</div></div><div>> _______________________________________________<br>
> Kernelnewbies mailing list<br>
> <a href="mailto:Kernelnewbies@kernelnewbies.org" target="_blank">Kernelnewbies@kernelnewbies.org</a><br>
> <a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
><br>
><br>
<br>
Hi Prajosh,<br>
<br>
</div>I believe, that generating keys by sshd involve blocked operation on<br>
/dev/random.<br>
It's strict requirement to use /dev/random instead of /dev/urandom in such case.<br>
<br>
Actually, it's well-known problem in embedded world to fill up entropy<br>
pool, because of<br>
lack random events into some solutions.<br>
<br>
I've heard it's possible to save and restore entropy pool, but it's<br>
not safe, I think.<br>
In my opinion, Dave's suggestion about saving keys into image is quite<br>
suitable, as<br>
soon as you aren't intend to distribute you solution on the market.<br>
<br>
P.S. Sorry for my English.<br>
</blockquote></div><br><br clear="all"><br></div></div>-- <br>Regards,<br><br>Prajosh Premdas<br>
</div>
</div><br><br clear="all"><br>-- <br>Regards,<br><br>Prajosh Premdas<br>