* failed Message Integrity Check (MIC)
@ 2019-05-23 5:01 Ordit Gross
0 siblings, 0 replies; only message in thread
From: Ordit Gross @ 2019-05-23 5:01 UTC (permalink / raw)
To: linux-bluetooth
hi all,
we have an application acting as gatt server, using bluez 5.47.
we just purchased a sniffer.
** when a client connects (mobile), I can see pairing (AES) process
taking place, all encrypted packets that follow show up as decrypted
incorrectly (bad MIC), but no disconnection occur.
** connecting to a specific phone (android LG G6), after pairing takes
place we see several encrypted packets that show up as decrypted
incorrectly (bad MIC), then connection is dropped with "Connection
Terminated due to MIC Failure (0x3d)"
Device Disconnected: reason 0
1. Is MIC being calculated in bluez? is kernel involved in this process?
2. How could it be other devices don't drop the connection?
I'm having a hard time understanding how could that problem arise..
and how to solve this..
any help would be appreciated
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-05-23 5:01 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-23 5:01 failed Message Integrity Check (MIC) Ordit Gross
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.