EldoS | Feel safer!

Software components for data protection, secure storage and transfer

PNPDeviceID with Call Back File System (cbfs3.sys)

Posted: 03/01/2012 19:31:51
by John Pfeiffer (Basic support level)
Joined: 03/01/2012
Posts: 2


Is there a way to find or identify the storage using PNPDeviceID?

Alternatively is it something that could be set in an API call?

The reason I ask is to provide a unique identifier for whitelisting with DLP software for our Customers.

Regards, -John
Posted: 03/02/2012 02:35:35
by Volodymyr Zinin (Team)

At least in the current and previous versions (<= 3.2) PnP storages always has "hardware ids" that starts with "{A5E1065D-0AD1-48ED-8457-A80B2D9B6FE2}". It's our internally generated GUID and it's expected to be unique. "Compatible ids" always contains "GenDisk".
In addition CallbackFS creates a PnP virtual bus where the virtual storages are placed. Its "hardware ids" is "root\cbfs_storlib_bus3". Actually full information about this device is located in the cbfs3.inf file.
Non-PnP storages don't have PnP support.
Posted: 03/06/2012 17:44:36
by John Pfeiffer (Basic support level)
Joined: 03/01/2012
Posts: 2

Many thanks! Apparently we did not use PnP storage but it's still good to know.



Topic viewed 3753 times

Number of guests: 1, registered members: 0, in total hidden: 0


Back to top

As of July 15, 2016 EldoS business operates as a division of /n software, inc. For more information, please read the announcement.

Got it!