public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Isabel Maldonado <Isabel.Maldonado@student.uib.no>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Is it posible to generate passkey on some external device, and then update the BT-device (without MMi) automatically?
Date: Thu, 29 Nov 2007 12:41:58 +0100	[thread overview]
Message-ID: <474EA586.5010602@student.uib.no> (raw)

Hi,

Useally a BT device without MMI uses a fixed passkey. If this device is
a public device, so that a group of people can connect to it, each
person should have a unique passkey with the public device.

I wonder if it is possible with BlueZ to let some other external
controll/system generate a unique passkey for each person that wishes to
connect to this public device in the future.

The external controll/system updates the public device and sends the new
passkey through a secure channel.

Is there some function in BLueZ for this? Is this be possible?

-- Tripas


-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2007-11-29 11:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 11:41 Isabel Maldonado [this message]
2007-11-29 20:17 ` [Bluez-devel] Is it posible to generate passkey on some external device, and then update the BT-device (without MMi) automatically? Marcel Holtmann
2007-11-30  9:23   ` Isabel

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=474EA586.5010602@student.uib.no \
    --to=isabel.maldonado@student.uib.no \
    --cc=bluez-devel@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