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 17:58:14 +0200 [thread overview]
Message-ID: <426E6516.3010403@gmx.ch> (raw)
In-Reply-To: <1114530540.10706.301.camel@pegasus>
Hello Marcel
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...
I assume it's easier to backport it to 2.6.7, if 2.4.26 is easier, please
let me know.
>>Can this encryption be reached in another way?
>
>
> In general yes. You must call the HCI functions, but it is impossible to
> call them at the correct time (after the SABM).
ok. so backporting would be the best option.
>>Where are the link keys saved? I'm unable to find them.
>
>
> Starting with bluez-utils-2.16 under /var/lib/bluetooth/*/linkkeys.
found them, thank you.
>>Is there something that has to be paid attention to if I do encryption like
>>this? Does the password/Dongle/... influence the encryption strength?
>
>
> The encryption key size is the only thing that may vary. For CSR chips
> it can be between 56 bits and 128 bits depending on the firmware.
ok. thank you.
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
next prev parent reply other threads:[~2005-04-26 15:58 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 [this message]
2005-04-26 16:19 ` Marcel Holtmann
2005-04-26 16:42 ` Marco Trudel
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=426E6516.3010403@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