Re: [NTSysADM] Keylogger Found in Audio Driver of HP Laptops

On Thu, May 11, 2017 at 10:33 AM, Susan E Bradley wrote: > Apparently, the functionality of capturing keystrokes is also extremely > common, but outputting the data to a file for diagnostic or debugging > purposes is new and (I concur) may not be a particularly wise >

Re: [NTSysADM] Keylogger Found in Audio Driver of HP Laptops

We can only hope that its just HP's mistake of leaving this sort of debug option enabled in the driver during testing, and that its not something from the OEM chip provider. -- Espi On Thu, May 11, 2017 at 10:05 AM, Mike wrote: > The Conexant software must be present

Re: [NTSysADM] Keylogger Found in Audio Driver of HP Laptops

We can only hope that its just HP's mistake of leaving this sort of debug option enabled in the driver during testing, and that its not something from the OEM chip provider. -- Espi On Thu, May 11, 2017 at 10:05 AM, Mike wrote: > The Conexant software must be present

Re: [NTSysADM] Keylogger Found in Audio Driver of HP Laptops

https://community.spiceworks.com/topic/1993834-keylogger-in-hp-audio-driver " Edit: however, after reading the original article.. holy mother of blowing this out of proportion... good grief lol. So the purpose of the keylogging functionality in the actual driver is because many/most HP

Re: [NTSysADM] Keylogger Found in Audio Driver of HP Laptops

The Conexant software must be present on other laptops in the OEM image. I wonder if this is HP specific somehow or if other manufacturers have the same issue. On Thu, May 11, 2017 at 10:08 AM, Micheal Espinola Jr < michealespin...@gmail.com> wrote: >

[NTSysADM] Keylogger Found in Audio Driver of HP Laptops

https://www.bleepingcomputer.com/news/security/keylogger-found-in-audio-driver-of-hp-laptops/ According to researchers, the keylogger feature was discovered in the > Conexant HD Audio Driver Package version 1.0.0.46 and earlier. > This is an audio driver that is preinstalled on HP laptops. One

RE: [NTSysADM] O365 and RDS

Well that explains the message “you can’t run this version of office 2016 in terminal services, get thee a volume license”. They bought the wrong O365 plan. Looks like they will be stuck with LibreOffice and Chrome for OWA. They also found out they originally bought the wrong OS RDS CALs. Some