[Home]

Summary:ASTERISK-15939: [patch] Bluetooth linkkey is never stored and as a result phone PIN is requested every time a new connection is started
Reporter:Daniel A. Veiga (dveiga)Labels:
Date Opened:2010-04-10 21:41:31Date Closed:2011-07-26 15:20:45
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Addons/chan_mobile
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) chan_mobile.diff
( 1) chan_mobileV2.diff
Description:I can´t tell since what version, because I jumped from 'bluez-libs-3.35-1.fc8' to 'bluez-libs-4.42-9.fc11.x86_64', but the security defaults of the bottom layers changed. As a consecuence the linkkey (the secret negotiated between the two bluetooth devices) is not stored on disk, and a new sync is started every time a new connection is started with the phone.
The proposed patch sets the socket options to avoid the problem.
Comments:By: Daniel A. Veiga (dveiga) 2010-05-09 20:23:09

Yesterday I was upgrading an old system and I decided to apply the latest patches to chan_mobile. When I got to mine I discovered it didn't compile. The problem was I introduced it because bluetooth's security changed and a new socket option (BT_SECURITY) was added to adjust it. The patch is not necessary for versions earlier than this change and it does not compile either.
Looking a little bit further into the problem I found BT_SECURITY was introduced in bluez 4.27. As the patch is not needed in earlier versions, I changed it to introduce a #ifdef BT_SECURITY to exclude the patch under those versions.


By: Leif Madsen (lmadsen) 2011-01-28 11:49:24.000-0600

I think the issues you have submitted should probably be reviewed and then get you commit access. Please contact me if you're interested in becoming the chan_mobile maintainer. Thanks!
By: Leif Madsen (lmadsen) 2011-07-26 15:20:39.182-0500

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines