Content-Type: text/plain;
        charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Subject: Re: Bluetooth ECDH selftest failed (endianness issue?)
From:   Marcel Holtmann <marcel@holtmann.org>
In-Reply-To: <CAEQQxWzdBy9JOC7+oQTBJ35Gov1CDk17fy+XH=jha8MuT9fy9Q@mail.gmail.com>
Date:   Sat, 29 Dec 2018 08:35:21 +0100
Cc:     linux-bluetooth@vger.kernel.org
Content-Transfer-Encoding: 8BIT
Message-Id: <49999069-238D-4FBE-8F38-3762788A67C1@holtmann.org>
References: <CAEQQxWzdBy9JOC7+oQTBJ35Gov1CDk17fy+XH=jha8MuT9fy9Q@mail.gmail.com>
To:     Andrey Batyiev <batyiev@gmail.com>
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

Hi Andrey,

> I'm trying to pair my MIPS based router with a phone (using bluez),
> without success.
> I have turned on debugging features of bluetooth kernel module and I
> got this in dmesg:
> 
> [  234.481526] Bluetooth: Core ver 2.22
> [  234.485231] Bluetooth: Starting self testing
> [  234.525375] Bluetooth: ECDH sample 1 failed
> [  234.529728] Bluetooth: Finished self testing
> 
> Also, I checked hcidump, and it seems that SMP "Pairing confirm"
> command got rejected by the phone with an error ("Reason: Unspecified
> Reason (0x08)").
> As far as I understand, ECDH computation is involved in a pairing process.

I think that our ECDH code was endian safe, but then it got changed at some point to use standard crypto and maybe something went wrong there. Can just provide the btmon -w trace.log for the SMP pairing so that I can have a look at the binary trace.

Regards

Marcel