FOREWORD

    The term "privacy invasion" is 'invented' by OCY, I (sincerely) do not know what they call it out there. Anyway, this is the text for poor but mischievious programmers who want to play James Bond. Why? Because as programmers, we don't have to fork out tonnes of money to buy those 'spy' softwares with limited functions. In fact, being armed with the right knowledge, programmers can always write the 'spy' softwares, taylor-made for themselves. :)

    In this idiot's guide, good OCY intends to give just enough knowledge / reference material for privacy invasion programming. Although given the name "Idiot's Guide", it is not meant for idiots. :) Well, as a self-taught programmer, I will present all the example source codes in the only 2 languages that I know: Visual Basic / QBasic, and Win32 assembly language.

    After OCY researched around the net a long time ago, looking at what the commerial 'spy' softwares are offering, I categorised privacy invasion (using computers) into the following: (what they offer is roughly the following )

    Keyboard logging
    Process (program) logging
    Web activity logging
    Password windows ( those edit boxes with the ******'s )
    Browser cache search

    Those categories is divided into 3 levels ( says good OCY ):

    - Beginner: Browser cache searching, passsword windows
    - Intermediate: Keyboard logging, processs executionn (intermediate)
    - Advanced: Web activity logging and proocess execution (advanced)

    OCY labelled the first as "Beginner" because you don't need a lot of extra knowledge to write a program to perform the task. For the intermediate group, many people do not have of knowledge / experience in that aspect of programming. Finally, the great and noble Advanced level - you need knowledge which is undocumented by Micro$oft, and assembly language is a stipulated skill.

    Well, a note to all readers: good OCY is always encouraging creativity, hence don't get too dependent on the example source codes, 'cos the most important thing is to understand the theory. After having a strong grasp of the theory, imaginations run wild... imagine someone get caught viewing porn by you, or you just simply know every single e-mail your friend typed to his girlfriend... hahahahahahahaha.... ( and plus a lot of sniggering ). And for those who want to give suggestions/comments, you are always welcomed, but once again... NO INSULTS. ( I do deserve some respect, don't I? )

    And this is the end of the loooooong and boring foreword. Happy learning and programming!

p/s: If you don't want to sore your eyes to blindness, print out these pages... 'cos reading the example codes on a computer screen is torturing... :)

-by the unorthodox OCY