You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I happened upon this page which describes a different Microsoft MSD format ("Swift Pair") than the one Sniffle currently parses ("Connected Devices Platform"). It's quite interesting because it always includes a device name. It also sometimes includes a BTC BDADDR, which makes devices guaranteed uniquely identifiable even if they're using random private BLE BDADDRs. I think it'd be worth Sniffle parsing that.
And then when I was adding support for parsing the same CDP MSD type Sniffle currently parses, I noticed based on my collected data that if NearShareAuthPolicyPermissive is set, apparently the "Device Hash" is actually 2 unknown bytes followed by a device name. E.g. this is where things like default "LAPTOP-1234ABCD" or customized hostnames are advertised via ADV_NONCONN_IND. So that seems like a nice-to-have improvement of the existing MSD parsing.
The text was updated successfully, but these errors were encountered:
I happened upon this page which describes a different Microsoft MSD format ("Swift Pair") than the one Sniffle currently parses ("Connected Devices Platform"). It's quite interesting because it always includes a device name. It also sometimes includes a BTC BDADDR, which makes devices guaranteed uniquely identifiable even if they're using random private BLE BDADDRs. I think it'd be worth Sniffle parsing that.
And then when I was adding support for parsing the same CDP MSD type Sniffle currently parses, I noticed based on my collected data that if
NearShareAuthPolicyPermissive
is set, apparently the "Device Hash" is actually 2 unknown bytes followed by a device name. E.g. this is where things like default "LAPTOP-1234ABCD" or customized hostnames are advertised via ADV_NONCONN_IND. So that seems like a nice-to-have improvement of the existing MSD parsing.The text was updated successfully, but these errors were encountered: