From owner-freebsd-bluetooth@FreeBSD.ORG Sun Mar 22 20:52:57 2015 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 80EBA91B for ; Sun, 22 Mar 2015 20:52:57 +0000 (UTC) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 051A039D for ; Sun, 22 Mar 2015 20:52:57 +0000 (UTC) Received: by wibg7 with SMTP id g7so23732688wib.1 for ; Sun, 22 Mar 2015 13:52:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bO6+DqfzmRGRk4Vy7ZeAhi7WC5FEDFDeVJSHt2jcrEc=; b=QDAnTYCZyHxErjPfa3OOgrSgFZQ4TjWI/tmx2AsVWZ+i+8vkIpfkfvxcmNx7ltPzTi 11gFgH9FDG5f21+vFibYCKCt7OZ/NB5jTPF1j1P2Bk/pnveT/UYb7pvxjGiTgJvXeF/O BaZGRtD0Fboq5T9yeq4eNe0BZaVyaqkMybycizvByl3bbb0yCapvCoJE58O7TasWnXLc l/Jm3fmYCzEI9f9Rv+7w3PFAKYC9/iwIw7k4zPC67W5GopWe96TVU4JpqXp2R8t+iYGH wHtSkJo8DYAVXOZ10SIzxvhu+2mNMnxhdBTsVjRBBgPP4xoKSRWputySSF543/+1KEtm CAcQ== MIME-Version: 1.0 X-Received: by 10.180.77.40 with SMTP id p8mr13698024wiw.1.1427057574977; Sun, 22 Mar 2015 13:52:54 -0700 (PDT) Received: by 10.27.91.75 with HTTP; Sun, 22 Mar 2015 13:52:54 -0700 (PDT) In-Reply-To: References: <77352B43-637C-4E0D-B4CC-B42D977551F6@gmail.com> Date: Sun, 22 Mar 2015 13:52:54 -0700 Message-ID: Subject: Re: register HID with SDP error From: Waitman Gobble To: Iain Hibbert Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-bluetooth@freebsd.org" X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Mar 2015 20:52:57 -0000 On Sun, Mar 22, 2015 at 1:10 PM, Iain Hibbert wrote: > On Sat, 21 Mar 2015, Waitman Gobble wrote: > >> > char newpin[16]; > >> correction, should be newpin[32], or maybe more.. MS windows asks for >> a longer pincode. > > Are you sure about that? All the specifications I have seen, say that the > PIN code can be a maximum of 128 bits. (see 7.1.12 Pin Code Request Reply > Command in the Bluetooth v4.0 Core specification) > > iain I was getting garbage in the pincode with char[16] 32 is larger than needed. But also need to add the 'enter key' or the client will sit there waiting. < HCI Command: PIN Code Request Reply(0x01|0x000d) plen 23 L . . . . . . 3 2 1 6 7 6 4 2 . . . . . -- Waitman Gobble Los Altos California USA 510-830-7975