From: Lennart Poettering Date: Fri, 27 Dec 2013 00:20:21 +0000 (+0100) Subject: bus: actually, the kernel does enforce validity of bus names... X-Git-Tag: v209~621 X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=commitdiff_plain;h=3e8ba0b815ebe83e396eb911fa9302e6ddb0ac07;hp=9129246ba5ae990025347b3d5ab7d5178d968ee1 bus: actually, the kernel does enforce validity of bus names... --- diff --git a/src/libsystemd-bus/PORTING-DBUS1 b/src/libsystemd-bus/PORTING-DBUS1 index 930013723..f2cf27748 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