Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <CAPHZWUeGeaN5jmNHv56VzSsdmCvS1WKfSnaYE+YCfd5E8+3S-Q@mail.gmail.com>
In-Reply-To: <CAPHZWUeGeaN5jmNHv56VzSsdmCvS1WKfSnaYE+YCfd5E8+3S-Q@mail.gmail.com>
From:   Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date:   Tue, 21 Apr 2020 11:12:40 -0700
Message-ID: <CABBYNZJ4MhhEWvxX+hw8fR9uOpqXd8XWQBsy2VjP_dVtL0R+7w@mail.gmail.com>
Subject: Re: Auto-connect after disconnection from user on trusted devices
To:     Yun-hao Chung <howardchung@google.com>
Cc:     Bluez mailing list <linux-bluetooth@vger.kernel.org>,
        Sonny Sasaka <sonnysasaka@google.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi,

On Mon, Apr 20, 2020 at 9:30 PM Yun-hao Chung <howardchung@google.com> wrote:
>
> Hi linux-bluetooth,
>
> Bluez doesn't disable auto-connect for trusted devices even in
> device.Disconnect. This causes users can't disconnect from peripherals
> unless they untrust the device.
>
> The behavior seems to change into this way intentionally after this change:
> https://www.spinics.net/lists/linux-bluetooth/msg72898.html
>
> I would like to understand why this change is needed and what is the
> suggestion to disconnect a trusted device.

This has been there for a while but if I recall correctly the problem
is that we cannot really tell when the auto-connect was disabled,
besides it was not really honoring that in case the daemon is
restarted, etc, so instead of having yet another setting to persist it
was simpler to just use the trust, or block, properties to control
auto-connect which are persisted properly, that said maybe we can make
disconnect auto block the device and then connect to unblock
automatically but I think that having the application set the block
property is probably clearer that we don't want it to be reconnected.

-- 
Luiz Augusto von Dentz