> Become? Become?! You stole my comment! No but in all seriousness, this is a long-standing issue. The A) requirement of making BT-enabled devices backwards co

> Become? Become?! You stole my comment! No but in all seriousness, this is a long-standing issue. The A) requirement of making BT-enabled devices backwards compatible, B) the monstrous stack of protocols involved in like every use-case, & C) an assumption that Spread-Spectrum Frequency Hopping @ the physical layer is a substitute for encryption, all combine to make a BT kind of especially terrifying. Take for example the Nike Fit Band, an iconic bluetooth peripheral that's been on the market for some time: 2015: https://securelist.com/how-i-hacked-my-smart-bracelet/69369/ https://securelist.com/how-i-hacked-my-smart-bracelet/69369/ 2016: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4737495/ https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4737495/ 2017: https://www.zdnet.com/article/bluetooth-security-flaw-blueborne-iphone-android-windows-devices-at-risk/ https://www.zdnet.com/article/bluetooth-security-flaw-bluebo... I'm sure I can find one from last year as well, but you get the point. Also here's this for good-measure: http://ubertooth.blogspot.com/ http://ubertooth.blogspot.com/