From 1c781ce2fb035bc5a983433b39a43f3ef2ddfb1f Mon Sep 17 00:00:00 2001 From: nanotube Date: Wed, 7 Sep 2005 15:21:13 +0000 Subject: [PATCH] changed some layout, added future features section, and overall purpose. --- html/index.html | 50 ++++++++++++++++++++++++++++++++++++++------- html/stylesheet.css | 10 ++++----- 2 files changed, 48 insertions(+), 12 deletions(-) diff --git a/html/index.html b/html/index.html index bab4b8f..77114bf 100644 --- a/html/index.html +++ b/html/index.html @@ -1,23 +1,26 @@ - PyKeylogger + PyKeylogger - The Universal Backup Solution -
@@ -28,6 +31,13 @@ I threw it together one day after not being able to find a simple and trustworthy (as in, source available) keylogger for windows.

+

+ My goal is to create a universal backup solution for everything you type. We have all + at one time or another accidentally closed that word or notepad file without saving. We have + all lost form data on the web after it failed to submit properly. Not even mentioning the + everpresent threat of computer crash. PyKeylogger logs everything you + type, so you can recover your text of anything you type in any application. +

Since PyKeylogger is available as a simple python source file, there are no trust issues with using it - you can just look at the source yourself and make sure that it does exactly @@ -41,7 +51,7 @@

iconDownload

You can download PyKeylogger from the + href="http://sourceforge.net/project/showfiles.php?group_id=147501">the SourceForge download page.

@@ -78,7 +88,8 @@

Since the file's extension is ".pyw", it runs without a console window in the background, if you just double-click the file. If you want to see the console (to see error output, e.g.), - just rename the file with ".py" extension, or run it from command line with "python keylogger.pyw" command. + just rename the file with ".py" extension, or run it from command line with + 

python keylogger.pyw

Controlling pykeylogger:

@@ -135,6 +146,27 @@ so you will have to make a copy of the logfile and open the copy with wordpad, rather than open the logfile directly.

+ +

icon Future direction [Features planned]

+

+ Currently, the log file just has everything dumped into it as keyboard input is received. + This means that when you type something in say, notepad, then alt-tab into word, then write an email, + then come back to notepad, the log file has all that input mixed in, so while it is not lost, it is hard + to retrieve in "original condition". +

+

+ I plan to enhance the logging capability so that it splits the keyboard input by window, and then create + a log viewer, where you can search by date, application name, and window title. So that you can, for example, + say "show me what I typed in all notepad windows yesterday", or "show me what I typed in word document titled 'some stuff'". +

+

+ Another feature I plan for the log viewer is to have an option to parse the backspaces and arrow keys to recreate + the final output, rather than have a bunch of [Backspace] and [LeftArrow] text in the log. Of course, if you want that + to be particularly useful, you have to try to refrain from using the mouse to reposition your cursor :). +

+ Any other ideas, or contributions to the code, are highly welcomed. +

+

icon Where can I ask more questions?

@@ -147,7 +179,8 @@

How can I help out?

If you're a programmer, please feel free to hack around in PyKeylogger code, - to add features, or anything else you would like. + to add features, or anything else you would like. Get the latest src package, or just pull + the latest release (or, if you are feeling daring, HEAD) from CVS.

If you're not a programmer, you could file bug reports or feature requests. @@ -155,6 +188,9 @@

Any contributions will be gladly accepted as patches at sourceforge.

+ + + Last changed: Sep 5 2005 14:27