From: Frederic Danis <frederic.danis@palmsource.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Problem to connect hci as non-root
Date: Thu, 26 May 2005 18:48:37 +0200 [thread overview]
Message-ID: <4295FDE5.1080404@palmsource.com> (raw)
In-Reply-To: <1117122236.12036.49.camel@pegasus>
I agree with you that Linux should not need a pairing/bonding
application. But we got one and want to keep it when porting our
applications to Linux.
I do not know differences between setsockopt() and ioctl() enough to
give you an advice, sorry.
Is there any way to force the authentication (encryption) for a L2CAP
socket (at creation time for example) ?
Regards
Fred
-----------------------------------------------
It is not by improving the oil lamp that one invents the electric bulb!
-----------------------------------------------
Danis Frederic PalmSource Europe
Software engineer
Mail : mailto:frederic.danis@palmsource.com
-----------------------------------------------
Marcel Holtmann wrote:
>Hi Fred,
>
>
>
>>OK, I thought about this but I don't know how to start the
>>authentication from an L2CAP socket.
>>Is it possible ?
>>Is it possible to acces to hci command from the L2CAP socket ?
>>
>>
>
>you can get the ACL handle through getsockopt() and then open an HCI raw
>socket and send the command. But I think the Authentication_Requested
>command will also fail due to limited permissions.
>
>For some time I thought to add the possibility to do authentication and
>enable encryption through the socket interface or L2CAP and RFCOMM. At
>the moment I haven't decided if I wanna do that with setsockopt() or
>with ioctl(). Feel free to suggest something.
>
>Do you think a pairing/bonding application is needed for Linux? If one
>side requests the authentication we will handle it through PIN helper
>and the rest is handled inside hcid. Deleting the link key is the only
>job we might need an application for.
>
>Regards
>
>Marcel
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by Yahoo.
>Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
>Search APIs Find out how you can build Yahoo! directly into your own
>Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
>_______________________________________________
>Bluez-devel mailing list
>Bluez-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-05-26 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 15:09 [Bluez-devel] Problem to connect hci as non-root Frederic Danis
2005-05-26 15:20 ` Marcel Holtmann
2005-05-26 15:33 ` Frederic Danis
2005-05-26 15:43 ` Marcel Holtmann
2005-05-26 16:48 ` Frederic Danis [this message]
2005-05-26 17:02 ` Marcel Holtmann
2005-05-29 16:57 ` [Bluez-devel] l2ping and timeout ligi
2005-05-29 18:09 ` Marcel Holtmann
2005-05-29 19:12 ` ligi
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=4295FDE5.1080404@palmsource.com \
--to=frederic.danis@palmsource.com \
--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 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.