On Tue Feb 11 11:14:01 2025 +0000, Harald Sitter wrote:
I've adjusted the MR to hash sysfs information on both sides. I am not quite sure how to best get access to the sha implementation in crypt.c though. As far as I understand it's not part of the unix lib. I am also not sure putting the sysfs/containerid handling into ntdll is at all that pretty. Input would be greatly appreciated.
Do we really need to use a cryptographic hash there? Could we instead extract the useful bits from the sysfs path, like USB port numbers and put them into some of the GUID data fields? We only need it to match the mmdevapi side when it is plugged in, I don't think we need to have anything stable across hotplugs or prefix restart.
Note that in any case there's things to resolve on the mmdevapi side before this can be useful like the property registry format in !359, and perhaps also how audio device hot-plugging works (if it does) or would work.