From owner-freebsd-bluetooth@FreeBSD.ORG Sun Mar 22 20:10:38 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 59BC2BC0 for ; Sun, 22 Mar 2015 20:10:38 +0000 (UTC) Received: from relay6-d.mail.gandi.net (relay6-d.mail.gandi.net [IPv6:2001:4b98:c:538::198]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 09F51E42 for ; Sun, 22 Mar 2015 20:10:38 +0000 (UTC) Received: from mfilter33-d.gandi.net (mfilter33-d.gandi.net [217.70.178.164]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id D0102FB877; Sun, 22 Mar 2015 21:10:35 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mfilter33-d.gandi.net Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by mfilter33-d.gandi.net (mfilter33-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id hOWG2QwIUZQt; Sun, 22 Mar 2015 21:10:34 +0100 (CET) X-Originating-IP: 31.68.68.12 Received: from galant.ogmig.net (unknown [31.68.68.12]) (Authenticated sender: plunky@ogmig.net) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 46138FB87D; Sun, 22 Mar 2015 21:10:33 +0100 (CET) Received: by galant.ogmig.net (Postfix, from userid 1000) id B86692600C6; Sun, 22 Mar 2015 20:10:28 +0000 (GMT) Date: Sun, 22 Mar 2015 20:10:28 +0000 (GMT) From: Iain Hibbert To: Waitman Gobble Subject: Re: register HID with SDP error In-Reply-To: Message-ID: References: <77352B43-637C-4E0D-B4CC-B42D977551F6@gmail.com> User-Agent: Alpine 2.11 (NEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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:10:38 -0000 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