I was trying to compile collectd on a old CentOS 6 host, and ./configure complained that rrdtool couldn’t be found; e.g.
rrdtool . . . . . . . no (rrd.h not found)
I’d intended to use rrdtool to collect instance-level metrics and then graph ’em out with CGP, so it was pretty annoying. TIL that you can use the “-ql” to list the files installed by a particular binary; e.g.
$ rpm -ql rrdtool-devel
package rrdtool-devel is not installed
I installed rrdtool-devel, and then lo and behold:
rrdtool . . . . . . . yes
A keylogger records when a key is pressed, when it is released, and whether any shift or special keys have been pressed. It is also recorded if, for example, a password is entered even if it is not displayed on the screen.
There is no evidence that this keylogger has been intentionally implemented. Obviously, it is a negligence of the developers – which makes the software no less harmful. If the developer would just disable all logging, using debug-logs only in the development environment, there wouldn’t be problems with the confidentiality of the data of any user.
I found the file MicTray64.exe in my HP EliteBook 840 G3. It’s barely 2 months old, running an up-to-date version of Windows 10 Pro. The prudent measure was to remove this file, as neither Conexant nor Hewlett-Packard hasn’t deigned to respond. I was unable to find the log file C:\Users\Public\MicTray.log, though.