[PATCH BlueZ v5 0/5] Add possibility to use remote device keys

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



+Fix build/checkpatch errors
+Remove unused APP_IDX_NET and APP_IDX_ANY
+Fix handling of incoming packets marked with APP_IDX_DEV_REMOTE
+Fix usage of l_dbus_message_new_method_return
+Fix usage of l_dbus_message_builder APIs


This patchset adds support for sending and receiving messages encrypted
with remote device keys.

This plugs a 'loophole' in the API where it was possible to exchange
such messages using Send()/MessageReceived() API by using 0x7fff app key
index.

In order to allow the application to receive responses from a local
Config Server model, messages originating from a local node and
encrypted using local device key are also forwarded to the application
via D-Bus (assuming they were not handled by one of internal models).

Michał Lowas-Rzechonek (5):
  mesh: Cleanup l_dbus_message_... API usage in models
  mesh: Cleanup D-Bus method returns with empty result
  mesh: Split APP_IDX_DEV into APP_IDX_DEV_LOCAL and APP_IDX_DEV_REMOTE
  mesh: Implement DevKeySend() method on Node interface
  mesh: Handle messages encrypted with a remote device key

 mesh/cfgmod-server.c |  15 +++---
 mesh/model.c         | 124 ++++++++++++++++++++++++++++++-------------
 mesh/net.h           |   8 +--
 mesh/node.c          |  71 +++++++++++++++++++------
 4 files changed, 154 insertions(+), 64 deletions(-)

-- 
2.19.1




[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux