superr4y / logkeys Goto Github PK

What steps will reproduce the problem?
1. Compile and install program
2. Run program like 'logkeys -s -o logfile -d /dev/input/event9'
3.

What is the expected output? What do you see instead?
Expected is that there would be an output log file. I don't see any log
file being created. There's also 100% CPU usage.

What version of the product are you using? On what operating system?
0.1.0 on slackware64 13.0

Please provide any additional information below.

I am using a USB keyboard listed as:

I: Bus=0003 Vendor=045e Product=00b0 Version=0111
N: Name="Microsoft Microsoft® Digital Media Pro Keyboard"
P: Phys=usb-0000:00:1a.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/input/input9
U: Uniq=
H: Handlers=kbd event9 
B: EV=120013
B: KEY=1000000000007 ff800000000007ff febeffdff3cfffff fffffffffffffffe
B: MSC=10
B: LED=107

I: Bus=0003 Vendor=045e Product=00b0 Version=0111
N: Name="Microsoft Microsoft® Digital Media Pro Keyboard"
P: Phys=usb-0000:00:1a.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.1/input/input10
U: Uniq=
H: Handlers=kbd event10 js0 
B: EV=10001f
B: KEY=837fff002c3027 bf00444400000000 c00000000000001 10f848a27c007
ffff7bfad941dfff febeffdfffefffff fffffffffffffffe
B: REL=40
B: ABS=ffffff01000701ff
B: MSC=10

I know another keylogger works with event9, so this one should too, it also
does not work with event10.

Not sure if this will help, but here's the gdb output:
bash-3.1# gdb -args logkeys -s -o logfile -d /dev/input/event9
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-slackware-linux"...
(gdb) start
Breakpoint 1 at 0x401f20
Starting program: /home/demonslayer/tmp/logkeys-0.1.0/src/logkeys -s -o
logfile -d /dev/input/event9
0x0000000000401f20 in main ()
Current language:  auto; currently asm
(gdb) continue
Continuing.
^C
Program received signal SIGINT, Interrupt.
0x0000000000402e00 in main ()

I had to quit it because it was stuck with Ctrl-C.

I suspect that it may be a problem with USB keyboards ?

Fixed Layout for it_IT keyboard layout

Option to have keylog emailed in the background.  Either time based or
logfile size to determine when emailed. Something like this would be very
handy for those away from the computer.

logkeys uses shell scripting to extract certain information about the
system, e.g.

 "grep Name /proc/bus/input/devices | grep -nE '[Kk]eyboard|kbd'"

command string is used to extract event device number.

As logkeys is installed setuid root, the attacker could

 $ mv malicious_file.sh /home/attacker/attack_dir/grep
 $ PATH=/home/attacker/attack_dir:$PATH

and then run logkeys, which will upon execution of above command string run
the attackers malicious file with root permissions.


Proposed fix:

Use absolute program paths, e.g.

 "/bin/grep Name /proc/bus/input/devices | /bin/grep -nE '[Kk]eyboard|kbd'"


Also, logkeys shouldn't be setuid root, instead setuid the helper scripts
(lkl, lklk), which can also be run by anyone, but only configured by system
owner.

What steps will reproduce the problem?
1. Compiling

cd build
../configure
make


imerelli@rambo:~/logkeys-0.1.1a/build$ make
make  all-recursive
make[1]: Entering directory `/ldaphome/imerelli/logkeys-0.1.1a/build'
Making all in src
make[2]: Entering directory `/ldaphome/imerelli/logkeys-0.1.1a/build/src'
g++ -DHAVE_CONFIG_H -I. -I../../src -I..     -Wall -O3 
-DSYS_CONF_DIR=\"/usr/local/etc\" -MT logkeys.o -MD -MP -MF .deps/logkeys.Tpo 
-c -o logkeys.o ../../src/logkeys.cc
In file included from ../../src/logkeys.cc:58:
../../src/args.cc:49:50: error: invalid suffix "b1" on integer constant
../../src/args.cc:50:50: error: invalid suffix "b10" on integer constant
../../src/args.cc:51:50: error: invalid suffix "b100" on integer constant
../../src/args.cc:52:50: error: invalid suffix "b1000" on integer constant
../../src/args.cc:53:50: error: invalid suffix "b10000" on integer constant
../../src/args.cc:54:50: error: invalid suffix "b100000" on integer constant
../../src/args.cc:76:16: error: invalid suffix "b1" on integer constant
../../src/args.cc:78:16: error: invalid suffix "b1000" on integer constant
../../src/args.cc:84:16: error: invalid suffix "b10000" on integer constant
../../src/args.cc:98:16: error: invalid suffix "b100000" on integer constant
../../src/logkeys.cc:370:37: error: invalid suffix "b1" on integer constant
../../src/logkeys.cc:384:51: error: invalid suffix "b1" on integer constant
../../src/logkeys.cc:388:61: error: invalid suffix "b1" on integer constant
../../src/logkeys.cc:393:23: error: invalid suffix "b1" on integer constant
../../src/logkeys.cc:459:20: error: invalid suffix "b100" on integer constant
../../src/logkeys.cc:523:27: error: invalid suffix "b10" on integer constant
../../src/logkeys.cc:537:26: error: invalid suffix "b100" on integer constant
../../src/logkeys.cc:577:28: error: invalid suffix "b10" on integer constant
make[2]: *** [logkeys.o] Error 1
make[2]: Leaving directory `/ldaphome/imerelli/logkeys-0.1.1a/build/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/ldaphome/imerelli/logkeys-0.1.1a/build'
make: *** [all] Error 2


What version of the product are you using (`logkeys --help`)?

logkeys-0.1.1a

On what operating system?

Ubuntu 8.04

Hi -

If you could convert 

<LShft> to <Shft_L>
<RShft> to <Shft_R>
<LAlt> to <Alt_L>
<RAlt> to <Alt_R>
<LCtrl> to <Control_L>
<RCtrl> to <Control_R>

So it would comply to xmacro convention.
KeyStrPress Alt_L
KeyStrPress Control_L
KeyStrPress Right
KeyStrRelease Right
KeyStrRelease Alt_L
KeyStrRelease Control_L
MotionNotify 298 10
ButtonPress 1
ButtonRelease 1
KeyStrPress p
KeyStrRelease p
KeyStrPress a
KeyStrRelease a
KeyStrPress n
KeyStrRelease n
KeyStrPress Return
KeyStrRelease Return
KeyStrPress Control_L
KeyStrPress Shift_L
KeyStrPress u
KeyStrRelease u
KeyStrRelease Shift_L
KeyStrRelease Control_L

Here are the steps to reproduce:

1. start logkeys with USB keyboard connected to computer
2. disconnect USB keyboard
3. reconnect USB keyboard
4. logkeys stops logging
5. stop logkeys
6. restart logkeys
7. logkeys runs, but does not log any keystrokes

I did some detective work to find out why this is.

The problem is in the code to detect the input device. After reconnecting the 
USB keyboard, the event numbers in /proc/bus/input/devices are no longer in 
sequential order, but for the input device detection to work they must be 
sequential. This is why the wrong event number is selected for reading keyboard 
events.

Attached below is a copy of my /proc/bus/input/devices file after reconnecting 
the USB keyboard. As you can see, the 6th item has event3, not event5, as the 
input device detection code assumes.

I'm working on a new input device detection routine, which will work when USB 
keyboards are reconnected. If you are interested, I would be happy to send it 
to you when finished.

--
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
U: Uniq=
H: Handlers=kbd event0 
B: EV=3
B: KEY=10000000000000 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: EV=3
B: KEY=10000000000000 0

I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=mouse0 event2 
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3

I: Bus=0003 Vendor=046d Product=c054 Version=0111
N: Name="Logitech USB Optical Mouse"
P: Phys=usb-0000:00:1a.2-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:1a.2/usb5/5-2/5-2:1.0/input/input5
U: Uniq=
H: Handlers=mouse1 event5 
B: EV=17
B: KEY=ff0000 0 0 0 0
B: REL=143
B: MSC=10

I: Bus=0001 Vendor=10ec Product=0888 Version=0001
N: Name="HDA Digital PCBeep"
P: Phys=card0/codec#0/beep0
S: Sysfs=/devices/pci0000:00/0000:00:1b.0/input/input6
U: Uniq=
H: Handlers=kbd event6 
B: EV=40001
B: SND=6

I: Bus=0003 Vendor=04f2 Product=0760 Version=0111
N: Name="Chicony USB Keyboard"
P: Phys=usb-0000:00:1a.2-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1a.2/usb5/5-1/5-1:1.0/input/input15
U: Uniq=
H: Handlers=kbd event3 
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7

I: Bus=0003 Vendor=04f2 Product=0760 Version=0111
N: Name="Chicony USB Keyboard"
P: Phys=usb-0000:00:1a.2-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:1a.2/usb5/5-1/5-1:1.1/input/input16
U: Uniq=
H: Handlers=kbd event4 
B: EV=13
B: KEY=2000000 387ad801d001 1e000000000000 0
B: MSC=10

What steps will reproduce the problem?
1.turn on logkeys, it starts normally
2.turn off logkeys by typing "gkeys --kill" results in the following text
3."kofjeya --jikk"; which when you compare the top row letters are getting 
correctly mapped (row starting with q), but second row letters are off by one.

What is the expected output?gkeys --kill
What do you see instead?kofjeya --jikk


What version of the product are you using (`logkeys --help`)?0.1.1a
On what operating system?ubuntu 10.04


Please provide any additional information below.
If applicable, also attach contents of /proc/bus/input/devices, the output
of command `dumpkeys -n > dumpkeys.output`, and any
other relevant files.

When I try to open dumpkeys.output with gedit I get an error, can't recognize 
encoding. It then gives me a choice of "Current Locale (UTF-8)" and "Western 
(ISO-8859-15)", The Current Locale does not work, but the Western does for 
correctly opening the file.

Also, I am on an HP laptop (pavillion)

What steps will reproduce the problem?
1.When I try to install it shows that:
root@jose-desktop:~/Videos/logkeys-0.1.0/build# ../configure
1.When I try to install it shows that:
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking for C++ compiler default output file name... 
2.After
root@jose-desktop:~/Videos/logkeys-0.1.0/build# make
make: *** No se especificó ningún objetivo y no se encontró ningún
makefile.  Alto.

3.root@jose-desktop:~/Videos/logkeys-0.1.0/build# make install
make: *** No hay ninguna regla para construir el objetivo `install'.  Alto.
I'm a new user with Linux Ubuntu. What happen? How i solved this?

What steps will reproduce the problem?
1.if i run lkl all i get is <RShift> and LShift and so on with backspace,
but if i run logkeys --start --output key.log it outputs fine, and im not
totally concinered on how to run the service.


What is the expected output? What do you see instead?
When Running logkeys --start --output key.log and i do Shift <capital
letter> it doesnt record the capital letter at all.

What version of the product are you using? On what operating system?
Downloaded the latest version using it on Fedora Core 12.

Please provide any additional information below.
If applicable, also attach contents of /proc/bus/input/devices and any
other relevant files.

File Devices is attached


Thank you for your help

What steps will reproduce the problem?
1.I do not know installed ok
2.
3.

What is the expected output? What do you see instead?
to have a log file with something in it

What version of the product are you using? On what operating system?

logkeys-0.1.0      bt4  laptop install
Please provide any additional information below.


locale 

LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

What steps will reproduce the problem?
1. then lines wich containe than 5 characters have a error message
but it work perfectly :)
What is the expected output?
What do you see instead?


What version of the product are you using (`logkeys --help`)? latest version
On what operating system? linux fedora

Cmon man.. I didn't found any place to comment on this project so please 
forgive me for writing it here....

This is seriously awesome man... Easy to install and very effective....
A very genius project...

********* - You get 9/10 from me

please man.. contact me... 

[email protected]

$ sudo logkeys --start --output test.log
logkeys: LC_CTYPE locale must be of UTF-8 type
$ locale
LANG=it_IT.UTF-8
LC_CTYPE="it_IT.UTF-8"
LC_NUMERIC="it_IT.UTF-8"
LC_TIME="it_IT.UTF-8"
LC_COLLATE="it_IT.UTF-8"
LC_MONETARY="it_IT.UTF-8"
LC_MESSAGES="it_IT.UTF-8"
LC_PAPER="it_IT.UTF-8"
LC_NAME="it_IT.UTF-8"
LC_ADDRESS="it_IT.UTF-8"
LC_TELEPHONE="it_IT.UTF-8"
LC_MEASUREMENT="it_IT.UTF-8"
LC_IDENTIFICATION="it_IT.UTF-8"
LC_ALL=


What version of the product are you using (`logkeys --help`)? 0.1.1a
On what operating system? Debian Squeeze

Hi,

Have just tried this out on Ubuntu 9.10 and it seems to work as advertised.
Thanks. 

I just thought I'd suggest a feature: you might like to consider capturing
the Window Title to give some context to the typing eg. 
 12th Feb 2010, 23:08 Firefox - Google Search: keylogger

I'm not a programmer, so I don't know if this is a big job or a two-liner,
but it would certainly be useful. 

Thanks again. 

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? install logkeys
What do you see instead?

josh@josh-laptop:~/src/logkeys-0.1.0/build$ ../configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking for C++ compiler default output file name... 
configure: error: in `/home/josh/src/logkeys-0.1.0/build':
configure: error: C++ compiler cannot create executables
See `config.log' for more details.
josh@josh-laptop:~/src/logkeys-0.1.0/build$ make
make: *** No targets specified and no makefile found.  Stop.
josh@josh-laptop:~/src/logkeys-0.1.0/build$ ^C
josh@josh-laptop:~/src/logkeys-0.1.0/build$ 


What version of the product are you using (`logkeys --help`)? logkeys0.1.0
On what operating system?
ubuntu 9

sorry not 100% ubuntu,terminal and computer in general literate. 

would love and really really appreciate some help!

Portuguese Map

Providing a keymap file that doesn't exist makes logkeys segfaul.

What steps will reproduce the problem?
1. buy a wireless cherry sirius XT keyboard + mouse
2. start llk

What is the expected output?
expected the program to run

What do you see instead?
<<
logkeys: Couldn't determine keyboard device. :/
logkeys: Please post contents of your /proc/bus/input/devices file as a new bug 
report. Thanks!
>>

What version of the product are you using (`logkeys --help`)?
On what operating system?
logkeys version: 0.1.1a
on
Ubuntu 10.04

Please provide any additional information below.
If applicable, also attach contents of /proc/bus/input/devices, the output
of command `dumpkeys -n > dumpkeys.output`, and any
other relevant files.

was resolved when i started the program with the -d /dev/input/event3 switch 

/proc/bus/input/devices:

cat /proc/bus/input/devices
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0 
B: EV=3
B: KEY=10000000000000 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: EV=3
B: KEY=10000000000000 0

I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=mouse0 event2 
B: EV=7
B: KEY=70000 0 0 0 0
B: REL=3

I: Bus=0003 Vendor=046a Product=0100 Version=0100
N: Name="MLK Wireless Desktop"
P: Phys=usb-0000:00:02.0-8/input0
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb2/2-8/2-8:1.0/input/input3
U: Uniq=
H: Handlers=kbd event3 
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=046a Product=0100 Version=0100
N: Name="MLK Wireless Desktop"
P: Phys=usb-0000:00:02.0-8/input1
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb2/2-8/2-8:1.1/input/input4
U: Uniq=
H: Handlers=kbd mouse1 event4 
B: EV=1f
B: KEY=837fff002c3027 bf00444400000000 1f0001 f848a27c000 667bfad941dfed 
9e000000000000 0
B: REL=1c3
B: ABS=100000000
B: MSC=10

I: Bus=0001 Vendor=10ec Product=0888 Version=0001
N: Name="HDA Digital PCBeep"
P: Phys=card0/codec#0/beep0
S: Sysfs=/devices/pci0000:00/0000:00:07.0/input/input5
U: Uniq=
H: Handlers=kbd event5 
B: EV=40001
B: SND=6

Here is Slovak keymap described as "Slovak QWERTY"

What steps will reproduce the problem?
1.
2.
3.

What is the expected output?
What do you see instead?


What version of the product are you using (`logkeys --help`)?
On what operating system?


Please provide any additional information below.
If applicable, also attach contents of /proc/bus/input/devices, the output
of command `dumpkeys -n > dumpkeys.output`, and any
other relevant files.

What steps will reproduce the problem?
1.Compile the program
2.
3.

What is the expected output?
The compilation not end god
What do you see instead?

ON ./CONFIGURE
--------------------------------------------------
jotadeath@jotadeath-desktop:~/Desktop/logkeys-0.1.0$ ./configure          

checking for a BSD-compatible install... /usr/bin/install -c              

checking whether build environment is sane... yes                         

checking for a thread-safe mkdir -p... /bin/mkdir -p                      

checking for gawk... gawk                                                 

checking whether make sets $(MAKE)... yes                                 

checking for g++... g++                                                   

checking for C++ compiler default output file name... a.out               

checking whether the C++ compiler works... yes                            

checking whether we are cross compiling... no                             

checking for suffix of executables...                                     

checking for suffix of object files... o                                  

checking whether we are using the GNU C++ compiler... yes                 

checking whether g++ accepts -g... yes                                    

checking for style of include used by make... GNU                         

checking dependency style of g++... gcc3                                  

checking whether make sets $(MAKE)... (cached) yes                        

checking for grep... yes                                                  

checking for pgrep... yes                                                 

checking for dumpkeys... yes                                              

checking for /dev/input... yes                                            

checking for /proc/bus/input/devices... yes                               

checking how to run the C++ preprocessor... g++ -E                        

checking for grep that handles long lines and -e... /bin/grep             

checking for egrep... /bin/grep -E                                        

checking for ANSI C header files... yes                                   

checking for sys/types.h... yes                                           

checking for sys/stat.h... yes                                            

checking for stdlib.h... yes                                              

checking for string.h... yes                                              

checking for memory.h... yes                                              

checking for strings.h... yes                                             

checking for inttypes.h... yes                                            

checking for stdint.h... yes                                              

checking for unistd.h... yes                                              

checking cstdio usability... yes                                          

checking cstdio presence... yes                                           

checking for cstdio... yes                                                

checking cerrno usability... yes                                          

checking cerrno presence... yes                                           

checking for cerrno... yes                                                

checking cstring usability... yes                                         

checking cstring presence... yes                                          

checking for cstring... yes                                               

checking sstream usability... yes                                         

checking sstream presence... yes                                          

checking for sstream... yes                                               

checking cstdlib usability... yes                                         

checking cstdlib presence... yes                                          

checking for cstdlib... yes                                               

checking csignal usability... yes                                         

checking csignal presence... yes                                          

checking for csignal... yes                                               

checking for unistd.h... (cached) yes                                     

checking getopt.h usability... yes                                        

checking getopt.h presence... yes                                         

checking for getopt.h... yes                                              

checking sys/file.h usability... yes                                      

checking sys/file.h presence... yes                                       

checking for sys/file.h... yes                                            

checking linux/input.h usability... yes                                   

checking linux/input.h presence... yes                                    

checking for linux/input.h... yes                                         

checking for stdbool.h that conforms to C99... yes                        

checking for _Bool... no                                                  

checking for inline... inline                                             

checking for pid_t... yes                                                 

checking for size_t... yes                                                

checking for error_at_line... yes                                         

checking vfork.h usability... no                                          

checking vfork.h presence... no                                           

checking for vfork.h... no                                                

checking for fork... yes                                                  

checking for vfork... yes                                                 

checking for working fork... yes                                          

checking for working vfork... (cached) yes                                

checking for geteuid... yes                                               

checking for getcwd... yes                                                

checking for memset... yes                                                

checking for setlocale... yes                                             

checking for strerror... yes                                              

checking for fprintf... yes                                               

checking for getopt_long... yes                                           

checking for fopen... yes                                                 

checking for sscanf... yes                                                

checking for fscanf... yes                                                

checking for getpid... yes                                                

checking for fclose... yes                                                

checking for remove... yes                                                

checking for kill... yes                                                  

checking for strlen... yes                                                

checking for strcat... yes                                                

checking for strcpy... yes                                                

checking for strncat... yes                                               

checking for freopen... yes                                               

checking for feof... yes                                                  

checking for fgets... yes                                                 

checking for atoi... yes
checking for sigaction... yes
checking for fork... (cached) yes
checking for setsid... yes
checking for open... yes
checking for close... yes
checking for flock... yes
checking for write... yes
checking for umask... yes
checking for setgid... yes
checking for setuid... yes
checking for strftime... yes
checking for localtime... yes
checking for fflush... yes
checking for read... yes
checking for sleep... yes
checking for time... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating man/Makefile
config.status: creating scripts/Makefile
config.status: creating config.h
config.status: executing depfiles commands
------------------------------------

ON MAKE

------------------------------------

jotadeath@jotadeath-desktop:~/Desktop/logkeys-0.1.0$ make
make  all-recursive
make[1]: se ingresa al directorio `/home/jotadeath/Desktop/logkeys-0.1.0'
Making all in src
make[2]: se ingresa al directorio `/home/jotadeath/Desktop/logkeys-0.1.0/src'
g++ -DHAVE_CONFIG_H -I. -I..     -Wall -O3 -MT logkeys.o -MD -MP -MF
.deps/logkeys.Tpo -c -o logkeys.o logkeys.cc
mv -f .deps/logkeys.Tpo .deps/logkeys.Po
g++  -Wall -O3   -o logkeys logkeys.o
make[2]: se sale del directorio `/home/jotadeath/Desktop/logkeys-0.1.0/src'
Making all in man
make[2]: se ingresa al directorio `/home/jotadeath/Desktop/logkeys-0.1.0/man'
make[2]: No se hace nada para `all'.
make[2]: se sale del directorio `/home/jotadeath/Desktop/logkeys-0.1.0/man'
Making all in scripts
make[2]: se ingresa al directorio
`/home/jotadeath/Desktop/logkeys-0.1.0/scripts'
make[2]: No se hace nada para `all'.
make[2]: se sale del directorio `/home/jotadeath/Desktop/logkeys-0.1.0/scripts'
make[2]: se ingresa al directorio `/home/jotadeath/Desktop/logkeys-0.1.0'
make[2]: No se hace nada para `all-am'.
make[2]: se sale del directorio `/home/jotadeath/Desktop/logkeys-0.1.0'
make[1]: se sale del directorio `/home/jotadeath/Desktop/logkeys-0.1.0'
-----------------------------------------------------------------


What version of the product are you using (`logkeys --help`)?
On what operating system?
Ubuntu 9.10


Please provide any additional information below.

se sale del directorio == out of directory

pleas any explanation

In some instances, the line

 "grep Name /proc/bus/input/devices | grep -nE '[Kk]eyboard|kbd'"

doesn't produce any result, and the parsed int becomes -1, and input device
/dev/input/event-1, which doesn't exist.

This happens when keyboard device doesn't include '[Kk]eyboard|kbd' in its
name, namely some USB hubs.

In the attached devices file, the keyboard device is /dev/input/event4.
Keyboard brand and model:
http://www.enermaxusa.com/catalog/product_info.php?cPath=28_48&products_id=156


Proposed fix:

If the parsed int is -1 (kbd not yet found), search the output for 'HID' ?

  "grep Name /proc/bus/input/devices | grep -nE 'HID'"

When i type gmail and press CTRL+ENTER and view mt log it shows output as 
   䰊杯楧杮猠慴瑲摥⸠⸮ਊ〲〱〭ⴲ㠱ㄠ㨴㜴㔺⬱㔰〳㸠映摥牯੡〲〱〭ⴲ㠱ㄠ㨴㠴ㄺ⬱㔰〳㸠ਠ
〲〱〭ⴲ㠱ㄠ㨴㠴㌺⬶㔰〳㸠爠潯ੴ〲〱〭ⴲ㠱ㄠ㨴㠴㐺⬳��
�〳㸠甠畢瑮ੵ〲〱〭ⴲ㠱ㄠ㨴㠴㐺⬶㔰
〳㸠爠潯ੴ〲〱〭ⴲ㠱ㄠ㨴㠴㐺⬹㔰〳㸠甠畢瑮畹㈊㄰ⴰ㈰��
�‸㐱㐺㨸ㄵ〫㌵‰‾潲瑯㈊㄰ⴰ㈰ㄭ‸
㐱㐺㨸㜵〫㌵‰‾扵湵畴㈊㄰ⴰ㈰ㄭ‸㐱㐺㨸㤵〫㌵‰‾慫��
�楨正㈊㄰ⴰ㈰ㄭ‸㐱㐺㨹㐰〫㌵‰‾楬畮੸
〲〱〭ⴲ㠱ㄠ㨴㤴〺⬷㔰〳㸠欠牡桴捩੫〲〱〭ⴲ㠱ㄠ㨴㤴��
�⬵㔰〳㸠映摥牯੡〲〱〭ⴲ㠱ㄠ㨴㤴ㄺ
⬸㔰〳㸠猠摵慰獳摥㰠捂卫㹰䈼正灓㰾捂卫㹰摷欠牡桴捩��
�〲〱〭ⴲ㠱ㄠ㨴㈵〺⬳㔰〳㸠映
摥牯੡〲〱〭ⴲ㠱ㄠ㨴㈵ㄺ⬱㔰〳㸠氠湩硵㈊㄰ⴰ㈰ㄭ‸㐱��
�㨲㘱〫㌵‰‾楬畮੸〲〱〭ⴲ㠱ㄠ㨴㈵ㄺ
⬹㔰〳㸠㰠灕ਾ〲〱〭ⴲ㠱ㄠ㨴㈵㈺⬳㔰〳㸠㰠灕ਾ〲〱〭��
�㠱ㄠ㨴㈵㌺⬱㔰〳㸠㰠敄㹬煳㈊㄰ⴰ
㈰ㄭ‸㐱㔺㨴㈱〫㌵‰‾䈼正灓㰾卒晨㹴䐼汥ਾ〲〱〭ⴲ㠱��
�㨴㔵ㄺ⬷㔰〳㸠㰠卒晨㹴䐼汥ਾ〲〱〭
ⴲ㠱ㄠ㨴㔵㈺⬴㔰〳㸠映㈊㄰ⴰ㈰ㄭ‸㐱㔺㨶㄰〫㌵‰‾獬��
�䈼正灓㰾捂卫㹰䈼正灓㰾捂卫㹰䈼
正灓挾⁤慶ੲ〲〱〭ⴲ㠱ㄠ㨴㘵㐺⬰㔰〳㸠挠⁤瘯牡㰯捂卫��
�㈊㄰ⴰ㈰ㄭ‸㐱㔺㨶㔴〫㌵‰‾摣氠㱯
捂卫㹰䈼正灓⼾潬੧〲〱〭ⴲ㠱ㄠ㨴㘵㔺⬰㔰〳㸠氠ੳ〲〱��
�ⴲ㠱ㄠ㨴㜵〺⬸㔰〳㸠挠⁤氯杯㈊㄰
ⴰ㈰ㄭ‸㐱㔺㨷㈱〫㌵‰‾唼㹰䰼晥㹴䰼晥㹴䰼晥㹴䰼晥㹴��
�正灓ਾ〲〱〭ⴲ㠱ㄠ㨴㜵ㄺ⬶㔰〳㸠
挠੤〲〱〭ⴲ㠱ㄠ㨴㜵ㄺ⬹㔰〳㸠挠⁤瘯牡㱥捂卫㹰氯杯㈊��
�ⴰ㈰ㄭ‸㐱㔺㨷㐲〫㌵‰‾獬ⴠ潬歧
祥⹳潬੧〲〱〭ⴲ㠱ㄠ㨴㜵㌺⬵㔰〳㸠挠੤〲〱〭ⴲ㠱ㄠ㨴��
�㐺⬸㔰〳㸠挠⁤支捴猯畱摩㈊㄰ⴰ㈰ㄭ
‸㐱㔺㨷㐵〫㌵‰‾獬ⴠ煳極⹤潣㱭捂卫㹰普㈊㄰ⴰ㈰ㄭ��
�㐱㔺㨸㄰〫㌵‰‾歧畳渠畡楴畬ੳ〲〱〭ⴲ
㠱ㄠ㨵㐰㌺⬹㔰〳㸠猠ੱ〲〱〭ⴲ㠱ㄠ㨵㐰㔺⬰㔰〳㸠猠ੱ��
�〱〭ⴲ㠱ㄠ㨵㔰㈺⬱㔰〳㸠猠ੱ〲〱〭ⴲ㠱
ㄠ㨵㠰ㄺ⬳㔰〳㸠㰠敌瑦㰾捂卫㹰䈼正灓猾摵敧楤⁴支捴��
�畱摩挮屜䈼正灓㰾捂卫㹰䈼
正灓㰾捂卫㹰猯畱摩挮湯੦〲〱〭ⴲ㠱ㄠ㨵㠰㔺⬸㔰〳㸠㰠��
�㰾灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾
灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾��
�㰾灕㰾灕㰾灕㰾灕㰾灕
㰾灕㰾灕㰾灕㰾潄湷㰾潄湷㰾灕㰾⬣㸱䈼正灓㰾⬣㤱㰾䍌牴��
�牦㱭捂卫㹰䈼正灓猾䈼正
灓㰾䍌牴㹬獲摵浲䔼捳ਾ䰊杯楧杮猠潴灰摥愠⁴〲〱〭ⴲ��
�ㄠ㨵ㄱ㌺⬵㔰〳ਊ潌杧湩⁧瑳牡整
⁤⸮ਮ㈊㄰ⴰ㈰ㄭ‸㘱㔺㨳㔴〫㌵‰‾唼㹰㈊㄰ⴰ㈰ㄭ‸㘱��
�㨴㜰〫㌵‰‾敦潤慲㈊㄰ⴰ㈰ㄭ‸㘱㔺㨴ㄱ〫
㌵‰‾楬畮੸〲〱〭ⴲ㠱ㄠ㨶㐵㈺⬰㔰〳㸠㰠卌晨㹴㰣卌晨��
�㰣灕㰾灕㰾灕㰾灕㰾灕㰾潄湷㰾
灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾灕㰾��
�㰾潄湷ਾ〲〱〭ⴲ㠱ㄠ㨶㐵
㌺⬶㔰〳㸠猠摵潰獤⵬牰癯摩牥㈊㄰ⴰ㈰ㄭ‸㘱㔺㨴㘴��
�㌵‰‾畺㱬捂卫㹰䈼正灓㰾捂卫㹰
䈼正灓朾業䈼正灓愾汩挮浯㈊㄰ⴰ㈰ㄭ‸㘱㔺㨴㤵〫㌵‰‾��
�瑃汲琾扵䐼睯㹮㈊㄰ⴰ㈰ㄭ‸㘱
㔺㨵〱〫㌵‰‾䰼瑃汲琾整档畳灰牯晴㱰捂卫㹰牯浵挮浯㈊��
�ⴰ㈰ㄭ‸㘱㔺㨵㌲〫㌵‰‾敧晴摥
牯੡〲〱〭ⴲ㠱ㄠ㨶㔵㌺⬴㔰〳㸠朠慢扤祯畺晬慩瑢捥㱨慔��
�湩整湲瑥䬼ㅐ㰾偋㸹䬼㡐㰾偋
㸷㈊㄰ⴰ㈰ㄭ‸㘱㔺㨶㜵〫㌵‰‾潧杯䐼睯㹮㈊㄰ⴰ㈰ㄭ‸��
�㔺㨷㤲〫㌵‰‾潬歧祥ੳ〲〱〭ⴲ㠱ㄠ㨶
㜵㌺⬷㔰〳㸠映摥牯捡牯੥〲〱〭ⴲ㠱ㄠ㨶㤵㐺⬳㔰〳㸠搠��
�慮桴䬼ㅐ㰾偋㸹䬼㡐㰾偋㸴吼
扡显摥牯捡牯੥〲〱〭ⴲ㠱ㄠ㨷〰〺⬳㔰〳㸠椠㱩敄㹬䐼汥��
�敄㹬䐼汥㰾捂卫㹰䈼正灓㰾捂
卫㹰䈼正灓㰾卌晨㹴刼杩瑨㰾敄㹬䰼桓瑦䌾䬼ㅐ㰾楒桧㹴刼��
�瑨㰾楒桧㹴刼杩瑨㰾楒
桧㹴刼杩瑨㰾楒桧㹴䈼正灓㰾捂卫㹰䬼㉐㰾偋㸵刼杩瑨㰾潄��
�㰾敄㹬䰼桓瑦夾畯⁲䰼桓
瑦倾潲楦敬栠獡戠敥桳牯汴獩整㱤䍌牴㹬㱴卌晨㹴䍈㱌捂��
�㹰䈼正灓㰾捂卫㹰䈼正灓
朾潯䰼晥㹴䐼睯㹮䐼睯㹮㈊㄰ⴰ㈰ㄭ‸㜱〺㨲㄰〫㌵‰‾䰼��
�瑦䠾䱃㈊㄰ⴰ㈰ㄭ‸㜱〺㨲㐰〫㌵‰
‾挠敨湮楡㈊㄰ⴰ㈰ㄭ‸㜱〺㨲㘴〫㌵‰‾䐼汥㰾䍌牴㹬㱶��
�牴㹬楩刼杩瑨㰾捂卫㹰䈼正灓㰾
捂卫㹰䰼桓瑦䠾䈼正灓㰾敌瑦㰾敌瑦㰾卌晨㹴䍈㱌楒桧㹴刼��
�瑨㰾捂卫㹰刼杩瑨㰾⬣㸵
刼杩瑨㰾楒桧㹴㈊㄰ⴰ㈰ㄭ‸㜱〺㨳㤳〫㌵‰‾刼杩瑨㰾⬣��
�㰾敌瑦㰾捂卫㹰ਬ〲〱〭ⴲ㠱ㄠ㨷㌰
㐺⬵㔰〳㸠㰠潄湷㰾潄湷㰾潄湷㰾潄湷㰾潄湷㰾潄湷㰾灕㰾��
�桧㹴⌼㐫㰾楒桧㹴刼杩瑨
㰾楒桧㹴刼杩瑨㰾敄㹬䐼汥ⰾ敧㱴潄湷ਾ〲〱〭ⴲ㠱ㄠ㨷㐰��
�⬸㔰〳㸠㰠捂卫㹰㈊㄰ⴰ㈰ㄭ‸
㜱〺㨴〵〫㌵‰‾唼㹰䰼桓瑦圾污湩刼桓瑦㨾䰼桓瑦䴾剁��
�晥㹴䰼晥㹴䰼晥㹴㰠楒桧㹴⌼
ㄫ㸰䰼晥㹴䰼晥㹴㰠偋㸱䬼㡐㰾卌晨㹴桔牵摳祡晧摥牯捡牯��
�〲〱〭ⴲ㠱ㄠ㨷㜰〺⬹㔰〳㸠
㰠䍌牴㹬杴慭汩挮浯㈊㄰ⴰ㈰ㄭ‸㜱〺㨹㌳〫㌵‰‾慫瑲楨��
�灩㱳慔㹢敦潤慲潣敲㈊㄰ⴰ㈰ㄭ
‸㜱〺㨹㈴〫㌵‰‾晧摥牯捡牯੥〲〱〭ⴲ㠱ㄠ㨷〱㌺⬹㔰��
�㸠㰠卌晨㹴剔㱌卌晨㹴䔫瑎牥䈼正
灓㰾捂卫㹰䈼正灓㰾卌晨㹴䕔⁒潣扭湩瑡潩潤獥渠瑯眠牯��
�䈼正灓㰾⬣㠱㰾捂卫㹰獩渠
瑯眠牯楫杮栠牥⹥⸮桷湥椠椠㱰捂卫㹰䈼正灓㰾捂卫㹰䈼正��
�㰾捂卫㹰䈼正灓㰾捂卫㹰
䈼正灓㰾捂卫㹰桨湥䈼正灓㰾捂卫㹰䈼正灓㰾捂卫㹰桷湥椠��
�灹⁥浧楡湡⁤牰獥⁳䰼桓
瑦䌾剔㱌卌晨㹴䔫呎剅楬畮੸〲〱〭ⴲ㠱ㄠ㨷㌱㈺⬰㔰〳㸠��
�䍌牴㹬਀〲〱〭ⴲ㠱ㄠ㨷㌱㌺⬹㔰
〳㸠猠摵慣⁴瘯牡氯杯氯杯敫獹氮杯㈊㄰ⴰ㈰ㄭ‸㜱ㄺ㨴��
�〫㌵‰‾楬畮੸〲〱〭ⴲ㠱ㄠ㨷㐱ㄺ⬰
㔰〳㸠㰠䍌牴㹬摴湩歡牡湡挮浯㈊㄰ⴰ㈰ㄭ‸㜱ㄺ㨴ㄴ〫㌵��
�‾䐼汥㰾敄㹬䐼汥㰾敄㹬䐼汥
㰾敄㹬䰼桓瑦圾唼㹰㈊㄰ⴰ㈰ㄭ‸㜱ㄺ㨵〲〫㌵‰‾㈊㄰ⴰ��
�ㄭ‸㜱ㄺ㨵ㄴ〫㌵‰‾潧杯敬㱲捂卫
㹰䰼瑃汲>㈊㄰ⴰ㈰ㄭ‸㜱ㄺ㨵〵〫㌵‰‾唼㹰㈊㄰ⴰ㈰ㄭ‸�
��ㄺ㨵㐵〫㌵‰‾

Using logkeys version: 0.1.0
Operating System: Ubuntu 9.04

I'm getting the following error when trying to compile logkeys on Fedora
Linux 12:

make  all-recursive
make[1]: Entrando no diretório `/home/taylon/rpmbuild/SOURCES/logkeys-0.1.0'
Making all in src
make[2]: Entrando no diretório
`/home/taylon/rpmbuild/SOURCES/logkeys-0.1.0/src'
g++ -DHAVE_CONFIG_H -I. -I..     -Wall -O3 -MT logkeys.o -MD -MP -MF
.deps/logkeys.Tpo -c -o logkeys.o logkeys.cc
logkeys.cc: In function ‘int main(int, char**)’:
logkeys.cc:473: error: ‘umask’ was not declared in this scope
make[2]: ** [logkeys.o] Erro 1
make[2]: Saindo do diretório `/home/taylon/rpmbuild/SOURCES/logkeys-0.1.0/src'
make[1]: ** [all-recursive] Erro 1
make[1]: Saindo do diretório `/home/taylon/rpmbuild/SOURCES/logkeys-0.1.0'
make: ** [all] Erro 2

Seems to be missing a "#include <sys/stat.h>".
I added it on the code and everything worked fine.

Could be possible to create a directory (maybe /lib/keylog) where save all 
existing keymap file. Moreover keylogs should automatically choose the right 
keymap if user doesn't specify another one.

The check could be based on the locale.

I: Bus=0003 Vendor=045e Product=071d Version=0111
N: Name="Microsoft Microsoft® 2.4GHz Transceiver V1.0"
P: Phys=usb-0000:00:1d.3-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.3/usb5/5-1/5-1:1.0/input/input4
U: Uniq=
H: Handlers=kbd event4 
B: EV=120013
B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe
B: MSC=10
B: LED=107

I: Bus=0003 Vendor=045e Product=071d Version=0111
N: Name="Microsoft Microsoft® 2.4GHz Transceiver V1.0"
P: Phys=usb-0000:00:1d.3-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:1d.3/usb5/5-1/5-1:1.1/input/input5
U: Uniq=
H: Handlers=kbd mouse2 event5 js0 
B: EV=10001f
B: KEY=837fff 2c3027 bf004444 0 c000000 1f0001 10f84 8a27c007 ffff7bfa d941dfff 
febeffdf ffefffff ffffffff fffffffe
B: REL=fc3
B: ABS=ffffff01 701ff
B: MSC=10

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.
If applicable, also attach contents of /proc/bus/input/devices.
proc/bus/input/devices   is an empty file

I like logkeys! I especially appreciate the ease of use and the readability of 
the log file. However, I'd like to have the option to crypt the log file and 
have it readable by non-root user. That way I could save the log file to my 
dropbox folder or transfer it easily from a machine to another.

Great work, thanks :)

Not sure where to leave a BIG THANK YOU but this is the only area I can do a 
post so I thought I want to say how grateful I am to find this application.  
Been looking through all the keyloggers on Linux, this one is THE BEST.

Works great all around.  I'm sure there will be a ton of request for new 
features but so far, I love it!

I attach the es_ES keymap, tested working.

Great job!

Hello,
i have a problem for a compilation:

[...]
checking for close... yes
checking for flock... yes
checking for write... yes
checking for umask... yes
checking for setegid... yes
checking for seteuid... yes
checking for strftime... yes
checking for localtime... yes
checking for fflush... yes
checking for read... yes
checking for time... yes
checking for fgetws... yes
checking for wcslen... yes
checking for swscanf... yes
checking for wcscpy... yes
checking for popen... yes
checking for pclose... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating man/Makefile
config.status: creating scripts/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
make  all-recursive
make[1]: entrant dans le répertoire « /home/wido/Desktop/logkeys/src/
logkeys-0.1.1a/build »
Making all in src
make[2]: entrant dans le répertoire « /home/wido/Desktop/logkeys/src/
logkeys-0.1.1a/build/src »
make[2]: Rien à faire pour « all ».
make[2]: quittant le répertoire « /home/wido/Desktop/logkeys/src/
logkeys-0.1.1a/build/src »
Making all in man
make[2]: entrant dans le répertoire « /home/wido/Desktop/logkeys/src/
logkeys-0.1.1a/build/man »
make[2]: Rien à faire pour « all ».
make[2]: quittant le répertoire « /home/wido/Desktop/logkeys/src/
logkeys-0.1.1a/build/man »
Making all in scripts
make[2]: entrant dans le répertoire « /home/wido/Desktop/logkeys/src/
logkeys-0.1.1a/build/scripts »
make[2]: Rien à faire pour « all ».
make[2]: quittant le répertoire « /home/wido/Desktop/logkeys/src/
logkeys-0.1.1a/build/scripts »
make[2]: entrant dans le répertoire « /home/wido/Desktop/logkeys/src/
logkeys-0.1.1a/build »
make[2]: quittant le répertoire « /home/wido/Desktop/logkeys/src/
logkeys-0.1.1a/build »
make[1]: quittant le répertoire « /home/wido/Desktop/logkeys/src/
logkeys-0.1.1a/build »
Making install in src
make[1]: entrant dans le répertoire « /home/wido/Desktop/logkeys/src/
logkeys-0.1.1a/build/src »
make[2]: entrant dans le répertoire « /home/wido/Desktop/logkeys/src/
logkeys-0.1.1a/build/src »
test -z "/usr/bin" || /bin/mkdir -p "/usr/bin"
make[2]: Rien à faire pour « install-data-am ».
  /bin/install -c logkeys llk llkk '/usr/bin'
/bin/install: impossible de créer le fichier standard « /usr/bin/
logkeys »: Permission non accordée
/bin/install: impossible de créer le fichier standard « /usr/bin/llk »: 
Permission non accordée
/bin/install: impossible de créer le fichier standard « /usr/bin/llkk »: 
Permission non accordée
make[2]: *** [install-binPROGRAMS] Erreur 1
make[2]: quittant le répertoire « /home/wido/Desktop/logkeys/src/
logkeys-0.1.1a/build/src »
make[1]: *** [install-am] Erreur 2
make[1]: quittant le répertoire « /home/wido/Desktop/logkeys/src/
logkeys-0.1.1a/build/src »
make: *** [install-recursive] Erreur 1
==> ERREUR: La compilation a échoué.
    Abandon...

I use archlinux x86_64, and i create a pkgbuild:

# Maintainer: wido <[email protected]>

pkgname=logkeys
pkgver=0.1.1a
pkgrel=1
pkgdesc="keylogger support USB keyboard"
license=(GPL3)
arch=(i686 x86_64)
depends=('')
url="http://logkeys.googlecode.com/"
source=(http://logkeys.googlecode.com/files/$pkgname-$pkgver.tar.gz)
md5sums=('19362a382b65e89c66ea4c5642297589')

build() {

cd ${srcdir}/${pkgname}-${pkgver}/build
../configure --prefix=/usr
make || return 1
make install || return 1
}

There is insufficient checking done when opening files.
(I'm only a newb. :S)

I am not writing about an issue but would like to make an inquiry on the 
product. I could not find an email I could send my inquiry to so I am writing 
here. Is logkeys capable of monitoring keyboards from multiple machines? Can 
the monitoring be in one box which has a different location from all the 
machines. So basically all machines are on different locations. We are looking 
for an application that can monitor Point of Sale applications and user key ins 
from a single point.

Instead of using the first kbd entry found in /proc/bus/input/devices, you 
could spawn threads to handle input from all kbd devices found.

The log files would just have to be named accordingly, to indicate which device 
produced the keystroke data.

Also, you could have a thread that monitors the system to detect when new USB 
or Bluetooth keyboards are attached to the system, then automatically spawn a 
thread to log their input.

This ability would make logkeys quite a bit more powerful and flexible.

Regards,
Markus.

What steps will reproduce the problem?
1. sudo logkeys -s
2.
3.

What is the expected output? To log ;-)
What do you see instead?

logkeys: Couldn't determine keyboard device. :/
logkeys: Please post contents of your /proc/bus/input/devices file as a new bug 
report. Thanks!
desktop:~/Apps/logkeys-0.1.1a/build$ cat /proc/bus/input/devices
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0 
B: EV=3
B: KEY=10000000000000 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: EV=3
B: KEY=10000000000000 0

I: Bus=0003 Vendor=046d Product=c517 Version=0110
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:1a.1-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/input/input2
U: Uniq=
H: Handlers=sysrq kbd event2 
B: EV=120013
B: KEY=1000000000007 ff800000000007ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=046d Product=c517 Version=0110
N: Name="Logitech USB Receiver"
P: Phys=usb-0000:00:1a.1-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.1/input/input3
U: Uniq=
H: Handlers=kbd mouse0 event3 
B: EV=1f
B: KEY=c0000000 837fff042c332f bf08444500000000 ff0001 1f848b37cc00 
667bfadd71dfed 9e000000000000 0
B: REL=1c3
B: ABS=100000000
B: MSC=10



What version of the product are you using (`logkeys --help`)?0.1.1a

On what operating system? Ubuntu Maverick 10.10 x86_64


Please provide any additional information below.
If applicable, also attach contents of /proc/bus/input/devices, the output
of command `dumpkeys -n > dumpkeys.output`, and any
other relevant files.

What steps will reproduce the problem?
1. sudu su
2. tar xvzf logkeys-0.1.0.tar.gz
3. cd logkeys-0.1.0/build
4. ../configure

What output do you see instead?

* * * * * * * * * * * * * * * * * * * * * * * * 

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking for C++ compiler default output file name... 
configure: error: in `/home/flip/logkeys-0.1.0/build':
configure: error: C++ compiler cannot create executables


* * * * * * * * * * * * * * * * * * * * * * * * 

What version of the product are you using? On what operating system?

Logkeys 0.1.0 on Ubuntu 9.04 Gnome version 2.26.1

What steps will reproduce the problem?
1. install
2. run "logkeys -s"


the Code is stuck in an infinite loop at around line 305
      index = line.find("U+", 0);
      while ((unsigned int) index != std::string::npos) {
        line[index] = '0'; line[index + 1] = 'x';
        index = line.find("U+", index);
      }

When I printed index I get "-1". which is part of the problem.

Hello, my keymaps (french keyboard)

Hello,

Thanks for writing a great Linux keylogger. It has been very educational for me 
to read through the code, to understand how to read input from any keyboard 
attached to the system, regardless of which program has input focus. This is 
very useful for embedded systems, where you need a simple method to control a 
device, e.g. by plugging a USB keyboard into a hidden USB port.

In the logkeys-0.1.1a source code, I happened to notice what appears to be a 
deadly bug, just waiting to blow up.

On line 349 of logkeys.cc, you have the following code:

args.device = const_cast<char*>(input_dev_index.str().c_str());

If we analyze what is happening here, we see that:

1) input_dev_index is a std::stringstream object, created on the stack, and 
therefore will be destroyed when the function returns.
2) Calling input_dev_index.str() returns a possibly temporary std::string 
object.
3) Calling input_dev_index.str().c_str() returns a char pointer, pointing to 
the data in the contents of the temporary input_dev_index object (or a 
temporary std::string object).
4) When the input_dev_index variable destructs when it goes out of scope, any 
char pointers to the stringstream data will be invalid. Later, when new memory 
is allocated, the new memory blocks may occupy the bytes formerly occupied by 
the stringstream data. Accessing args.device will of course read from the 
undefined memory contents, and your program will have unpredictable behaviour.

Your program should already be producing unpredictable behaviour. The fact that 
it isn't is possibly because you are not allocating any new memory after 
calling the determine_input_device() function. However, if this changes in the 
future, you will see problems.

Suggested solutions:
1) Create a global std::string gInputDevice object. Copy the contents of 
input_dev_index into the string [gInputDevice = input_dev_index.str()] and then 
set args.device = gInputDevice.c_str(). This will work because the string will 
not be destroyed when determine_input_device() returns and the args.device 
pointer will remain valid.
2) Instead of using char pointers in the args structure, use char arrays. Copy 
the actual string values into the structure using strcpy(). This is the most 
robust solution, because then you can have multiple copies of the args 
structure, each with different values. In the existing code, if you have 
multiple copies, changing the contents of one of the char arrays pointed to 
will cause all copies of args to be affected.

Hope this helps. Keep up the great work.

Regards,
Markus.

I have tried many many times to do this and usually crash on "segmentation 
error", other people have tried this with no luck, maybe anyone can give us a 
little of help?... or this issue need a new feature??

Sorry about my English...

Hi -

xmacroplay (http://xmacro.sourceforge.net/) can play back mouse and 
keyboard actions.  The macro format is rather simple.  Here's an example of 
a test.macro file:

MotionNotify 525 1033
ButtonPress 1
ButtonRelease 1
String My name
KeyStrPress h
KeyStrRelease h

I think having a script to convert logkeys format to xmacro format would be 
useful.  We could use a python script to do the enhancement.

BTW, have you consider using github?

What steps will reproduce the problem?
1. the directory is at the following direction: home/.dust/logkeys-0.1.1a
2. ../configure doesn't give me error
3. make either
4. i turn into root by typing su and then type "make install"

What is the expected output?
the program should be installed

What do you see instead?

root@virpat-desktop:/home/virpat/.dust/logkeys-0.1.1a/build# make install
Making install in src
make[1]: se ingresa al directorio `/home/virpat/.dust/logkeys-0.1.1a/build/src'
g++ -DHAVE_CONFIG_H -I. -I../../src -I..     -Wall -O3 
-DSYS_CONF_DIR=\"/usr/local/etc\" -MT logkeys.o -MD -MP -MF .deps/logkeys.Tpo 
-c -o logkeys.o ../../src/logkeys.cc
mv -f .deps/logkeys.Tpo .deps/logkeys.Po
g++  -Wall -O3 -DSYS_CONF_DIR=\"/usr/local/etc\"   -o logkeys logkeys.o  
g++ -DHAVE_CONFIG_H -I. -I../../src -I..     -Wall -O3 
-DSYS_CONF_DIR=\"/usr/local/etc\" -MT llk.o -MD -MP -MF .deps/llk.Tpo -c -o 
llk.o ../../src/llk.cc
mv -f .deps/llk.Tpo .deps/llk.Po
g++  -Wall -O3 -DSYS_CONF_DIR=\"/usr/local/etc\"   -o llk llk.o  
g++ -DHAVE_CONFIG_H -I. -I../../src -I..     -Wall -O3 
-DSYS_CONF_DIR=\"/usr/local/etc\" -MT llkk.o -MD -MP -MF .deps/llkk.Tpo -c -o 
llkk.o ../../src/llkk.cc
mv -f .deps/llkk.Tpo .deps/llkk.Po
g++  -Wall -O3 -DSYS_CONF_DIR=\"/usr/local/etc\"   -o llkk llkk.o  
make[2]: se ingresa al directorio `/home/virpat/.dust/logkeys-0.1.1a/build/src'
test -z "/usr/local/bin" || /bin/mkdir -p "/usr/local/bin"
  /usr/bin/install -c logkeys llk llkk '/usr/local/bin'
make  install-exec-hook
make[3]: se ingresa al directorio `/home/virpat/.dust/logkeys-0.1.1a/build/src'
chown root\: /usr/local/bin/llk
chmod u+s    /usr/local/bin/llk
chown root\: /usr/local/bin/llkk
chmod u+s    /usr/local/bin/llkk
make[3]: se sale del directorio `/home/virpat/.dust/logkeys-0.1.1a/build/src'
make[2]: No se hace nada para `install-data-am'.
make[2]: se sale del directorio `/home/virpat/.dust/logkeys-0.1.1a/build/src'
make[1]: se sale del directorio `/home/virpat/.dust/logkeys-0.1.1a/build/src'
Making install in man
make[1]: se ingresa al directorio `/home/virpat/.dust/logkeys-0.1.1a/build/man'
make[2]: se ingresa al directorio `/home/virpat/.dust/logkeys-0.1.1a/build/man'
make[2]: No se hace nada para `install-exec-am'.
test -z "/usr/local/share/man/man8" || /bin/mkdir -p "/usr/local/share/man/man8"
 /usr/bin/install -c -m 644 ../../man/logkeys.8 '/usr/local/share/man/man8'
make[2]: se sale del directorio `/home/virpat/.dust/logkeys-0.1.1a/build/man'
make[1]: se sale del directorio `/home/virpat/.dust/logkeys-0.1.1a/build/man'
Making install in scripts
make[1]: se ingresa al directorio 
`/home/virpat/.dust/logkeys-0.1.1a/build/scripts'
make[2]: se ingresa al directorio 
`/home/virpat/.dust/logkeys-0.1.1a/build/scripts'
make[2]: No se hace nada para `install-exec-am'.
test -z "/usr/local/etc" || /bin/mkdir -p "/usr/local/etc"
 /usr/bin/install -c ../../scripts/logkeys-start.sh ../../scripts/logkeys-kill.sh '/usr/local/etc'
make[2]: se sale del directorio 
`/home/virpat/.dust/logkeys-0.1.1a/build/scripts'
make[1]: se sale del directorio 
`/home/virpat/.dust/logkeys-0.1.1a/build/scripts'
make[1]: se ingresa al directorio `/home/virpat/.dust/logkeys-0.1.1a/build'
make[2]: se ingresa al directorio `/home/virpat/.dust/logkeys-0.1.1a/build'
make[2]: No se hace nada para `install-exec-am'.
make[2]: No se hace nada para `install-data-am'.
make[2]: se sale del directorio `/home/virpat/.dust/logkeys-0.1.1a/build'
make[1]: se sale del directorio `/home/virpat/.dust/logkeys-0.1.1a/build'
root@virpat-desktop:/home/virpat/.dust/logkeys-0.1.1a/build# bin/llk
bash: bin/llk: No existe el archivo o directorio



my terminal is in spanish, just a few translation
se ingresa al directorio --> enter in the directory
se sale del directorio --> exit of the directory
No existe el archivo o directorio --> the file or directory doesn't exist



What version of the product are you using (`logkeys --help`)?
logkeys version: 0.1.1a

On what operating system?
Ubuntu 10.04 (lucid)
gnome 2.30.2 (Ubuntu 2010-06-25)
kernel 2.6.32-25-generic (#45-Ubuntu SMP Sat Oct 16 19:52:42 U
gcc version 4.4.3 (x86_64-linux-gnu)

Please provide any additional information below.
If applicable, also attach contents of /proc/bus/input/devices, the output
of command `dumpkeys -n > dumpkeys.output`, and any
other relevant files.

Hi,

 I was involved in the developement of an embedded Linux project and was using xbindkeys to link some keys to a set of scripts. Due to a complex weird bug in the X-Free implementation while interacting with an usb-2-serial device, I couldn't make it work since randomly the X came into an infinite loop.
 Fortunately I found that by slightly modifying logkeys to suit my needs I could replace xbindkeys with logkeys and the result was much better. Not only I could bypass the bug in the X system, but the setup was much easier, and now I can differentiate the events comming from two different keyboards. In my particular system this is a big plus since the system has two keyboards and I needed to make a complex setup to differentiate both inside X (activating/disabling usb-profiles depending on the system).

 I couldn't find any email address to contact the logkeys' author so I post it as a feature request to let logkeys act as a xbindkeys replacement.
 I'm sure many other development groups could be interested. From the desktop guys at Ubuntu/Fedora to all the army of developers that are targeting Android and Meego embedded devices.

P.S.: 
Hope this post arrive to someone, since I see no activity in this project since 
June 2010 (nearly 6 months ago).

What steps will reproduce the problem?
1. using "logkeys --start -u --post-size=3k" cause the log file to be 
overwritten with a fresh log file when the size reaches 3k.
2.
3.

What is the expected output?
It is suppose to be renamed to logfile.X creating this new file.
What do you see instead?
all the data is erased and the log file starts again over the same file.


What version of the product are you using (`logkeys --help`)?
logkeys-0.1.1a
On what operating system?
Ubuntu 10.10 Maverick Meerkat

Please provide any additional information below.
If applicable, also attach contents of /proc/bus/input/devices, the output
of command `dumpkeys -n > dumpkeys.output`, and any
other relevant files.

What steps will reproduce the problem?
1.extract using tar xvzf
2.go to build dir and do a ../configure
3. then do a make

What is the expected output?
the make succeeds with no errors

What do you see instead?
Lots of failures
../../src/args.cc:84:16: error: invalid suffix "b10000" on integer constant
../../src/args.cc:98:16: error: invalid suffix "b100000" on integer constant
../../src/logkeys.cc:370:37: error: invalid suffix "b1" on integer constant
../../src/logkeys.cc:384:51: error: invalid suffix "b1" on integer constant
../../src/logkeys.cc:388:61: error: invalid suffix "b1" on integer constant


What version of the product are you using (`logkeys --help`)?
logkeys-0.1.1a

On what operating system?
RHEL 5.1

Please provide any additional information below.
If applicable, also attach contents of /proc/bus/input/devices, the output
of command `dumpkeys -n > dumpkeys.output`, and any
other relevant files.

Hi,

I had to update the keymap for portuguese (Brazil). I am attaching the final 
file here.

Thanks.

I: Bus=0003 Vendor=045e Product=008a Version=0111
N: Name="Microsoft Microsoft Wireless Optical Desktop® 1.00"
P: Phys=usb-0000:00:1d.1-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/input/input3
U: Uniq=
H: Handlers=kbd event3 
B: EV=120013
B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe
B: MSC=10
B: LED=107

I: Bus=0003 Vendor=045e Product=008a Version=0111
N: Name="Microsoft Microsoft Wireless Optical Desktop® 1.00"
P: Phys=usb-0000:00:1d.1-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.1/input/input4
U: Uniq=
H: Handlers=kbd mouse1 event4 
B: EV=17
B: KEY=30000 0 0 0 0 1f0000 f84 244000 601878 d800d448 1e0000 0 0 0
B: REL=7c3
B: MSC=10

logkeys was working fine when I tried it with the -u switch.

But to use bin/llk , I need to change the change the etc/logkeys-start.sh file, 
I believe! But I don't seem to find the bash file.

Check out

human@pc-1:~$ logkeys
logkeys: Got r00t?                #just to make sure logkeys is installed
human@pc-1:~$ cd /etc
human@pc-1:/etc$ ls
acpi                    group-               pm
adduser.conf            grub.d               pnm2ppa.conf
alternatives            gshadow              polkit-1
anacrontab              gshadow-             popularity-contest.conf
apm                     gtk-2.0              ppp
apparmor                hdparm.conf          profile
apparmor.d              host.conf            profile.d
apport                  hostname             protocols
apt                     hosts                pulse
at.deny                 hosts.allow          purple
avahi                   hosts.deny           python
bash.bashrc             hp                   python2.6
bash_completion         ifplugd              rc0.d
bash_completion.d       init                 rc1.d
bindresvport.blacklist  init.d               rc2.d
blkid.conf              initramfs-tools      rc3.d
blkid.tab               inputrc              rc4.d
bluetooth               insserv              rc5.d
bogofilter.cf           insserv.conf         rc6.d
bonobo-activation       insserv.conf.d       rc.local
brlapi.key              iproute2             rcS.d
brltty                  issue                resolvconf
byobu                   issue.net            resolv.conf
ca-certificates         kbd                  resolv.conf.pppd-backup
ca-certificates.conf    kernel               rmt
calendar                kernel-img.conf      rpc
chatscripts             kerneloops.conf      rsyslog.conf
checkbox.d              ldap                 rsyslog.d
compizconfig            ld.so.cache          samba
computer-janitor.d      ld.so.conf           sane.d
ConsoleKit              ld.so.conf.d         scim
console-setup           legal                screenrc
couchdb                 lftp.conf            securetty
cron.d                  libpaper.d           security
cron.daily              locale.alias         sensors3.conf
cron.hourly             localtime            sensors.d
cron.monthly            logcheck             services
crontab                 login.defs           sgml
cron.weekly             logrotate.conf       shadow
crypttab                logrotate.d          shadow-
cups                    lsb-base             shells
dbus-1                  lsb-base-logging.sh  skel
debconf.conf            lsb-release          snmp
debian_version          ltrace.conf          sound
default                 magic                speech-dispatcher
defoma                  magic.mime           ssh
deluser.conf            mailcap              ssl
depmod.d                mailcap.order        sudoers
dhcp                    manpath.config       sudoers.d
dhcp3                   mime.types           sysctl.conf
dictionaries-common     mke2fs.conf          sysctl.d
doc-base                modprobe.d           terminfo
dpkg                    modules              timezone
emacs                   mono                 ucf.conf
environment             motd                 udev
firefox                 mtab                 ufw
fonts                   mtab.fuselock        updatedb.conf
foomatic                mtools.conf          update-manager
fstab                   nanorc               update-motd.d
fuse.conf               netscsid.conf        update-notifier
gai.conf                network              UPower
gamin                   NetworkManager       usb_modeswitch.conf
gconf                   networks             usb_modeswitch.d
gdb                     nsswitch.conf        vim
gdm                     obex-data-server     w3m
ghostscript             openoffice           wgetrc
gnome                   opt                  wodim.conf
gnome-app-install       pam.conf             wpa_supplicant
gnome-settings-daemon   pam.d                X11
gnome-system-tools      pango                xdg
gnome-vfs-2.0           papersize            xml
gnome-vfs-mime-magic    passwd               xul-ext
gre.d                   passwd-              xulrunner-1.9.2
groff                   pcmcia               zsh_command_not_found
group                   perl

Thank you

Error:
logkeys: Couldn't determine keyboard device. :/
logkeys: Please post contents of your /proc/bus/input/devices file as a new bug 
report. Thanks!

see devices file attach

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0 
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: EV=3
B: KEY=100000 0 0 0

I: Bus=0017 Vendor=0001 Product=0001 Version=0100
N: Name="Macintosh mouse button emulation"
P: Phys=
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=mouse0 event2 
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

I: Bus=0003 Vendor=045e Product=00f9 Version=0111
N: Name="Microsft Microsoft Wireless Desktop Receiver 3.1"
P: Phys=usb-0000:00:06.0-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb4/4-1/4-1:1.0/input/input3
U: Uniq=
H: Handlers=kbd event3 
B: EV=120013
B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe
B: MSC=10
B: LED=107

I: Bus=0003 Vendor=045e Product=00f9 Version=0111
N: Name="Microsft Microsoft Wireless Desktop Receiver 3.1"
P: Phys=usb-0000:00:06.0-1/input1
S: Sysfs=/devices/pci0000:00/0000:00:06.0/usb4/4-1/4-1:1.1/input/input4
U: Uniq=
H: Handlers=kbd mouse1 event4 
B: EV=10001f
B: KEY=837fff 2c3027 bf004444 0 0 1f0001 10f84 8b27c007 ff7f7bfa d9415fff 
febeffdf ffefffff ffffffff fffffffe
B: REL=fc3
B: ABS=1 0
B: MSC=10

I: Bus=0003 Vendor=0413 Product=6f00 Version=0002
N: Name="IR-receiver inside an USB DVB receiver"
P: Phys=usb-0000:00:04.1-2/ir0
S: Sysfs=/devices/pci0000:00/0000:00:04.1/usb1/1-2/input/input5
U: Uniq=
H: Handlers=kbd event5 
B: EV=3
B: KEY=14afc336 284284d 0 0 0 4 80058000 2190 40000801 9e96c0 0 900200 ffd

I: Bus=0001 Vendor=10ec Product=0662 Version=0001
N: Name="HDA Digital PCBeep"
P: Phys=card0/codec#0/beep0
S: Sysfs=/devices/pci0000:00/0000:00:08.0/input/input6
U: Uniq=
H: Handlers=kbd event6 
B: EV=40001
B: SND=6