Linux Keylogger

people believe that the Trojans are not valid against the Linux operating systems. The reality is that Troy is valid against the Linux operating systems, but they infect in different ways.

LKL is a popular Linux keylogger that runs on Linux on x86 architecture. LKL sniffs and logs everything that passes through the hardware keyboard port (0x60). It translates keycodes to ASCII with a keymap file.

Download

https://sourceforge.net/projects/lkl/files/lkl-0.1.1/lkl-0.1.1/lkl-0.1.1.tar.gz/download

Installation:

'Define' shell script attempts to guess correct values ??for various dependent variables during compilation.

It uses those values ??to create a 'Makefile' in each directory of the package. It can also create one or more. "H", the definition of dependent files.

Finally, it creates a shell script 'config.status' that you can run in the future to recreate the current configuration of "config.cache file that records the results of its tests to speed

reconfiguration, and the compiler output contains 'config.log' file (useful mainly for debugging 'configure').

If you need to do unusual things to assemble the package, try to figure out how to "set" can be verified to them, and mail diffs or instructions to "README", so that they can be considered for the next release.

If 'some point config.cache contains results you do not want, you can delete or edit.

"Configure.in" The file is used to create 'configure' by a program called "autoconf". You only need 'configure.in' if you want to change it or regenerate 'configure' using a newer version of `autoconf '.

The simplest way to compile this package is:

1. Directory "CD" that contains the source code of the package and type ". / Configure 'configures a package management system.

If you use 'csh' on an old version of System V, you may need SH type ". / Configure 'instead to prevent" csh "trying to run' configure 'itself.

Running 'configure' takes awhile. When running, it prints messages telling which features it is checking.

2. Type 'make' to compile the package.

3. Alternatively, type 'make check' to run any self-test functions that will be a package.

4. Type "make install" to install programs and data files and documentation.

5. You can remove the program binaries and object of the source code directory by typing "make clean". Also remove "set" files created (you can compile the package for a different kind of computer), type 'make distclean.

There is also a "make maintainer-clean 'target, but is primarily intended for developers of the package. If you use it, you may have to get all sorts of other programs in order to regenerate files provided with the distribution.