Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <01070182f561c630-852e0333-6f04-448b-b064-46a2f000e860-000000@eu-central-1.amazonses.com>
Date:   Wed, 31 Aug 2022 19:30:01 +0000
MIME-Version: 1.0
To:     linux-bluetooth@vger.kernel.org
Content-Language: de-DE
From:   Florian Leeber <florian@ubports.com>
Subject: [PATCH] plugins: Do not try to autopair with Nissan Connect devices
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Feedback-ID: 1.eu-central-1.U71sxic/3tmi0U3T+Ze2hDyqoN46zyPgdCO+zEPT6YQ=:AmazonSES
Precedence: bulk

It seems that Nissan Connect carkits a) do not use 0000 but 1234 as 
default code
but also b) the autopair plugin is not allowed to make a second attempt 
to pair.
Let´s try to not use the autopairing at all for those devices.
---
  plugins/autopair.c | 3 +++
  1 file changed, 3 insertions(+)

diff --git a/plugins/autopair.c b/plugins/autopair.c
index 0b09e89..6bf07e3 100644
--- a/plugins/autopair.c
+++ b/plugins/autopair.c
@@ -66,6 +66,9 @@ static ssize_t autopair_pincb(struct btd_adapter *adapter,
         /* The iCade shouldn't use random PINs like normal keyboards */
         if (strstr(name, "iCade") != NULL)
                 return 0;
+       /* Nissan Connect carkits use PIN 1234 but refuse a retry */
+       if (strstr(name, "NISSAN CONNECT") != NULL)
+               return 0;

         /* This is a class-based pincode guesser. Ignore devices with an
          * unknown class.
--
2.17.1