From: Biman Paul <biman.paul@samsung.com>
Date: Wed, 11 Oct 2017 09:12:13 +0000 (+0900)
Subject: fix unable to pair with headset having pin '1234'
X-Git-Tag: accepted/tizen/4.0/unified/20171023.120736~3
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=5d79387d035ed704a46cde05008002d83ba96141;hp=34626f4d76a257ad0d65be5a212d09ce8d516107;p=platform%2Fcore%2Fconnectivity%2Fbluetooth-frwk.git

fix unable to pair with headset having pin '1234'

[Problem] unable to pair with headset having pin '1234'
[Cause & Measure] For headset, usually default pin is
'0000' and request is Pairing pin is send as '0000'. But
when pin is not '0000' first attempt fails and remote
device BD address is blacklisted(saved in a file) and for
all future requests blacklisted devices are checked and
pin popup is shown.
But here bt-service is unable to write to blacklist file.
Measure:
1. Allow write mode for blacklist file.
2. Give appropriate smack label.

[Checking Method] Use Mecapp:
1. Set COD such as Mecapp is recognised as Headset.
2. Initiate a pairing request to Mecapp.
3. Give pin 1234 or anything other than '0000' in mecapp.

Change-Id: I8629e782e98cbce88822094d1765fe4bad38994b
---

diff --git a/packaging/bluetooth-frwk.spec b/packaging/bluetooth-frwk.spec
index 7bc2f59..f164130 100644
--- a/packaging/bluetooth-frwk.spec
+++ b/packaging/bluetooth-frwk.spec
@@ -316,6 +316,10 @@ ln -s ../bluetooth-frwk.service %{buildroot}%{_unitdir}/starter.target.wants/blu
 
 %postun -p /sbin/ldconfig
 
+%post service
+/usr/bin/chsmack -a '_' %{_varlibdir}/bluetooth/auto-pair-blacklist
+/usr/bin/chown 5001:100 %{_varlibdir}/bluetooth/auto-pair-blacklist
+
 %files
 %manifest %{name}.manifest
 %license LICENSE
@@ -361,6 +365,7 @@ popd
 %{_bindir}/bluetooth-frwk-test
 %{_varlibdir}/bluetooth
 %{_prefix}/etc/bluetooth
+%attr(-,owner,users) %{_varlibdir}/bluetooth/auto-pair-blacklist
 
 %files httpproxy
 %manifest %{name}.manifest