============================================
    Linux-ready firmware developer kit:
           HOWTO SSH COPY RESULT
============================================

LFK supports uploading test results over the network. The file transfer is via scp/ssh from the 
test target to a single host. 

At the host side, an SSH daemon must be active and support "publickey" authentication method. 
LFK CD image has pre-generated public-private key pair, the public key is available below. 
It needs to be appended or copied to your host ~root/.ssh/authorized_keys. 

Host IP and destination directory information can be set automatically or manually. For the manual 
method, the user needs to manually type host IP address and directory name in the syntax of scp; 
For the automatic method, a user needs to use PXE, USB, or other boot method which allows you to 
edit the kernel command line. For an example, on a PXE server the entry for LFK looks like:

label lfk
        kernel vmlinuz-lfk
        APPEND   root=/dev/ram0 init=/init ramdisk_size=8192 vga=0x314 ip=dhcp initrd=initramfs-lfk  console=tty1 pci=nommconf  idle=poll udev saveovernet=11.11.11.10:/root/temp/ noninteractive

The "saveovernet" parameter tells LFK where to save test results. If "noninteractive" is given to 
LFK, the entire process will be automated, i.e. LFK will perform the tests, save the result to 
host, then reboot. After a few iterations, the host destination directory will have results from 
multiple runs and looks like below:

putvin:~# ls -l /root/temp/
total 12
drwxr-xr-x 2 root root 4096 2007-01-10 10:14 results_testmachine_1415020102
drwxr-xr-x 2 root root 4096 2007-01-10 10:16 results_testmachine_1416020102
drwxr-xr-x 2 root root 4096 2007-01-10 10:17 results_testmachine_1417020102

To stop the repetitive reboots needs human intervention.


Public key for LFK:
ssh-dss AAAAB3NzaC1kc3MAAACBAKrgKSyoKV+hJxeOEdUPyQ0Bo75sPxs4gYipx5XcHOvPSMdwE/ty7ejbOiMbkWKt8+aug7NWV/CGX198/muZ1OYCehaC3nUAGK/vhPkbv/IAEP9bEb3KZOXvKJZVYiviLYs84NoMu84y/ixSgETuQms8aC1vIAVnaZm9idN9as2tAAAAFQDPthkdEE8Cz88tafP603kYF4uqFwAAAIEAp9oiYshDwRlPzQsAi8pMJh3juTGLtTz6Zyx7jKvnV4GaEnqdoDpX6iafCu9V6jypiCWlK65cXq0vitB5bh4mw+FAg80bxZ8RrP7il9rFuYtI2kyZ1ccLPVRf2hV+OE3zXjBACubOpns6sITuC94zyKiWW0SigCcRK1X2hYNluFQAAACAeMz/XFrG5bNbO+YI4TGfnxUeD+QVJgFgQXpjWiamRcz2Lw13/J8QL1tQmlDKlWxGInBQmVGfx/gA4fzdTshtTmUq0fyBxRLdYF6suhQtmPeI0WxRC1vJMDyN3Ywm3S6gXZqKmFQSwvpZ7N64z2uWO7IuJhyHdx1Xmflii6nwkWQ= root@putvin

=============================
Alternative way (more secure)
=============================
If you feel uncomfortable allowing root access with a publically known key, then
configure as follows:

1) nail down the server and directory with
"saveovernet=1.2.3.4:/root/FirmwareKitresults/" as described above.

2) save the key with restrictions:

#
# Linux Ready Firmware Kit
from="*.testing.local",command="scp -r -t /root/FirmwareKitresults/" ssh-dss
AAAAB3NzaC1kc3MAAACBAKrgKSyoKV+hJxeOEdUPyQ0Bo75sPxs4gYipx5XcHOvPSMdwE/ty7
ejbOiMbkWKt8+aug7NWV/CGX198/muZ1OYCehaC3nUAGK/vhPkbv/IAEP9bEb3KZOXvKJZVYiviLYs84NoMu84y/ixSgETuQms8aC1vIAVnaZm9idN9as2tAAAAFQDPthkdEE8Cz88tafP603kYF4u
qFwAAAIEAp9oiYshDwRlPzQsAi8pMJh3juTGLtTz6Zyx7jKvnV4GaEnqdoDpX6iafCu9V6jypiCWlK65cXq0vitB5bh4mw+FAg80bxZ8RrP7il9rFuYtI2kyZ1ccLPVRf2hV+OE3zXjBACubOpns6s
ITuC94zyKiWW0SigCcRK1X2hYNluFQAAACAeMz/XFrG5bNbO+YI4TGfnxUeD+QVJgFgQXpjWiamRcz2Lw13/J8QL1tQmlDKlWxGInBQmVGfx/gA4fzdTshtTmUq0fyBxRLdYF6suhQtmPeI0WxRC1v
JMDyN3Ywm3S6gXZqKmFQSwvpZ7N64z2uWO7IuJhyHdx1Xmflii6nwkWQ= root@putvin

3) keep in mind that  your results will now always go to
/root/FirmwareKitresults/ if you save to 1.2.3.4, no matter what directory you
specify when saving (see 'man 8 sshd' for information on how the command=
parameter works)


Contributer:   Jacob Pan (jacob.jun.pan@intel.com)
		Patrick C.F.Ernzer