View Single Post
Old 06-07-2012, 08:08 AM   #311
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by silver18 View Post
It means it has SSH already installed?
Yes.
Unless the start-up scripting erases it (its under the /usr/local sub-tree).

Edit:
Perhaps that is the real reason for the /opt/factory/rootfs_md5_list I mentioned above.
It could be that scripting removes any file not on that list from the filesystem.

It has been reported: "... scripting removes the dropbear installation in /usr/local ..." but that might just be an artifact of a more general "approved manifest" system.
I.E: /usr/local is the only place where things have been put, to then later be removed by scripting.

Some ambitious soul with a KT and a love for reloading the system image would need to check this out for us.

If this turns out to be true, then all we have to do when installing things into the image (like SSH) is to also add the md5 of the files to this "approved manifest".
Unless that turns out to be a 'signed file' with a detached signature and we end up having to deal with another signed file. I never looked for that possibility.


I tried COLOR=GM and this is what I got.
Looks like a day of file forensics for me.

Last edited by knc1; 06-07-2012 at 08:58 AM.
knc1 is offline   Reply With Quote