1

I am having an issue where I cannot communicate with Bluetooth LE devices if my Android 8 phone, with common criteria mode enabled. When common criteria mode is disabled, everything works as expected.

However, when I use my Android 6 phone with common criteria mode enabled, I have no issue.

I came across this link that states that common criteria mode "prevents non-authenticated Bluetooth connections"

So what I am thinking is bluetooth LE connections are not authenticated, and BLE will never work with common criteria mode until samsung and knox work something out.

I have tried a 3 different BLE devices on 3 different apps, and the behavior is always the same, the devices work great with common criteria mode off, but they don't work with common criteria mode on.

I even made a test app, and when common criteria mode is enabled, my GATT callbacks immediately return error 133 "GATT_ERROR" and newState 0, "DISCONNECTED".

WolverinEli
  • 59
  • 1
  • 5
  • Well BLE connections must always be non-secure at the time a connection is established. Then a procedure can make the unencrypted link encrypted. So it feels like their design is broken or they forgot to mention the details how it works. – Emil Dec 27 '19 at 23:57
  • I was thinking that was the case. If their whole idea is to keep all Bluetooth connections 100% secure, then they would have to block all BLE connections. – WolverinEli Dec 30 '19 at 14:12
  • Emil, would you know of a outside of the box way around the OS for BLE connections, or anyway of by-passing this? Like any ideas or theories? – WolverinEli Jan 03 '20 at 16:13
  • Not unless you root it. – Emil Jan 03 '20 at 19:49
  • Would it be possible to use a custom BLE stack in lieu of the built-in stack without rooting the phone? We are getting desperate for a creative solution. – WolverinEli Jan 08 '20 at 14:41
  • No, since it's a system thing. – Emil Jan 09 '20 at 15:39

0 Answers0