From nobody Sat Jan 25 01:40:25 2025 X-Original-To: bluetooth@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Yfy6x0mclz5lkJC for ; Sat, 25 Jan 2025 01:40:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Yfy6x0C2Dz3Z2M for ; Sat, 25 Jan 2025 01:40:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1737769225; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xJJ9g/LVlG3JwBOjFGeaqJeehZ3o5LLMuDh5zY2Xv20=; b=kGmYxCIuZ9lKzCowv4QyTKszIsZukrgwUS5N0srLh49YNgeFTSRfrcCiWY3sth0MOs8ed9 eU3/Y6GwY/iPS3vtxXQXnLFHwciptsku7VFHugL6+4F2ObKjShr7j154srCqtwsvNzognY tbdhjI9ItYiQD5SJ3brYIu3wOERy/eLoFCQwhSlMc4y7qwrQ7i2pfM0igm3pR+n4mdug58 23yzC+rq0atxVY4P/oM1nsFYahlJJkajB/9xvOojbFCpL50z3c9xRCYs9aqL4GuNF9bmUw n39PzfSgO+eFEnAsyYzcc7qTs0bVIkURBmV4fgCMcQFakTV8AoWVbJpQvXnNFg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1737769225; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xJJ9g/LVlG3JwBOjFGeaqJeehZ3o5LLMuDh5zY2Xv20=; b=kgl+kErqnd+vhYLJPM5+PwUSwFA25LWvwxvig7mW7CE7KKzF7JIwg8sq+4+rRbzQcVDp4M HToAErh4UUatDJwid82WjXn7ODz6U+NRcxRoGSvA5k2yaANP8959y5GXAjOH6c0S3gck5P so4Jxs4VPa+0FJ6rFuasjy7WrApXpRdDNqBlC/01/nW/p3jkvbah4lh4390KMJsAiv8qOD 0lYL2r7SFnpBu1MnLvxU5QVM1WtuX2DPtwUswcpdeihZ0JJ83laJwBIeYevRsaztxoPdFx +i7YxbppnTePDVof/UQV40Sj2LY3oeU8noNe5Mp852DfbsADOrEtpZx238v6kg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1737769225; a=rsa-sha256; cv=none; b=AyVXdq/YlS50TFo+RNRxi1MjTgfH/wxJ458KKJVLUyfqsNHLnAycUQ+bapkRmpkhHGqt6D qMgvGe/OC6WBrRWGXoWkQF4sG98Sa/c56qMbDJ5cX/LmFeDu1K1WtMWVRoFriIja3W/Adg BH2MftKTgEn4tP9usuk5fai38Qs3xxJbg+uOru8jyBDvGz4B1BwpTejHcn7NsHCZFyZAfR 7SFxTbE+cGjqaXXEOU4QiXLAruXdiwVm35SEYMFqlr0r5du5nOePiKHXEiIVY6HbkHg/K2 Z7Lu0PSxsQV6dlZLn73fs7bt3nq7Bt9XCYJ+I9iy+SI4cGBWTvATyO+DzpnMiQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4Yfy6w6vRczr8g for ; Sat, 25 Jan 2025 01:40:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 50P1eOZk037033 for ; Sat, 25 Jan 2025 01:40:24 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 50P1eOLE037032 for bluetooth@FreeBSD.org; Sat, 25 Jan 2025 01:40:24 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bluetooth@FreeBSD.org Subject: [Bug 265066] ng_hci: Add support for Bluetooth secure simple pairing Date: Sat, 25 Jan 2025 01:40:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: feature, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kempe@lysator.liu.se X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bz@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Using Bluetooth in FreeBSD environments List-Archive: https://lists.freebsd.org/archives/freebsd-bluetooth List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bluetooth@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D265066 --- Comment #10 from Andreas Kempe --- Created attachment 256976 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D256976&action= =3Dedit Updated patch with extre messages and name change. (In reply to Bjoern A. Zeeb from comment #9) Thank you for looking at this! I checked and actually have an updated versi= on of the patch where I added a few more messages that I noticed I had missed while working on blued. I am uploading the newest version of the patch I ha= ve with your suggested name change. It is good to hear some work might get done. I have been meaning to share s= ome of my thoughts but never got around to it, because I lost all my steam when= I realised the task was too big for me to have time to undertake alone. I think the Bluetooth infrastructure needs a good looking over. The current split between kernel and user space makes some things difficult. HCI connections being handled in user space gave me difficulties with correctly handling the interplay between l2cap connections that have proper socket support, the HCI connection and authentication. Unfortunately, I can't reme= mber the details and would have to dive back into the core specification to refr= esh my memory. Another issue with how HCI connections are handled is that a crash of the daemon loses track of what connections were active if state is not saved in persistent memory. If you lose the handle, there is no easy way to cause the connection to disconnect from software without resetting the host controlle= r or the Bluetooth device. I think it would probably be desirable to either put the entire implementat= ion in the kernel or user space, not splitting it like it is now. Maybe even looking at doing for Bluetooth what is currently being done for WiFi by importing driver infrastructure from Linux. --=20 You are receiving this mail because: You are on the CC list for the bug.=