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;
Content-Type: text/plain;
        charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Re: [PATCH] Blocked key mgmt Api definition
From:   Marcel Holtmann <marcel@holtmann.org>
In-Reply-To: <20191126191452.23603-1-alainm@chromium.org>
Date:   Wed, 27 Nov 2019 07:00:08 +0100
Cc:     Bluez mailing list <linux-bluetooth@vger.kernel.org>
Content-Transfer-Encoding: 8BIT
Message-Id: <7223C834-7E4C-4521-9C1E-CA7C2F26EC63@holtmann.org>
References: <20191126191452.23603-1-alainm@chromium.org>
To:     Alain Michaud <alainm@chromium.org>
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

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 blocked keys.  Any connections that
> +	are attempting to use the keys will be terminated. If a device tries to distribute the keys during
> +	pairing, pairing will fail.
> +

However, I ended up rewording this part since it doesn’t sounded right to me. We can adjust this once we have the implementation to match against, but for now I kept it simple. Oh, and we need to stay within the rule that it has to readable in 80 character wide terminal. So no long lines.

Regards

Marcel