3 ms·

Have you checked if this was possibly because of https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2102 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE

Have you checked if this was possibly because of https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2102 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-2102? I mean, I get why you would blame MS for breaking this but maybe the onus is also on Bose and their ridiculously bad driver support.

thaumasiotes 6y ago
I haven't checked. How would I do that? The headphones are able to connect once after disabling and reenabling bluetooth in Windows. If the problem were that the headphones are configured to use a fixed, predictable long-term key, it isn't obvious to me why Windows would accept that key sometimes, but not all the time. (Note that I don't need to have Windows forget the device and re-pair from scratch.) Is there some aspect of initial bluetooth negotiation that would explain this?
- seniorgarcia 6y ago
  There was a list somewhere with devices using the wrong config. An explanation of the issue is here https://www.bleepingcomputer.com/news/security/microsoft-blocks-some-bluetooth-devices-due-to-security-risks/ https://www.bleepingcomputer.com/news/security/microsoft-blo... and there also is advice on checking if your device is affected. I thought the issue was that if the host initiates the connection it will work but if it's just auto reconnecting it will not but I may be wrong.
  - thaumasiotes 6y ago
    Doesn't look like the CVE is relevant. That article says it's indicated by this message: > Your Bluetooth device attempted to establish a debug connection. The Windows Bluetooth stack does not allow debug connection while it is not in the debug mode. I don't see that. What I see is > A device with Bluetooth adapter address (2c:45:a1:20:a1:99) has a bad service record (attribute identifier 9). The service will not be visible. That happens several times every time, whether the connection succeeds or not. There is also a message that appears just once, when the connection succeeds: > Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup. Searching for the first message, I found some support threads from Bose customers. They seem pretty angry about their headphones not working. :/

thaumasiotes 6y ago

I haven't checked. How would I do that? The headphones are able to connect once after disabling and reenabling bluetooth in Windows. If the problem were that the headphones are configured to use a fixed, predictable long-term key, it isn't obvious to me why Windows would accept that key sometimes, but not all the time. (Note that I don't need to have Windows forget the device and re-pair from scratch.) Is there some aspect of initial bluetooth negotiation that would explain this?

seniorgarcia 6y ago
There was a list somewhere with devices using the wrong config. An explanation of the issue is here https://www.bleepingcomputer.com/news/security/microsoft-blocks-some-bluetooth-devices-due-to-security-risks/ https://www.bleepingcomputer.com/news/security/microsoft-blo... and there also is advice on checking if your device is affected. I thought the issue was that if the host initiates the connection it will work but if it's just auto reconnecting it will not but I may be wrong.
- thaumasiotes 6y ago
  Doesn't look like the CVE is relevant. That article says it's indicated by this message: > Your Bluetooth device attempted to establish a debug connection. The Windows Bluetooth stack does not allow debug connection while it is not in the debug mode. I don't see that. What I see is > A device with Bluetooth adapter address (2c:45:a1:20:a1:99) has a bad service record (attribute identifier 9). The service will not be visible. That happens several times every time, whether the connection succeeds or not. There is also a message that appears just once, when the connection succeeds: > Windows cannot store Bluetooth authentication codes (link keys) on the local adapter. Bluetooth keyboards might not work in the system BIOS during startup. Searching for the first message, I found some support threads from Bose customers. They seem pretty angry about their headphones not working. :/