2 ms·
I suspect this will be a disaster. The article already hints at the reason why: "there's no indication yet that it has impacted Cronus or XIM accessories. Cronu
by ralferoo 3y ago
I suspect this will be a disaster. The article already hints at the reason why: "there's no indication yet that it has impacted Cronus or XIM accessories. Cronus and XIM accessories are controversial since they allow users to mimic a mouse and keyboard as an Xbox controller."
Currently, most third-party accessories correctly use their own USB VID:PID pair and are recognised as controllers by virtue of correctly implementing the USB HID protocols. By deciding to block anything that isn't approved by Microsoft, they'll necessarily have to whitelist a set of VID:PID pairs for devices that have been approved, and so unapproved third-party accessories will just fake their VID:PID pairs and present as another device.
Once this happens, there's no way of blacklisting the clones without impacting the genuine devices, unless they further have undocumented identification methods e.g. incorrectly responding to standard messages (e.g. the PS3 controller reported an incorrect number of axes, but would return data correctly when queried) or adding non-standard packet types.
- NessDan 3y agoTo add to this, PS4 queries the controller every 8 minutes for a challenge authentication response and PS5 controllers send the controller state, an incrementing number, and finally an encrypted hash of the above at the end of every data packet. I know because I had to try implementing it for my project https://keyboard.gg https://keyboard.gg