{"id":15372042,"url":"https://github.com/bagder/keyfreq","last_synced_at":"2025-04-15T11:32:51.211Z","repository":{"id":19475206,"uuid":"22720581","full_name":"bagder/keyfreq","owner":"bagder","description":"Logs all key presses with a timestamp","archived":false,"fork":false,"pushed_at":"2014-09-17T09:02:19.000Z","size":424,"stargazers_count":77,"open_issues_count":1,"forks_count":8,"subscribers_count":5,"default_branch":"master","last_synced_at":"2025-03-28T20:51:22.294Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":"rajanadar/VaultSharp","license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/bagder.png","metadata":{"files":{"readme":"README","changelog":"ChangeLog","contributing":null,"funding":null,"license":"COPYING","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2014-08-07T12:35:09.000Z","updated_at":"2024-07-25T15:19:59.000Z","dependencies_parsed_at":"2022-08-07T09:15:21.616Z","dependency_job_id":null,"html_url":"https://github.com/bagder/keyfreq","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bagder%2Fkeyfreq","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bagder%2Fkeyfreq/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bagder%2Fkeyfreq/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/bagder%2Fkeyfreq/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/bagder","download_url":"https://codeload.github.com/bagder/keyfreq/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":249061202,"owners_count":21206467,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-10-01T13:49:28.632Z","updated_at":"2025-04-15T11:32:50.938Z","avatar_url":"https://github.com/bagder.png","language":"Shell","funding_links":[],"categories":[],"sub_categories":[],"readme":"Original project: https://code.google.com/p/logkeys/\n\nForked-here-because: I wanted to log and analyze key frequency. I added the -f\noption. I found no way to contribute this back to the original project. Enjoy.\n\n==============================================================================         \n\n\n===============================================================================\n logkeys - a GNU/Linux keylogger that works!\n===============================================================================\n\n  0. Licence\n  1. Description\n  2. Installation\n  3. Usage how-to\n  4. Troubleshooting\n  5. Further information\n\n===============================================================================\n\n\n+------------------------------------------------\n 0. Licence\n===============================================================================\nlogkeys is dual licensed under the terms of either GNU GPLv3 or later, or \nWTFPLv2 or later. It is entirely your choice! See COPYING for further \ninformation about licensing.\n\n\n+------------------------------------------------\n 1. Description\n===============================================================================\nlogkeys is a linux keylogger. It is no more advanced than other available linux\nkeyloggers, notably lkl and uberkey, but is a bit newer, more up to date, it\ndoesn't unreliably repeat keys and it shouldn't crash your X. All in all, it\njust seems to work. It relies on event interface of the Linux input subsystem. \nOnce completely set, it logs all common character and function keys, while also\nbeing fully aware of Shift and AltGr key modifiers.\n\n\n+------------------------------------------------\n 2. Installation\n===============================================================================\nProvided your GNU/Linux distribution doesn't include logkeys package in its\nrepositories, manual installation of logkeys from source is as easy as:\n\n $ tar xvzf logkeys-0.1.1.tar.gz      # to extract the logkeys archive\n \n $ cd logkeys-0.1.1/build     # move to build directory to build there\n $ ../configure               # invoke configure from parent directory\n $ make                       # make compiles what it needs to compile\n ( become super↙user now )    # you need root to install in system dir\n # make install               # installs binaries, manuals and scripts\n\nThat's it.\n\nTo ever uninstall logkeys, remove accompanying scripts and manuals, issue\n\n # make uninstall    # in the same logkeys-0.1.1/build dir from before\n\nA copy of these instructions is in the accompanying INSTALL file.\n\n\n+------------------------------------------------\n 3. Usage how-to\n===============================================================================\n\nlogkeys is simple. You can either invoke it directly, by typing full command \nline, or use the provided scripts. There are two helper programs in this \npackage:\n\n bin/llk  , which is intended to start the logkeys daemon, and\n bin/llkk , which is intended to kill it.\n \nbin/llk runs etc/logkeys-start.sh, and bin/llkk runs etc/logkeys-kill.sh.\n\nYou can use these two setuid root programs (llk and llkk) for starting and\nstopping the keylogger quickly and covertly. You can modify the .sh scripts as\nyou like. As the two programs are installed with setuid bit set, the root\npassword need not be provided at their runtime.\n\nDefault log file is /var/log/logkeys.log and is not readable by others.\n\nI suggest you first test the program manually with\n\n $ touch test.log\n $ logkeys --start --output test.log\n\nand in the other terminal follow it with\n\n $ tail --follow test.log\n\nand see if the pressed keys match to those noted. If you use a US keyboard\nlayout, use -u switch. Make sure your terminal character locale is set to UTF-8\n\n $ locale\n LANG=xx_YY.UTF-8\n LC_CTYPE=\"xx_YY.UTF-8\"\n ...\n\nor alternatively, you need en_US.UTF-8 locale available on your system\n\n $ locale -a\n ...\n en_US.UTF-8\n ...\n\notherwise you may only see odd characters (like ꑶ etc.) when pressing character\nkeys.\n\nlogkeys acts as a daemon, and you stop the running logger process with\n\n $ logkeys --kill\n\n(or bin/llkk provided script).\n\nFor more information about logkeys log file format, logkeys keymap format, and\ncommand line arguments, read the application manual,\n\n $ man logkeys\n\nor see the wiki at project website: http://code.google.com/p/logkeys/\n\nAbuse the output of this software wisely.\n\n\n+------------------------------------------------\n 4. Troubleshooting\n===============================================================================\n\n4.1 empty log file or 'Error opening input event device'\n-------------------------------------------------\nAfter you run logkeys successfully, if you open the log file and see only the\n'Logging started...' and 'Logging stopped...' tag without any keypress\n\"contents,\" it is very likely that logkeys got your device id wrong.\n\nThis may also apply if you get the following error:\n  Error opening input event device '/dev/input/event-1'\n\nThe solution is to determine the correct event device id, and then run \nlogkeys with --device (-d) switch, specifying that device manually.\n\nThe procedure for manually learning the device id to use is as follows:\n\nAs root, for each existing device eventX in /dev/input/, where X is a number\nbetween 0 and 31 inclusively, write:\n\n $ cat /dev/input/eventX\n\nthen type some arbitrary characters. If you see any output, that is the device\nto be used. If you don't see any output, press Ctrl+C and continue with the\nnext device.\n\nIf this happened to be your issue, *please* submit a bug report, attaching\nyour /proc/bus/input/devices file as well as and specifying which was the\ncorrect id.\n\n\n4.2 logkeys outputs wrong characters\n-------------------------------------------------\nIt is very likely that you will see only some characters recognized, without\nany hope for Shift and AltGr working even slightly correct, especially when\nstarting logkeys in X. In that case it is better to switch to virtual \nterminal, e.g. tty4 (Ctrl+Alt+F4), and there execute:\n\n $ logkeys --export-keymap my_lang.keymap\n\nThen open my_lang.keymap in UTF-8 enabled text editor and manually repair any\nmissing or incorrectly determined mappings. From then on, execute logkeys by\n\n $ logkeys --start --keymap my_lang.keymap\n\nAgain, see if it now works correctly (character keys appear correct when you\nare viewing the log file in editor), and opt to modify bin/llk starter script.\n\nIf you create full and completely valid keymap for your particular language,\nplease upload it to website or send it to me by e-mail. Thanks.\n\n\n+------------------------------------------------\n 5. Further information\n===============================================================================\n\nRead the man page. Please read the whole man page. Thanks. :-)\n\nRefer to troubleshooting and FAQ sections on the project website,\n\n http://code.google.com/p/logkeys/ ,\n\nfor currently known issues, ways to resolve them, and any other information.\n\nReport any bugs and request reasonable features on the issues list page\n\n http://code.google.com/p/logkeys/issues .\n\nWhen opening new issues, always provide descriptively keyworded summary and\ndescription.\n\nYou are more than welcome to implement unreasonable features yourself, as well\nas hack the program to your liking.\n\nIf you are a pr0, please answer the few questions I commented in the source.\nThanks.\n\n~\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbagder%2Fkeyfreq","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fbagder%2Fkeyfreq","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbagder%2Fkeyfreq/lists"}