Keylocker 0.2.0.5
-----------------


About the project
-----------------
Keylocker was written originally for a member of an Australian forum for school administrators. No one could suggest a program that would prevent the continued use of computers during events such as fire alarms, so Keylocker was written (badly at first).


Quick Guide
-----------
keylocker2.exe is the client program. Simply run it from login scripts or whatever. It will need to be run as the currently logged in user to display the warning/message screens, so run it as a startup item from wherever you prefer to start such things.

keylocker2console.exe is the Keylocker2 Command Console. This program sends out control commands to the clients. This is where messages, timeouts, etc are set. Read on for how to use it....


Differences from previous versions
----------------------------------
Added support for taking a screenshot before locking. Currently this option isnt saved in the configs.
Screenshots are saved in the same directory the client runs from.


Command Line Options
--------------------------
This version supports 2 command line options (one at a time only):
/lock filename.conf	- Send a lock command using the options from "filename.conf".
			  filename.conf should refer to a config file created using the
			  console.
/unlock filename.conf	- Unlocks based on the content of the config file given.

If one of these is used, and successful, a message is given and then the console exits.
If neither is specified, the console will attempt to load default values from "keylocker2.conf" in the same directory as the exe. You can set your own prefered defaults by saving over this file.




Keylocker2 Command Console Interface
------------------------------------
The options available here are:
Warning Message - The text that will appear in the client when it is locked.
		  This is mostly limited to screen space on the client, though may
		  have some length limit (Im not sure).
Text Colour	- Text colour. Click the coloured button to choose a colour
Back Colour	- Background colour. Same as above, except background colour
Font Size	- The size the client will show the text.
Take Screenshot - If ticked, the client will take a screenshot before bringing up the
		  message on the screen. This screenshot will be saved using the 
		  computer name and the date and time. It is saved as a bitmap in the
		  directory the client was run from.
Timeout 	- Time in seconds that the client will be locked. Max 65535 seconds.
Target Computer	- Specify specific computer(s) to lock. You can use wildcards (* or ?)
		  or you can seperate names with a comma, or both. (ie. "room1-*,room2-*).
Target User	- Can be used instead of the computer name. Only one username, and no
		  wildcards here though. Meant to target one specific user, not groups.
Broadcast Address - You can specify your subnet's broadcast address here (eg 192.168.1.255).
		  This option must be correct for the commands to be sent correctly.
Lock Button	- Sends a lock command to the host specified in the target box.
Unlock Button	- Sends an unlock command to the target. Other settings are ignored.


File Menu Options
--------------------------
Open Config	- Quite obviously, this opens a previously saved config file.
Save Config	- Saves files for later opening.
Quit		- Exits the Command Console program.


Colour Selection
--------------------------
Colour selection is done using the Windows Common Dialog Colour Picker. It should be fairly familiar to most people.


Known Problems
--------------------------
Client may crash if it receives some bad values. I have tried to prevent this.
Font size text box does no value checks. It will allow silly values (ie 1000pt font)
Documentation is pretty ordinary (feel free to fix and improve) :P
Attempting to load a file that wasnt a config file saved by this program will most likely crash the console program.
Lack of security with regards to controlling the client. Anyone with access to the console program can control the clients. Anyone with access to VB could in theory also write thier own controller.

Questions?
------------------
Any questions should be asked on the Keylocker mailing list. See http://lists.sourceforge.net/lists/listinfo/keylocker-users to subscribe.


Copyright Tim Bates 2005.