|
Type/Code/Value interpretations for evbug module
In dmesg with the evbug module added to the kernel, how do I translate the Type/Code/Value values to keypresses and mouse moves? I think that these values correspond to keypresses, but I may be (probably am) wrong.
For some background, I am trying to write a keylogger for linux, for non-cracking, non-invasive, scientific-study-related reasons (see below for explanation). The way I have thought of thus far is to add the evbug module to the kernel, and then read the evbug logs using dmesg and filter for lines that contain the word evbug. That said, I need to understand the output, and lines like the following are confusing me.
[ 8753.328583] evbug.c: Event. Dev: input5, Type: 0, Code: 0, Value: 0
[ 8754.250077] evbug.c: Event. Dev: input5, Type: 4, Code: 4, Value: 28
[ 8754.250119] evbug.c: Event. Dev: input5, Type: 1, Code: 28, Value: 1
[ 8754.250142] evbug.c: Event. Dev: input5, Type: 0, Code: 0, Value: 0
Is there a good way of translating these values to keypresses?
The reason I would like the keylogger is to record input to a program that processes perfusion CT data, in order to later replicate, keystroke by keystroke, the input to the program for slightly different data. I am working in a radiology research department, and for some odd unknowable reason, they don't want me downloading a keylogger and installing it on a computer that also contains confidential information. A short script that I have written and can explain to them is alright, though, especially if it just takes output from dmesg and interprets it.
Thanks!
anjruu
|