commit 45059ca6092fbcd7058db16264a62ffa357fefc0
author Jakub Pawlowski <jpawlowski@google.com> Thu Aug 04 14:28:40 2016 -0700
committer Jakub Pawlowski <jpawlowski@google.com> Fri Aug 19 13:02:24 2016 +0000
tree 0a8f8dacffd30df6fc48fc2121e7052b42c4ee21
parent 1ff09042e0f95cd4adcca60a250a80f1638703ac

Fix Bluetooth OOB data parsing

In some early implementations of OOB, TK was send in bad, reversed
order, and was implemented in such way. This patch fixes that.

Bug: 30675596
Change-Id: Id6af6d96cd35ef118372319bab39862ba0501f29

src/com/android/nfc/handover/HandoverDataParser.java

diff --git a/src/com/android/nfc/handover/HandoverDataParser.java b/src/com/android/nfc/handover/HandoverDataParser.java
index eb77aaa..2921c67 100644
--- a/src/com/android/nfc/handover/HandoverDataParser.java
+++ b/src/com/android/nfc/handover/HandoverDataParser.java
@@ -443,15 +443,8 @@
                             break;
                         }
 
-                        byte[] reversedTK = new byte[len - 1];
-                        payload.get(reversedTK);
-
                         byte[] securityManagerTK = new byte[len - 1];
-
-                        //TK in AD is in reverse order
-                        for (int i = 0; i < reversedTK.length; i++) {
-                            securityManagerTK[i] = reversedTK[securityManagerTK.length - 1 - i];
-                        }
+                        payload.get(securityManagerTK);
 
                         result.oobData = new OobData();
                         result.oobData.setSecurityManagerTk(securityManagerTK);