b01xb / klog-sharp Goto Github PK

The log file might contain passwords -- delete option from within the
program should wipe the file (overwrite with 0's), not just delete it. 

When just deleting, recovery is possible (actually easy), and this could be
a major security vulnerability.

This is not as critical for screenshot files as it is for the main text log.

What steps will reproduce the problem?
1. Start Klog
2. Double click the tray icon [password box then appears]
3. Type password

Expected: Typed password goes into the box. 

Actual: Focus is somewhere else, keystrokes are lost.

What steps will reproduce the problem?
1. Double click the tray icon
2. Cancel out of password dialog

Expected: hooks are restored, logging continues as normal

Actual: ???

Hi, is it possible to take into account another languages when logging keyboard 
strokes ?


What steps will reproduce the problem?
1.Change the keyboard language
2.Type in any program
3.Open the main log file
4.you will see the letters still written in English

Different types of clicks should appear differently:

1. Different message in the log.
2. Different type of circle in the screenshot.

Double-click we have now is intuitive, but there needs to be a context menu
(with the same effect) and a tooltip to help discoverability.

Spawn a monitor task to prevent killing the app from the task manager.

This should be configurable as an option within the app / config file,
perhaps not enabled by default.

1. When the app starts, start Monitor.
2. From the app, check periodically if Monitor is running. If not, restart.
3. From Monitor, check periodically if the app is running. If not, restart.
4. When exiting off the app:
  1. Turn off the checking for Monitor
  2. Terminate the Monitor
  3. Terminate the app itself.

This seems just slightly evil, but does help the intended purpose
(localhost monitoring).

State of checkboxes on the main form (mouse/keyb logging enabled) should be
automatically loaded on startup and saved on change.