search for: keylogging

I wrote a small program to monitor keyboards found on /dev/input/event* It works great but I always get EAGAIN from my read() function. google says this is normal when open() is used and O_NONBLOCK mode. I know this is slightly offtopic but I was wondering if the centos gurus that also program know anything about this. My goal was to not be eating CPU cycles with a small program that just

Hi list Several people have physical access to my FreeBSD box and I have the feeling that somebody try to get access with boot -s options . Can I log activity after boot -s option (change user password, install software and etc.). I use boot -s and change user password, but after reboot i can't find this atcivity in log files. The BSD box is shutdown and run again many time at day. Best

...rmines that X11 forwarding ftp://ftp.dfn-cert.de/pub/docs/crypt/ssh-x11.ps.gz in response Alan Cox suggested that X11 Security Extensions may be used to limit the access of remote applications to the local X11 server 2004 X11 Forwarding is as dangerous as it was 1995: - keylogging (even though "secure keyboard" is used in (xterm|ssh-agent|xscreensaver) - I was able to attach a X0vncserver process on an forwarded X-display and got complete remote control. - screenshots of root window is possible through 'xwd' or ImageMagick's...