2020-11-27 08:50:50

by C K

[permalink] [raw]
Subject: BlueZ “Pin or Key missing” occurred even though it has already been paired

Hello,
I have an issue with my bluez device.
I explained it on stackover flow.
Help me about this please.

https://stackoverflow.com/questions/65001891/bluez-pin-or-key-missing-occurred-even-though-it-has-already-been-paired


Thanks,
Calvin


2020-11-27 08:53:12

by Jamie Mccrae

[permalink] [raw]
Subject: RE: BlueZ “Pin or Key missing” occurred e ven though it has already been paired

Hi Calvin,
What type of address is it? If the device has a random resolvable address then this means once the device has paired and exchanged IRK that regardless of what random resolvable address the device uses, the other device will always know what the device's true address is and will use the correct encryption keys and details. If the device has a different random non-resolvable address or random static address which changes then you cannot match these against a pairing.
Thanks,
Jamie

-----Original Message-----
From: C K <[email protected]>
Sent: 27 November 2020 06:46
To: [email protected]
Subject: BlueZ “Pin or Key missing” occurred even though it has already been paired

EXTERNAL EMAIL: Be careful with attachments and links.

Hello,
I have an issue with my bluez device.
I explained it on stackover flow.
Help me about this please.

https://stackoverflow.com/questions/65001891/bluez-pin-or-key-missing-occurred-even-though-it-has-already-been-paired


Thanks,
Calvin
THIS MESSAGE, ANY ATTACHMENT(S), AND THE INFORMATION CONTAINED HEREIN MAY BE PROPRIETARY TO LAIRD CONNECTIVITY, INC. AND/OR ANOTHER PARTY, AND MAY FURTHER BE INTENDED TO BE KEPT CONFIDENTIAL. IF YOU ARE NOT THE INTENDED RECIPIENT, PLEASE DELETE THE EMAIL AND ANY ATTACHMENTS, AND IMMEDIATELY NOTIFY THE SENDER BY RETURN EMAIL. THIS MESSAGE AND ITS CONTENTS ARE THE PROPERTY OF LAIRD CONNECTIVITY, INC. AND MAY NOT BE REPRODUCED OR USED WITHOUT THE EXPRESS WRITTEN CONSENT OF LAIRD CONNECTIVITY, INC.

2020-12-17 08:54:33

by C K

[permalink] [raw]
Subject: Re: BlueZ “Pin or Key missing” occurred even tho ugh it has already been paired

Hi Jamie,
I'm very sorry for late reply. I was busy with other urgent works.

Could you check this log?
Why is "Removing temporary device..." happening?


=============== first connection and pairing with my android test app
: connect -> bonded -> disconnect from app
===================================
Dec 17 07:35:38 bluetoothd[368]:
../bluez-5.50/src/agent.c:agent_ref() 0xfd1000: ref=1
Dec 17 07:35:38 bluetoothd[368]:
../bluez-5.50/src/agent.c:register_agent() agent :1.49
Dec 17 07:35:38 bluetoothd[368]:
../bluez-5.50/src/agent.c:unregister_agent() agent :1.49
Dec 17 07:35:38 bluetoothd[368]:
../bluez-5.50/src/agent.c:agent_disconnect() Agent :1.49 disconnected
Dec 17 07:35:38 bluetoothd[368]:
../bluez-5.50/src/agent.c:agent_destroy() agent :1.49
Dec 17 07:35:38 bluetoothd[368]:
../bluez-5.50/src/agent.c:agent_unref() 0xfd1000: ref=0
Dec 17 07:35:38 bluetoothd[368]:
../bluez-5.50/src/agent.c:agent_ref() 0xfd1000: ref=1
Dec 17 07:35:38 bluetoothd[368]:
../bluez-5.50/src/agent.c:register_agent() agent :1.49
Dec 17 07:35:38 bluetoothd[368]:
../bluez-5.50/src/agent.c:add_default_agent() Default agent set to
:1.49 /org/bluez/agent
Dec 17 07:35:46 bluetoothd[368]:
../bluez-5.50/src/adapter.c:connected_callback() hci0 device
5C:CB:99:7F:77:02 connected eir_len 0
Dec 17 07:35:47 bluetoothd[368]:
../bluez-5.50/src/adapter.c:user_passkey_notify_callback() hci0
5C:CB:99:7F:77:02
Dec 17 07:35:47 bluetoothd[368]:
../bluez-5.50/src/adapter.c:user_passkey_notify_callback() passkey
859060 entered 0
Dec 17 07:35:47 bluetoothd[368]:
../bluez-5.50/src/device.c:new_auth() Requesting agent authentication
for 5C:CB:99:7F:77:02
Dec 17 07:35:47 bluetoothd[368]:
../bluez-5.50/src/agent.c:agent_ref() 0xfd1000: ref=2
Dec 17 07:35:56 bluetoothd[368]:
../bluez-5.50/src/adapter.c:new_irk_callback() hci0 new IRK for
5C:CB:99:7F:77:02 RPA 00:00:00:00:00:00
Dec 17 07:35:56 bluetoothd[368]:
../bluez-5.50/src/adapter.c:new_csrk_callback() hci0 new CSRK for
5C:CB:99:7F:77:02 type 3
Dec 17 07:35:56 bluetoothd[368]:
../bluez-5.50/src/adapter.c:new_csrk_callback() hci0 new CSRK for
5C:CB:99:7F:77:02 type 2
Dec 17 07:35:56 bluetoothd[368]:
../bluez-5.50/src/adapter.c:new_long_term_key_callback() hci0 new LTK
for 5C:CB:99:7F:77:02 type 1 enc_size 16
Dec 17 07:35:56 bluetoothd[368]: ../bluez-5.50/src/device.c:device_set_bonded()
Dec 17 07:35:56 bluetoothd[368]:
../bluez-5.50/src/device.c:device_bonding_complete() bonding (nil)
status 0x00
Dec 17 07:35:56 bluetoothd[368]:
../bluez-5.50/src/agent.c:agent_unref() 0xfd1000: ref=1
Dec 17 07:35:56 bluetoothd[368]: ../bluez-5.50/src/adapter.c:resume_discovery()
Dec 17 07:35:56 bluetoothd[368]:
../bluez-5.50/src/adapter.c:new_long_term_key_callback() hci0 new LTK
for 5C:CB:99:7F:77:02 type 1 enc_size 16
Dec 17 07:35:56 bluetoothd[368]: ../bluez-5.50/src/device.c:device_set_bonded()
Dec 17 07:35:56 bluetoothd[368]:
../bluez-5.50/src/device.c:device_bonding_complete() bonding (nil)
status 0x00
Dec 17 07:35:56 bluetoothd[368]: ../bluez-5.50/src/adapter.c:resume_discovery()
Dec 17 07:36:15 bluetoothd[368]:
../bluez-5.50/src/adapter.c:dev_disconnected() Device
5C:CB:99:7F:77:02 disconnected, reason 3
Dec 17 07:36:15 bluetoothd[368]:
../bluez-5.50/src/adapter.c:adapter_remove_connection()
Dec 17 07:36:15 bluetoothd[368]:
../bluez-5.50/plugins/policy.c:disconnect_cb() reason 3
Dec 17 07:36:15 bluetoothd[368]:
../bluez-5.50/src/adapter.c:bonding_attempt_complete() hci0 bdaddr
5C:CB:99:7F:77:02 type 1 status 0xe
Dec 17 07:36:15 bluetoothd[368]:
../bluez-5.50/src/device.c:device_bonding_complete() bonding (nil)
status 0x0e
Dec 17 07:36:15 bluetoothd[368]:
../bluez-5.50/src/device.c:device_bonding_failed() status 14
Dec 17 07:36:15 bluetoothd[368]: ../bluez-5.50/src/adapter.c:resume_discovery()
Dec 17 07:36:36 bluetoothd[368]:
../bluez-5.50/src/agent.c:agent_disconnect() Agent :1.49 disconnected
Dec 17 07:36:36 bluetoothd[368]:
../bluez-5.50/src/agent.c:remove_default_agent() Default agent cleared
Dec 17 07:36:36 bluetoothd[368]:
../bluez-5.50/src/agent.c:agent_destroy() agent :1.49
Dec 17 07:36:36 bluetoothd[368]:
../bluez-5.50/src/agent.c:agent_unref() 0xfd1000: ref=0
Dec 17 07:36:37 bluetoothd[368]:
../bluez-5.50/src/agent.c:agent_ref() 0xfd2808: ref=1
Dec 17 07:36:37 bluetoothd[368]:
../bluez-5.50/src/agent.c:register_agent() agent :1.51
Dec 17 07:36:37 bluetoothd[368]:
../bluez-5.50/src/agent.c:unregister_agent() agent :1.51
Dec 17 07:36:37 bluetoothd[368]:
../bluez-5.50/src/agent.c:agent_disconnect() Agent :1.51 disconnected
Dec 17 07:36:37 bluetoothd[368]:
../bluez-5.50/src/agent.c:agent_destroy() agent :1.51
Dec 17 07:36:37 bluetoothd[368]:
../bluez-5.50/src/agent.c:agent_unref() 0xfd2808: ref=0

============= second connection : this device unpaired unintentionally
from the app system as soon as connected
===================================
Dec 17 07:36:37 bluetoothd[368]:
../bluez-5.50/src/agent.c:agent_ref() 0xfd2808: ref=1
Dec 17 07:36:37 bluetoothd[368]:
../bluez-5.50/src/agent.c:register_agent() agent :1.51
Dec 17 07:36:37 bluetoothd[368]:
../bluez-5.50/src/agent.c:add_default_agent() Default agent set to
:1.51 /org/bluez/agent
Dec 17 07:36:42 bluetoothd[368]:
../bluez-5.50/src/adapter.c:connected_callback() hci0 device
4D:EE:4F:F1:6F:FD connected eir_len 0
Dec 17 07:36:42 bluetoothd[368]:
../bluez-5.50/src/device.c:device_create() dst 4D:EE:4F:F1:6F:FD
Dec 17 07:36:42 bluetoothd[368]:
../bluez-5.50/src/device.c:device_new() address 4D:EE:4F:F1:6F:FD
Dec 17 07:36:42 bluetoothd[368]:
../bluez-5.50/src/device.c:device_new() Creating device
/org/bluez/hci0/dev_4D_EE_4F_F1_6F_FD
Dec 17 07:36:43 bluetoothd[368]:
../bluez-5.50/src/adapter.c:dev_disconnected() Device
4D:EE:4F:F1:6F:FD disconnected, reason 3
Dec 17 07:36:43 bluetoothd[368]:
../bluez-5.50/src/adapter.c:adapter_remove_connection()
Dec 17 07:36:43 bluetoothd[368]:
../bluez-5.50/src/adapter.c:adapter_remove_connection() Removing
temporary device /org/bluez/hci0/dev_4D_EE_4F_F1_6F_FD
Dec 17 07:36:43 bluetoothd[368]:
../bluez-5.50/src/device.c:device_remove() Removing device
/org/bluez/hci0/dev_4D_EE_4F_F1_6F_FD
Dec 17 07:36:43 bluetoothd[368]:
../bluez-5.50/src/device.c:btd_device_unref() Freeing device
/org/bluez/hci0/dev_4D_EE_4F_F1_6F_FD
Dec 17 07:36:43 bluetoothd[368]:
../bluez-5.50/src/device.c:device_free() 0xff3058
Dec 17 07:36:43 bluetoothd[368]:
../bluez-5.50/plugins/policy.c:disconnect_cb() reason 3
Dec 17 07:36:43 bluetoothd[368]:
../bluez-5.50/src/adapter.c:bonding_attempt_complete() hci0 bdaddr
4D:EE:4F:F1:6F:FD type 2 status 0xe
Dec 17 07:36:43 bluetoothd[368]: ../bluez-5.50/src/adapter.c:resume_discovery()



Thanks,
Calvin

2020년 11월 27일 (금) 오후 5:43, Jamie Mccrae <[email protected]>님이 작성:
>
> Hi Calvin,
> What type of address is it? If the device has a random resolvable address then this means once the device has paired and exchanged IRK that regardless of what random resolvable address the device uses, the other device will always know what the device's true address is and will use the correct encryption keys and details. If the device has a different random non-resolvable address or random static address which changes then you cannot match these against a pairing.
> Thanks,
> Jamie
>
> -----Original Message-----
> From: C K <[email protected]>
> Sent: 27 November 2020 06:46
> To: [email protected]
> Subject: BlueZ “Pin or Key missing” occurred even though it has already been paired
>
> EXTERNAL EMAIL: Be careful with attachments and links.
>
> Hello,
> I have an issue with my bluez device.
> I explained it on stackover flow.
> Help me about this please.
>
> https://stackoverflow.com/questions/65001891/bluez-pin-or-key-missing-occurred-even-though-it-has-already-been-paired
>
>
> Thanks,
> Calvin
> THIS MESSAGE, ANY ATTACHMENT(S), AND THE INFORMATION CONTAINED HEREIN MAY BE PROPRIETARY TO LAIRD CONNECTIVITY, INC. AND/OR ANOTHER PARTY, AND MAY FURTHER BE INTENDED TO BE KEPT CONFIDENTIAL. IF YOU ARE NOT THE INTENDED RECIPIENT, PLEASE DELETE THE EMAIL AND ANY ATTACHMENTS, AND IMMEDIATELY NOTIFY THE SENDER BY RETURN EMAIL. THIS MESSAGE AND ITS CONTENTS ARE THE PROPERTY OF LAIRD CONNECTIVITY, INC. AND MAY NOT BE REPRODUCED OR USED WITHOUT THE EXPRESS WRITTEN CONSENT OF LAIRD CONNECTIVITY, INC.