All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timothy Murphy <tim@birdsnest.maths.tcd.ie>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Why is pairing so complicated?
Date: Thu, 12 Jul 2007 20:45:53 +0100	[thread overview]
Message-ID: <f760dh$np6$1@sea.gmane.org> (raw)

Why does bluez make pairing such a complicated issue?
Why not just have a file with the passkey in it?

-- 
Timothy Murphy  
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2007-07-12 19:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12 19:45 Timothy Murphy [this message]
2007-07-13 13:21 ` [Bluez-users] Why is pairing so complicated? Charles Majola

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='f760dh$np6$1@sea.gmane.org' \
    --to=tim@birdsnest.maths.tcd.ie \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.