From: Ronny L Nilsson <bb@arbetsmyra.dyndns.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Smartcard replacement security?
Date: Wed, 23 Mar 2005 16:45:52 +0100 [thread overview]
Message-ID: <20050323154630.F2A554A3@arbetsmyra.dyndns.org> (raw)
In-Reply-To: <1111590295.1916.3.camel@pegasus>
> > paired of course. But then, how "unsafe" is this realy? Can someone
> > else spoof my phone and thus fooling my computer other than using
> > some kind of brute force? Authentication is made two-ways, right?
>
> this depends on how your automatic unlocking is working. If you know
> the link key and the BD_ADDR you can spoof anything.
> Marcel
Sure, but I was woundering how hard it is for an intruder to guess the
link key. Of course if he sniff the traffic while doing the pairing
with PIN he knows my code, but if he misses this pairing, then what is
his chanses? The BD_ADDR is of course public (via a nearby scan).
I haven't read the whole spec but minor parts of it. It says
authentication can be made one-way or both-ways. Do BlueZ support both
of these ways? Which is the most commonly used?
Regards
/Ronny
-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-03-23 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 9:41 [Bluez-users] Smartcard replacement security? Ronny L Nilsson
2005-03-23 15:04 ` Marcel Holtmann
2005-03-23 15:45 ` Ronny L Nilsson [this message]
2005-03-23 17:38 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050323154630.F2A554A3@arbetsmyra.dyndns.org \
--to=bb@arbetsmyra.dyndns.org \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox