So this concludes the documentation accompanying this software. As we have seen above, ComLog is a tool that can empowers network administrators into knowing what is going on with the command prompts on their machines, and can use it to determine the actions of an attacker. Since only what is going through the command prompt is logged, I think this is not too intrusive to be placed eventually on every PC on a network, since regular office employees rarely have a professional reason to justify the use of the command prompt. ComLog being an emulator, it does show some shortcomings when compared with the real McCoy, but it should not prevent its use in most cases. However, fine knowledge of these shortcomings could help an intruder to determine that he is being watched, and more effort should be put into improving the program even more. A lot has been done recently to improve this, such as improving LogAgent to handle these logs and to make sure that ComLog has a LogAgent-compatible log file storing strategy, but more could be done to improve concealing. Finally, the source code is presented in Appendix A, and a sample session is showed as it appears on the console (Appendix B) and in the history.txt log file (Appendix C). The code should be easy to read, as I used comprehensive variable and procedure names, and I made a lot of comments along the code.
5. To Install
Appendix A. Source code
Table of contents