AES CCM encryption with Android decryption failing

RE: AES CCM encryption with Android decryption failing

codebreaker176 — Mon, 24 Aug 2020 14:42:35 GMT

Hi,

Can you please tell me the code you used for encrypting on nordic device and decrypting in java

RE: AES CCM encryption with Android decryption failing

Iiridayn — Fri, 22 Mar 2019 18:55:54 GMT

https://stackoverflow.com/q/46432516/118153 might be relevant to you.

RE: AES CCM encryption with Android decryption failing

bjorn-spockeli — Mon, 11 Jul 2016 13:53:27 GMT

@mazshar : I not an Android developer, but it could be that the Android BLE stack does not use the Cipher class to encrypt the link, but rather an internal crypto library.

RE: AES CCM encryption with Android decryption failing

Maz Shar — Mon, 09 May 2016 18:14:26 GMT

@Jay Unfortunately not. I ended up using ECB instead and found an open source ECB software library to decrypt

RE: AES CCM encryption with Android decryption failing

Jay — Sat, 07 May 2016 02:02:17 GMT

Maz did you find a workaround for this on the Android side? Thanks

RE: AES CCM encryption with Android decryption failing

Maz Shar — Mon, 18 Apr 2016 10:30:07 GMT

Could you explain how this is possible if on the nrf51 it sends 4 bytes MIC and Android expects 8? How can Android successfully decrypt?

RE: AES CCM encryption with Android decryption failing

bjorn-spockeli — Mon, 18 Apr 2016 07:39:08 GMT

AES-CCM is the encryption used by Bluetooth LE so there should not be any compatibility issues with the nRF51's AES-CCM module and Android Bluetooth stack.

As far as I know there is no way to change the size of the MIC from 4 to 8 bytes.

-Bjørn