Broken in 10.10.x about keylogger HOT 12 CLOSED

Running the executable as root seems to work, I'm on 10.11.4, working in Terminal to @dineshappavoo

from keylogger.

It appears that non-modifier keys now require root privileges (just tested on Yosemite and El Capitan). Is it working for anyone without root privileges?

from keylogger.

I can confirm it works on El Capitan with sudo.

from keylogger.

Update: it does work for other programs besides Terminal.app (e.g. Chrome and Aquamacs).
However, I am mostly interested in Terminal. Would iterm be any different ?

I did get logKext (binary release) to work
(you just need to chown the plist file to root to get 'launchctl load' to accept it).

from keylogger.

@toddkaufmann I am running in Yosemite. It does not even work in Terminal. Every key press goes to keycode 59
[ctrl][ctrl][ctrl][ctrl][option][option][ctrl].

Did you get any workaround. Or is there any other package for keylogging in OSX?

from keylogger.

I'm in El Capitan, and it happened when I tried to compile it into another name. But with the original 'key logger', it was okay up to now.

from keylogger.

It works fine for me as well on El Capitan

from keylogger.

(Sorry, I wrote a report for a completely different project--but a keylogger that does mostly work).

Just tried again,
git pull && make clean && make
ran as root -- same thing.

I've since learned that Terminal.app has a 'Secure Keyboard Entry' menu item, and (I guess) that's enabled by default.

When I turn this off, keylogger seems to work.

However, probably sticking with fsb for it's features: has a launchd script, encrypts it's log file, and you don't need to change the 'secure keyboard' entry for terminal (probably requires the kernel module functionality to acheive). And lazy.

from keylogger.

Confirming for Sierra

from keylogger.

Yosemite 10.10.3
without sudo only modifier keys
with sudo both modifiers and characters

from keylogger.

I believe running it at startup sudo make startup and then restarting functions as if it was run as sudo on Sierra.

from keylogger.

Running with sudo is the correct solution.

from keylogger.