Hi On Sun, Nov 30, 2014 at 9:56 AM, Florian Weimer <[email protected]> wrote: > * Greg Kroah-Hartman: > >> +The focus of this document is an overview of the low-level, native kernel >> D-Bus >> +transport called kdbus. Kdbus exposes its functionality via files in a >> +filesystem called 'kdbusfs'. All communication between processes takes place >> +via ioctls on files exposed through the mount point of a kdbusfs. The >> default >> +mount point of kdbusfs is /sys/fs/kdbus. > > Does this mean the bus does not enforce the correctness of the D-Bus > introspection metadata? That's really unfortunate. Classic D-Bus > does not do this, either, and combined with the variety of approaches > used to implement D-Bus endpoints, it makes it really difficult to > figure out what D-Bus services, exactly, a process provides.
kdbus operates on the transport-level only. We never touch or look at transferred data. As such, DBus introspection data as defined by org.freedesktop.DBus.Introspectable is not verified by the transport layer. Thanks David -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
