public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Jose Vasconcellos <jose@vasmac.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bonding
Date: Tue, 07 Nov 2006 15:22:31 -0500	[thread overview]
Message-ID: <4550EB07.4030106@vasmac.com> (raw)
In-Reply-To: <1162933029.4793.7.camel@aeonflux.holtmann.net>

Marcel Holtmann wrote:
> Hi Jose,
>
>   
>>>>>>>> I see that the dbus message RemoveBonding clears the link key
>>>>>>>> on the bluetooth adapter but does not remove the entry from the
>>>>>>>> linkkeys file. Afterwards ListBondings still shows a bonding and
>>>>>>>> CreateBonding reports that a bonding already exists. Is this the
>>>>>>>> correct behavior?
>>>>>>>>         
>>>>>>>>             
>>>>>>>>                 
>>>>>>> actually it should remove the entry from the linkkeys file. Otherwise
>>>>>>> this is a bug. Can you check the log files for errors.
>>>>>>>       
>>>>>>>           
>>>>>>>               
>>>>>> I don't see any error message in syslog or anywhere else.
>>>>>> The commands themselves don't seem to report anything
>>>>>> unusual.
>>>>>>     
>>>>>>         
>>>>>>             
>>>>> I am pretty sure that it works as expected. What distro do you have
>>>>> running. Maybe SELinux is restricting access to /var/lib/bluetooth/
>>>>>       
>>>>>           
>>>> OK, I did a little bit of digging and here's a better description:
>>>> Removing a device that has lower case hex numbers does not
>>>> remove it from the linkkeys file. You must use upper case.
>>>>     
>>>>         
>>> that should have been fixed. What version of bluez-utils are you
>>> running.
>>>   
>>>       
>> I'm running the latest, version 3.7 on Ubuntu 6.06.
>>     
>
> check the CVS when it was fixed (if we didn't forget it). I am pretty
> sure that if was fixed before 3.7, but I might be mistaken here. If it
> is still broken or the patch was incomplete, please fix it and send in a
> patch for it.
>
> Regards
>
> Marcel
>   
Looks like the problem is that the function textfile_del in 
common/textfile.c
calls write_key with the icase parameter set to 0. This is NOT fixed in CVS.

Jose


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-11-07 20:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 15:16 [Bluez-devel] Bonding Jose Vasconcellos
2006-11-07 15:26 ` Marcel Holtmann
2006-11-07 17:16   ` Jose Vasconcellos
2006-11-07 18:25     ` Marcel Holtmann
2006-11-07 19:36       ` Jose Vasconcellos
2006-11-07 20:41         ` Marcel Holtmann
2006-11-07 19:50           ` Jose Vasconcellos
2006-11-07 20:00             ` [Bluez-devel] Role switching Olivier Le Pogam
2006-11-07 20:57             ` [Bluez-devel] Bonding Marcel Holtmann
2006-11-07 20:22               ` Jose Vasconcellos [this message]
2006-11-07 20:28               ` [Bluez-devel] Case handling (was: Bonding) Jose Vasconcellos
2006-11-07 21:37                 ` 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=4550EB07.4030106@vasmac.com \
    --to=jose@vasmac.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox