security - How Bluetooth Passkey protects agains MITM attack -


I'm reading Bluetooth low energy: The developer is confused about the protection against the booklet and the MITM.

The book says after the exchange coupling, a random number is generated on both sides. With that random number, a confirmation value is calculated. Then the confirmation value is exchanged between the two sides, after which the random number is detected.

The exchanged messages are in this type of coupling. [April 25 18:04: 43.9 9] [Send SMP] SEMPair Request Request [APR 25 16: 53: 09.005] [SMP Receive] LE SMP Combination Response Command [25 April 16: 53: 09.01 9] [Send SMP] Confirmation of SMP Coupling Command [April 25 16: 53: 14.016] [SMP Receive] Confirm Let's Take SMP Coupler Command [April 25 16: 53: 14.017] [Send SMP] SMP Sump Pair for Random Commanding [25 April 16: 53: 14.076] [SMP Receive] LE SMP Pair Random Command

The book claims that it prevents MITM from attacking because MITM will be estimated at 2 ^ 128 potential random numbers to calculate the confirmation value.

My question is how does this help prevent MITM attack. I mean, if I am MITM, then I can carry the confirmation number from one end to the other without the need for calculation.

I am sure that I will remember something

What do you mean by MITM attacks It does not remember what it means.

Just passing the data obtained from one device to another does not make you an MITM attacker just an MITM.

To do "attack" you must modify the data before you pass it without actually receiving it. Ideally you will not just screw up the communication, but you will also make meaningful changes (for example, keeping the sender's signature in place of the destination bank account number with you, so that you get money in return for the original sender).

By not making any modifications to the data that you block (before sending), you only act as repeater .

Comments

Popular posts from this blog

c - Mpirun hangs when mpi send and recieve is put in a loop -

python - Apply coupon to a customer's subscription based on non-stripe related actions on the site -

java - Unable to get JDBC connection in Spring application to MySQL -