Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [D-BUS PATCH] Authentication
Date: Thu, 27 Oct 2005 16:53:08 +0200	[thread overview]
Message-ID: <1130424788.5163.15.camel@localhost.localdomain> (raw)
In-Reply-To: <e1effdeb0510270733q23c9cf01u9b3a597d1adbe258@mail.gmail.com>

Hi Claudio,

> Here are the patches based on the lastest BlueZ CVS. I am sending both
> approaches.
> Using signals is more clear in hcid side, however the clients will
> have to add flags to indicate that there is a authentication pending.
> Another problem is the error, using signals will not be possible send
> D-Bus error messages, therefore client will have to translate the
> status to a success or errors result.

we need the signal anyway, because a second application might be request
the authentication and if your first application displays different
icons for authenticated or unauthenticated connection then it should be
told that this connection is now authenticated. The same applies for the
encryption.

> PS: This is the message content for both approachs:
> * Signal approach
>   >>> D-Bus AuthenticationComplete signal
>   - String: peer bt address
>   - Byte: status
>   - Uint16: handle

We don't need the handle and the address. Use the address only, because
connection handles should be only used in hcid and the kernel.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2005-10-27 14:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-20 17:45 [Bluez-devel] [D-BUS PATCH] Authentication Claudio Takahasi
2005-10-22 13:08 ` Marcel Holtmann
2005-10-24 13:06   ` Claudio Takahasi
2005-10-24 13:19     ` Marcel Holtmann
2005-10-25 19:03       ` Claudio Takahasi
2005-10-27  0:37         ` Marcel Holtmann
2005-10-27 14:33           ` Claudio Takahasi
2005-10-27 14:39             ` Claudio Takahasi
2005-10-27 14:53             ` Marcel Holtmann [this message]
2005-10-27 16:33               ` Claudio Takahasi
2005-10-27 17:11                 ` Marcel Holtmann
2005-10-31 14:53                   ` Eduardo Rocha
2005-10-31 15:42                     ` 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=1130424788.5163.15.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --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