Master Emulator firmware has no MITM?

[Elias]

I'm using Master Control Panel for PC to try to test bonding with MITM security on the peripheral I'm developing, and I suspect there's something wrong with the Master Emulator device that MCP is controlling. When I sniff the packets between the Master Emulator device and a device running the (unaltered) Glucose Monitor example, I get this:

After the Master Emulator sends a connection request, I see one packet with MITM and one without. The Glucose Monitor has the SEC_PARAM_MITM bit set in the source code, so I assume that's the one with MITM, and that means the Master Emulator must be the other one. So, what's going on? MCP is supposed to support OOB, which is an implementation of MITM protection, so shouldn't the firmware that it uses have MITM enabled?

The hardware I'm using is: Master Emulator (v0.11.0)- nRF51 dev board (PCA10028); BLE Sniffer- nRF51 dev dongle (PCA10031); Glucose Monitor- nRF52 dev board (PCA10040)

[FormerMember]

Instead of using Master Control Panel, I would recommend you to use the newly released nRF Connect (PC). It is a new and more advanced version of Master Control Panel. If initiating bonding, you can for instance choose MITM or no MITM.

In Master Control Panel (PC) you can change the IO capabilities in for the Master Control Panel device in File -> Options -> Security. When the correct IO capabilities are set, there should be MITM bonding the peripheral requires it. Remember to set correct IO capabilities in the peripheral code as well.

Table 2.8 in the Bluetooth Core Specification v.4.2, vol 3, part H, chapter 2.3.5.1 shows which IO capabilities that result in which type of bonding:

[Elias]

Although this didn't directly answer my question, recommending nRF Connect made it moot.