anchao commented on code in PR #20686:
URL: https://github.com/apache/nuttx/pull/20686#discussion_r4389637228
##########
libs/zblue/CMakeLists.txt:
##########
@@ -0,0 +1,40 @@
+#
##############################################################################
+# libs/zblue/CMakeLists.txt
Review Comment:
@acassis @casaroli @xiaoxiang781216
One more point about userspace Bluetooth stacks: Android's move from BlueZ
to
Bluedroid was not simply because "userspace is safer". A major reason was
also
the licensing/runtime model around BlueZ (GPLv2 userspace components, D-Bus,
glibc/Linux userspace assumptions), which was not a good fit for Android's
platform goals.
So I do not think "Bluetooth in userspace" should automatically be treated
as
the only safe architecture. Security issues can be fixed by hardening,
reviewing, fuzzing, and testing the stack. That requires continuous effort
from
the community, but I do not think we should reject the architecture from the
beginning only because Bluetooth has a large attack surface.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
