Linux bluetooth development
 help / color / mirror / Atom feed
From: Marco Trudel <mtrudel@gmx.ch>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] implementing security mode 2 or 3
Date: Tue, 26 Apr 2005 18:42:08 +0200	[thread overview]
Message-ID: <426E6F60.2020000@gmx.ch> (raw)
In-Reply-To: <1114532376.10706.310.camel@pegasus>



Marcel Holtmann wrote:
> Hi Marco,
> 
> 
>>>>this works great with a 2.6.11 kernel.
>>>>Unfortunately I'm bound to kernel 2.4.26 or 2.6.7.
>>>>2.4.26 doesn't work. It just let's remote devices connect...
>>>>Do you know if 2.6.7 will?
>>>
>>> 
>>>the 2.6.7 will fail. The needed security hooks are introduced with
>>>2.6.10 and the RFCOMM service level security with 2.6.11 according to my
>>>patch logs.
>>> 
>>>
>>>>If not, which part of the kernel has to be fixed? Is it a part of bluez?
>>>
>>> 
>>>It is inside the BlueZ core and the RFCOMM layer.
>>
>>How long would you have to backport that to kernel 2.6.7?
>>Maybe we can arrainge something with a donation...
> 
> 
> tell me what interfaces are you going to use. Is it always USB? What
> kernel layers are involved? RFCOMM, BNEP, CMTP, HIDP?

always USB. RFCOMM services.

authentication/encryption enabled as suggested on the list:
    int opt = RFCOMM_LM_AUTH|RFCOMM_LM_ENCRYPT;
    setsockopt(sock, SOL_RFCOMM, RFCOMM_LM, &opt, sizeof(opt));

> You will need more than this two patches for a 2.6.7 based kernel,
> because there are some serious problems, too.

actually I never run into problems with the 2.4 kernel. But I think it 
would definitely make sense to have this things fixed too...

>>I assume it's easier to backport it to 2.6.7, if 2.4.26 is easier, please 
>>let me know.
> 
> 
> The 2.6.7 backport will be end up in selecting patches and fixes small
> things, while for 2.4.26 you need to rewrite most of the patches.

ok, so it's 2.6.7...


regards
Marco


-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start!  http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-04-26 16:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-26  9:39 [Bluez-users] implementing security mode 2 or 3 Marco Trudel
2005-04-26  9:53 ` Fred Schaettgen
2005-04-26 15:22   ` Marco Trudel
2005-04-26 15:49     ` Marcel Holtmann
2005-04-26 15:58       ` Marco Trudel
2005-04-26 16:19         ` Marcel Holtmann
2005-04-26 16:42           ` Marco Trudel [this message]
2005-04-26 17:00             ` Marcel Holtmann
2005-04-26 17:32               ` Marco Trudel
2005-04-27  8:55                 ` Marco Trudel
2005-04-27 10:41                   ` Marcel Holtmann
2005-04-27 11:28                     ` Marco Trudel
  -- strict thread matches above, loose matches on Subject: below --
2005-04-25 14:35 Marco Trudel

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=426E6F60.2020000@gmx.ch \
    --to=mtrudel@gmx.ch \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox