Hi,
I'd like to know: when using Buttonless Secure DFU Service without bonds, wich is the proper way to prevent a central device to set a new advertisement name for the bootloader? (SDK 14.1.0)
Hi,
I'd like to know: when using Buttonless Secure DFU Service without bonds, wich is the proper way to prevent a central device to set a new advertisement name for the bootloader? (SDK 14.1.0)
I would say this can easily be implemented by modify the case DFU_OP_SET_ADV_NAME in ble_dfu_buttonless_on_ctrl_pt_write() in ble_dfu_unbonded.c to respond DFU_RSP_OP_CODE_NOT_SUPPORTED , i.e.
case DFU_OP_SET_ADV_NAME: rsp_code = DFU_RSP_ADV_NAME_INVALID; break;
However, I do not know if this will break the compability with the DFU option using nRF Connect Mobile/ Desktop apps. But then again, I reckon that you might create your own app that uses our DFU libraries.
I would say this can easily be implemented by modify the case DFU_OP_SET_ADV_NAME in ble_dfu_buttonless_on_ctrl_pt_write() in ble_dfu_unbonded.c to respond DFU_RSP_OP_CODE_NOT_SUPPORTED , i.e.
case DFU_OP_SET_ADV_NAME: rsp_code = DFU_RSP_ADV_NAME_INVALID; break;
However, I do not know if this will break the compability with the DFU option using nRF Connect Mobile/ Desktop apps. But then again, I reckon that you might create your own app that uses our DFU libraries.