When I said: "you do realize.." I wasn't referring to Garry alone. I was referring to the fact that three posts are "gloating" on the issue not even realizing it is fixed.
Bluetooth is not a good protocol for file transfer (from a mobile phone for example). But it is really good for a lot of things (low latency, low power consumption). For example, I created a Debian based RC car which uses serial over bluetooth contolled from a phone. Try pull that off in any sensible sense with some other protocol. WIFI is an option, but power hungry and you most likely need a router or network, RF or infra red.. yes but how do you connect it to a phone? What about audio streaming? Yeah, sure, you can stream over Wifi, but considering the power usage it does not make a lot of sense in all situations...
But yes, Garry. I actually think that it is immoral - in a way - that in that other thread (
http://forums.debian.net/viewtopic.php?f=7&t=134698) you told a guy that was attempting to use a bluetooth device (that he needs for work!) to not use it because "bluetooth is insecure". Then you referenced a vulnerability that is already fixed. All networking protocols and software have vulnerabilities, yet you are not advocating the non-use of Wifi or Ethernet etc. You don't like bluetooth. FIne, but say it then. To me that post read as trying to masquerade your opinion as fact.
For what it's worth, people should notice that this vulnerability is fixed in bluez 5.47 upstream. That means that currently it is not fixed in Debian testing (5.45) and Sid (5.46), only in Stretch and Jessie.