Package Details: logkeys-git 1:r74.5c36832-2

Git Clone URL: https://aur.archlinux.org/logkeys-git.git (read-only)
Package Base: logkeys-git
Description: Simple keylogger supporting also USB keyboards.
Upstream URL: https://github.com/kernc/logkeys
Keywords: keylogger
Licenses: GPLv3
Conflicts: logkeys
Provides: logkeys
Submitter: SanskritFritz
Maintainer: SanskritFritz
Last Packager: SanskritFritz
Votes: 46
Popularity: 0.003511
First Submitted: 2013-04-10 13:03
Last Updated: 2018-01-15 15:37

Dependencies (1)

Required by (0)

Sources (3)

Latest Comments

SanskritFritz commented on 2018-01-16 08:40

Since upstream introduced releases again, I have reintroduced the stable logkeys package. Happy keylogging!

SanskritFritz commented on 2018-01-14 21:23

@MrHritik, autoconf is part of the base-devel group which should be installed already. https://wiki.archlinux.org/index.php/PKGBUILD#makedepends "Note: The group base-devel is assumed to be already installed when building with makepkg. Members of this group should not be included in makedepends array."

MrHritik commented on 2018-01-14 20:27

autoconf should be added as a dependency.

SanskritFritz commented on 2016-02-23 20:53

Thanks. I will update the package right away. Use gistit next time :)

sanerb commented on 2016-02-23 16:44

looks like they restructured some of the build process. here's a patch.

EDIT: wow. munged to hell. here it is in base64.

LS0tIFBLR0JVSUxELm9sZAkyMDE2LTAyLTIzIDExOjQyOjU0LjAxNjUwOTc0MCAtMDUwMAorKysg
UEtHQlVJTEQJMjAxNi0wMi0yMyAxMTo0MToyMy4yMDg0MTY2MjEgLTA1MDAKQEAgLTQsNyArNCw3
IEBACiAKIHBrZ25hbWU9bG9na2V5cy1naXQKIF9naXRuYW1lPSJsb2drZXlzIgotcGtndmVyPXI0
MC43ODMyMWM2Citwa2d2ZXI9cjYyLmMwYTI5NzEKIGVwb2NoPTEKIHBrZ3JlbD0xCiBwa2dkZXNj
PSJTaW1wbGUga2V5bG9nZ2VyIHN1cHBvcnRpbmcgYWxzbyBVU0Iga2V5Ym9hcmRzLiIKQEAgLTI0
LDI0ICsyNCwyNiBAQAogICAgICAgICAgJ1NLSVAnKQogCiBwa2d2ZXIoKSB7Ci0JY2QgIiRfZ2l0
bmFtZSIKKwljZCAiJHtzcmNkaXJ9LyRfZ2l0bmFtZSIKIAlwcmludGYgInIlcy4lcyIgIiQoZ2l0
IHJldi1saXN0IC0tY291bnQgSEVBRCkiICIkKGdpdCByZXYtcGFyc2UgLS1zaG9ydCBIRUFEKSIK
IH0KIAogYnVpbGQoKSB7Ci0JY2QgIiRfZ2l0bmFtZSIKLQkuL2NvbmZpZ3VyZSAtLXByZWZpeD0v
dXNyIC0tc3lzY29uZmRpcj0vZXRjCisJY2QgIiR7c3JjZGlyfS8kX2dpdG5hbWUiCisJLi9hdXRv
Z2VuLnNoCisJY2QgYnVpbGQKKwkuLi9jb25maWd1cmUgLS1wcmVmaXg9L3VzciAtLXN5c2NvbmZk
aXI9L2V0YwogCW1ha2UKIH0KIAogcGFja2FnZSgpIHsKLQljZCAiJF9naXRuYW1lIgorCWNkICIk
e3NyY2Rpcn0vJF9naXRuYW1lL2J1aWxkIgogCW1ha2UgcHJlZml4PSIkcGtnZGlyL3VzciIgc3lz
Y29uZmRpcj0iJHBrZ2Rpci9ldGMiIGluc3RhbGwKIAogCWluc3RhbGwgLURtMDY0NCAiJHNyY2Rp
ci9sb2drZXlzZC5jb25mIiAiJHBrZ2Rpci9ldGMvY29uZi5kL2xvZ2tleXNkIgogCWluc3RhbGwg
LURtMDY0NCAiJHNyY2Rpci9sb2drZXlzLnNlcnZpY2UiICIkcGtnZGlyL3Vzci9saWIvc3lzdGVt
ZC9zeXN0ZW0vbG9na2V5cy5zZXJ2aWNlIgogCi0JY2QgImtleW1hcHMiCisJY2QgIiR7c3JjZGly
fS8ke19naXRuYW1lfS9rZXltYXBzIgogCWZvciBmaWxlbmFtZSBpbiAkKGxzICoubWFwKTsgZG8K
IAkJaW5zdGFsbCAtRCAtbSA2NDQgIiR7ZmlsZW5hbWV9IiAiJHtwa2dkaXJ9L3Vzci9zaGFyZS9s
a21hcHMvJHtmaWxlbmFtZX0iCiAJZG9uZQo=

SanskritFritz commented on 2016-01-22 20:25

Upstream moved to Github. There are no releases on Github, I'll file a bug report. Please use the logkeys-git package, it is perfectly usable and has the logkeys-stdout patch included.

SanskritFritz commented on 2015-12-14 15:00

https://www.archlinux.org/news/c-abi-change/
This means, you have to rebuild the package.

brad87 commented on 2015-12-14 14:31

Getting this on service start:

Dec 14 09:27:48 gemini logkeys[17926]: /usr/bin/logkeys: Error opening input event device '': No such file or di
Dec 14 09:27:48 gemini systemd[1]: Started Keylogger daemon.
Dec 14 09:27:48 gemini systemd[1]: logkeys.service: Main process exited, code=exited, status=1/FAILURE
Dec 14 09:27:48 gemini systemd[1]: logkeys.service: Control process exited, code=exited status=1
Dec 14 09:27:48 gemini systemd[1]: logkeys.service: Unit entered failed state.
Dec 14 09:27:48 gemini systemd[1]: logkeys.service: Failed with result 'exit-code'.

SanskritFritz commented on 2015-01-05 08:39

Nice catch! Post your findings here later so that everyone can benefit.

TiborB commented on 2015-01-04 23:43

I have got it - I have to define a device:

cat /var/log/Xorg.0.log | grep keyboard | grep event
[ 26.621] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event14)
[ 26.621] (**) AT Translated Set 2 keyboard: always reports core events
[ 26.621] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event14"

=>--device=event14

But I wonder if the device changes after each boot, I will have to investigate...

All comments