From: Marcel Holtmann <marcel@holtmann.org>
To: Nils Faerber <nils.faerber@kernelconcepts.de>
Cc: bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] Pairing fails with RFCOMM
Date: Mon, 09 Feb 2004 17:14:14 +0100 [thread overview]
Message-ID: <1076343254.6869.214.camel@pegasus> (raw)
In-Reply-To: <1076342698.1167.90.camel@localhost>
Hi Nils,
> This has already been solved, sorry for bothering.
> My problem was that bthid is not very verbose unless you look into the
> daemon-log - I did not :(
> So I did not see that it already had connected upon first try! All other
> tries after that failed of course.
> BTW: "bthid -l" did not show this connection so there is still some
> glitch...
I know, there is much more work to do ;)
> BTW: The dongle in use is the EPOX USB dongle from the
> keyboard-mouse-dongle package. Switching from HID to HCI also worked
> like a charm - well done!
Thanks. And even the Logitech dongle can be switched. Some Apple iBooks
should also work like this.
> Now I only have to figure out how to force the pairing on the keyboard.
> >From what I know it should work in a way that you can input the pin on
> the keyboard. But I can simply connect to it without authentication...
That is one of the problems that must be solved. If you read the HID
specification then you will see that the host stack is responsible for
doing the authentication. But you can't enable auth per se, because the
connection to a mouse must be done (the Apple mouse is the exception)
without authentication and encryption. So you must first identify the
type of the HID device. This can be done through the class of device
value on incoming connection, but we don't make this value accessable
from userspace in BlueZ. Or you use the HID descriptor and then issue a
HCI_Authenticate command if it is a keyboard.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-02-09 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 17:03 [Bluez-devel] Pairing fails with RFCOMM Nils Faerber
2004-02-06 19:57 ` Marcel Holtmann
[not found] ` <1076337219.2892.57.camel@localhost>
2004-02-09 15:01 ` Marcel Holtmann
[not found] ` <1076339124.1169.67.camel@localhost>
2004-02-09 15:08 ` Marcel Holtmann
[not found] ` <1076340484.1167.79.camel@localhost>
2004-02-09 15:56 ` Marcel Holtmann
[not found] ` <1076342698.1167.90.camel@localhost>
2004-02-09 16:14 ` Marcel Holtmann [this message]
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=1076343254.6869.214.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sf.net \
--cc=nils.faerber@kernelconcepts.de \
/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.