Return-Path: MIME-Version: 1.0 References: In-Reply-To: From: Luiz Augusto von Dentz Date: Thu, 17 May 2018 10:55:05 +0300 Message-ID: Subject: Re: question: auto-trust after pairing To: lpeltan@insys-tec.de Cc: "linux-bluetooth@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Hi Libor, On Wed, May 16, 2018 at 2:01 PM Libor Peltan wrote: > Hello everyone, > I'd like to ask about specific configuration of bluetooth daemon. > 1. How it works for me: > I'm running BlueZ 5.47 on an ARMv7-powered board with a Qualcomm chip. > When a device (mostly a phone) connects via bluetooth, it is paired automatically without any PIN exchange. > In order to use PAN protocol over bluetooth, the connected device needs to be trusted. > To achieve this, I created an external program, that communicates with bluetoothd via DBus. When a DBus message arrives informing about new paired device, the program responds (if some policy conditions are fulfilled) with DBus message requesting trusting this device. Overall, this makes an approx 0.5 secs delay between pairing and trusting of the device. > 2. My problem > When testing an iPhone in the role of the connecting device, after the pairing I can see an error message on the iPhone. After trying to connect again, it already works. It's not nice, for the future users, to always receive an error message on first attempt - I need to avoid this. > I observed that after pairing, the iPhone immediately (in 10 millis) tries to connect to PAN. This is not yet possible, since it's not yet trusted. This causes the error message. > 3. My question > Is there a way to change bluetoothd, so that he automatically trusts a device when it pairs? > Is it possible to turn this "auto-trust" mode on and off without restarting bluetoothd? Even in case of just works pairing there should be a request to the agent to accept it, trust affects connection authorization perhaps we are not doing it properly for PAN since there should delay a little bit the accepting of the L2CAP connection but that is done for all profiles so Id be surprised that is what is causing the problem. > Thanks much for the answers or any other usefult tips! > Libor Peltan > -- > To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Luiz Augusto von Dentz