Jump to content
IGNORED

Article: USB Audio Driver Security Risk


Recommended Posts

Quote

I remember several years ago arguing with a manufacturer about the negatives to using custom drivers rather than USB Class 2 drivers built into the operating system. Looks like another vote for native OS drivers.

 

Just that those drivers for commercial OS like Windows and macOS severely lack in features, like native DSD support and such.

 

Manufacturers just have to learn how to do their own drivers and do it properly. Software is as much part of the product quality as is the hardware design. They've just been slacking on software front. Some manufacturers have their own drivers and know how to do things, that gives them competitive advantage over some other vendors. Sometimes it is contracted work, sometimes they have in-house developers. Contracting software work is also art of it's own.

 

From my perspective, it also looks like another vote for open source drivers and platforms like Linux, where the native OS drivers support features like native DSD... ;)

 

 

P.S. From the story it looks like someone wanted to save a bit of money by not obtaining proper code signing key for Windows. It costs just a bit over 200€/year... Meaning that the installer of the driver probably wasn't signed either. And OS will warn you about that. I would advise to never execute unsigned installers on your computer... You can right-click on the installer, select Properties and then Digital Signatures tab to check who signed the package. If there's no Digital Signatures tab, it is unsigned.

Signalyst - Developer of HQPlayer

Pulse & Fidelity - Software Defined Amplifiers

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...