Whether you are using lnstcustom with a thumb drive, hard drive, floppy or some other type of hard disk, the basic concept and preparation is the same. However, if you want to use the lnstcustom with a web server, there are some differences:
The entire customization directory must be archived into
a single tar.gz file.
You won't be able to easily write any changes back (in the previous example, the thumb drive was able to "learn" by simply copying a configuration file if the user adjusted it).
Assuming you still have your thumb drive mounted from
the previous session, the following is all that is required to
create and install the custom configuration on a fictional web
server 192.168.0.17:
[root@probe root]#tar czf /tmp/test.tgz -C /mnt/nst test[root@probe root]#tar tzf /tmp/test.tgztest/ test/XF86Config test/setup.sh[root@probe root]#scp /tmp/test.tgz root@192.168.0.17:/var/www/htmlWarning: Permanently added '192.168.0.17' (RSA) to the list of known hosts. root@192.168.0.17's password: test.tgz 100% |*****************************| 1633 00:00[root@probe root]#
Now that we've created and installed our custom setup on a web server, lets try it out. Let's reboot the Network Security Toolkit probe, remove the thumbdrive, log back in, and then invoke lnstcustom in the following manner:
[root@probe root]#lnstcustom test http://192.168.0.17/test.tgz... Lots of output - X finally comes back up ...
That's about all there is to it. We now have our custom
setup.sh script available on the
network.
You should be careful when using this method for loading Network Security Toolkit customization scripts. NEVER load someone else's customization script as you are handing them the keys to your system. You should also avoid placing any plain text passwords or security sensitive data in customization scripts placed on the network (as it will probably be possible for someone to find your files and view them).