Re: Auto-connect after disconnection from user on trusted devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks for sharing your thoughts!

On Wed, Apr 22, 2020 at 2:12 AM Luiz Augusto von Dentz
<luiz.dentz@xxxxxxxxx> wrote:
>
> Hi,
>
> On Mon, Apr 20, 2020 at 9:30 PM Yun-hao Chung <howardchung@xxxxxxxxxx> 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



[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux