Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
Security Technology

How Good Is BlueTooth's Security? 13

maliabu writes "If (not when) BlueTooth becomes really popular or populated in all the personal devices, will we start experiencing another wave of frauds similar to the current credit card strip-reading, or ATM machine shoulder-spying incidents? In this article about BlueTooth Security, the author asks 'but is Bluetooth secure enough for larger ad hoc networks, money transfers and transferring other sensitive information?' Even when the security standard becomes higher in BlueTooth, will the end users become victims of themselves by neglecting simple security rules, similar to not covering the keypad when entering your pin number? Remember personal devices such as mobile phone, heartrate sensor, blood-pressure alarm, vision-correction lenses etc, are more 'forgettable' than laptops/computers on WiFi. And the chances of strangers getting close enough to it is also higher, such as in the train, bus, cinema etc."
This discussion has been archived. No new comments can be posted.

How Good Is BlueTooth's Security?

Comments Filter:
  • Uh... Yes? (Score:4, Interesting)

    by Anonymous Coward on Tuesday June 10, 2003 @08:35AM (#6160150)
    Timothy asks:
    'will the end users become victims of themselves by neglecting simple security rules, similar to not covering the keypad when entering your pin number?'

    I think that we all know the answer to that one...

    As a matter of fact, the whole gist of this paper seems to point less to overt flaws in bt's implementation and more to simple user error/laziness.
    A good read, though.

    slomotion
  • by HaloZero ( 610207 ) <protodekaNO@SPAMgmail.com> on Tuesday June 10, 2003 @08:36AM (#6160160) Homepage
    ...when you're dead [slashdot.org].

    To be honest, I never found much use for BlueTooth. The idea is nice, but... we're not ready for it, yet. And I've found other solutions which fit the bill better than BlueTooth.
    • To be honest, I never found much use for BlueTooth

      Nor have I - though I know my mobile phone (Ericsson) supports it. I'm probably being a bit conservative, but I haven't been burned yet by trusting dubious technology. (The corollary to that is that I have been burned by trusting flesh-and-blood people. I think I've lost my money with these guys [cybershire.com] quite recently.)

    • I use a Bluetooth mouse, and with regards to mobile phone - it beats the shit out of IR.

      I think the big issue with acceptance of bluetooth is peoples misguided understanding of it's uses. It's not another 802.11x, it's short area wireless. "Personal Area Network" as I've heard it refered to.

      I think this is brilliant for these types of uses especially without the worry that someones on the street outside trying to hack into your bluetooth equipment.
  • wireless USB or you already know that ?

    So, whatever encryption that can be used for USB can also be used for Bluetooth. Correct me if I am wrong.
  • I must get one of those

  • If there's any possibility of a security hole, someone is going to try and take advantage of it.

    And probably will succeed.

    And probably get their wrist slapped.

  • Analysis a bit weak (Score:5, Interesting)

    by OpenMind(tm) ( 129095 ) on Tuesday June 10, 2003 @05:24PM (#6165620)
    It really seems like the author decided what he wanted to conclude before he started his study. His conclusions are mostly fluff. Sure the out of band PIN exchange is a bit clunky, but this isn't really a vulnerability. Nothing seamless is going to happen without some sort of certificate authority. Anything else is going to require authentication off the wire.

    Battery draining denial of service scheme? Seems like this will be an issue for any limited power mobile device that is listening for connections. As for no defense against it, leaving your device "undiscoverable" and only talking to trusted devices is a good start.

    The mention of a divide-and-conquer attack that cannot in fact be used probably doesn't belong in the conclusions.

    PINs are, I believe, alphanumeric in most user interfaces, giving us more like 1.7 million keys for a four-digit key length. Still not that great a key space, but that's why you're allowed 16 octets.

    It seems like the remainder of the conculsions make the assumption of bad application-level choices of keys and key types. I will acknowledge that this can derail pretty much any encryption scheme.

    Personally, I sort of wonder why more standard algorithms were not used, such as RC*, Diffie-Hellman, etc. Also, this seems like it could really use a certificate of PGP-like "web of trust" to support it.

    • I agree. The weaknesses mentioned are not Bluetooth-specific. If you use the 16 octets for the PIN, there is nothing wrong with the security, and building a Diffie-Hellman exchange on the application level to obtain the PIN automatically should not pose a problem.

      There are some security issues in the E0 algorithms, but the efecive key length is still around 73-84 bits which is more than enough (article here [nec.com]).

C makes it easy for you to shoot yourself in the foot. C++ makes that harder, but when you do, it blows away your whole leg. -- Bjarne Stroustrup

Working...