linux-kernel - What is the successor of /dev/rfcomm0 after the rfcomm tool be deprecated

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20231128071611.GA5154@linux-l9pv.suse>
Date:   Tue, 28 Nov 2023 15:16:11 +0800
From:   joeyli <jlee@...e.com>
To:     linux-bluetooth@...r.kernel.org
Cc:     linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: What is the successor of /dev/rfcomm0 after the rfcomm tool be
 deprecated

Hi bluetooth experts, 

I am learning user space programming for bluetooth. I have tried
a simple python script as a socket client for access /dev/rfcomm0 success.
I created the /dev/rfcomm0 device by "rfcomm bind" command. It works fine.

But after the rfcomm tool be deprecated in bluez. I didn't see any
successor of /dev/rfcomm0 or rfcomm tool. I read this article:

http://www.bluez.org/the-management-interface/  

Does that mean all scripts/applications base on rfcomm tool and /dev/rfcomm0
need to be rewritten by using bluetoothd-dbus API? Do we have any solution
to keep those old socket scripts work as is? For example: Forwarding socket
request of /dev/rfcomm0 to bluetoothd?

Thanks a lot!
Joey Lee