Received-SPF: pass (google.com: best guess record for domain of linux-bluetooth-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20191126191452.23603-1-alainm@chromium.org> <7223C834-7E4C-4521-9C1E-CA7C2F26EC63@holtmann.org>
In-Reply-To: <7223C834-7E4C-4521-9C1E-CA7C2F26EC63@holtmann.org>
From:   Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date:   Wed, 27 Nov 2019 17:54:26 +0200
Message-ID: <CABBYNZLg5+QM_+ZDBp3mfBnLq=3w05gTxb8=oRFLiYdTyDNsYA@mail.gmail.com>
Subject: Re: [PATCH] Blocked key mgmt Api definition
To:     Marcel Holtmann <marcel@holtmann.org>
Cc:     Alain Michaud <alainm@chromium.org>,
        Bluez mailing list <linux-bluetooth@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Marcel, Alain,

On Wed, Nov 27, 2019 at 8:02 AM Marcel Holtmann <marcel@holtmann.org> wrote=
:
>
> Hi Alain,
>
> > ---
> > doc/mgmt-api.txt | 33 +++++++++++++++++++++++++++++++++
> > 1 file changed, 33 insertions(+)
>
> patch has been applied.
>
> > +
> > +     This command can be used at anypoint to add to the list of blocke=
d keys.  Any connections that
> > +     are attempting to use the keys will be terminated. If a device tr=
ies to distribute the keys during
> > +     pairing, pairing will fail.
> > +
>
> However, I ended up rewording this part since it doesn=E2=80=99t sounded =
right to me. We can adjust this once we have the implementation to match ag=
ainst, but for now I kept it simple. Oh, and we need to stay within the rul=
e that it has to readable in 80 character wide terminal. So no long lines.

Will there be a follow up change to add support for this in the
daemon, I suspect we will need to have it given as a file or will the
blacklist be just hardcoded?

--=20
Luiz Augusto von Dentz