summaryrefslogtreecommitdiff
path: root/src/libsystemd-bus
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2013-12-27 01:20:21 +0100
committerLennart Poettering <lennart@poettering.net>2013-12-27 01:20:21 +0100
commit3e8ba0b815ebe83e396eb911fa9302e6ddb0ac07 (patch)
tree663d4c1262d7dfee9179b9cc5901695a8f3bb6c3 /src/libsystemd-bus
parent9129246ba5ae990025347b3d5ab7d5178d968ee1 (diff)
bus: actually, the kernel does enforce validity of bus names...
Diffstat (limited to 'src/libsystemd-bus')
-rw-r--r--src/libsystemd-bus/PORTING-DBUS15
1 files changed, 0 insertions, 5 deletions
diff --git a/src/libsystemd-bus/PORTING-DBUS1 b/src/libsystemd-bus/PORTING-DBUS1
index 9300137236..f2cf277483 100644
--- a/src/libsystemd-bus/PORTING-DBUS1
+++ b/src/libsystemd-bus/PORTING-DBUS1
@@ -459,11 +459,6 @@ name. The ioctl will return an offset into the memory pool. After
reading all the data you need you need to release this via the
KDBUS_CMD_FREE ioctl(), similar how you release a received message.
-Note that the kernel does not know anything about properly formatted
-dbus bus names. It is hence essential that you verify the validity of
-all bus names returned by the kernel (for example in message meta data
-or when listing acquired names), and ignore invalid entries.
-
CREDENTIALS
kdbus can optionally attach all kinds of metadata about the sender at