.
For your information, I actually tracked down the original reportabout this (and posted some corrections in a comment to theresearcher):
This was not HP's keyboard driver. This was Synaptics' touchpad driver (SynTP.sys).
Never said it is HP's driver. But understand, that it only went in to HP machines.
As far as we know. That, I have said.
The code in question was apparently the common classic issuethat the driver checks if a hotkey related to the touchpad ispressed, and has a test feature to help each laptop manufacturercheck if they configured the correct (laptop-specific) scan codefor that hotkey by using a special test driver that logs the keysthat match/don't match the configured one. On a number ofoccasions HP (and maybe others) have sent such test drivers to endusers instead of the drivers without the debug feature.
A keylogger is not useful in this case, particularly as timing is an acute issue. At the most basic, when they want what you portray, a utility like evtest.
In this case, no keys were logged unless someone (or something)with admin rights on the laptop did extra steps to turn on thefeature and to read back the results. Any malicious code withthose rights could just install its own logging without dependingon that particular wrong driver being installed, So to me, that particular issue falls into the less serious tier of:Possible misuse if other things go wrong first, upgrade when ready asa defense in depth. Jakob
Correct, it is not turned on by default. Never said otherwise. But it can be manually.
So far I've raised three independent issues in this thread, and have been fought on all three. I am bored now with trying to raise awareness, so let's just all agree that nobody wants to hear it. You do your thing and I'll do mine.
-- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users