diff options
author | Daniel Mack <daniel@zonque.org> | 2014-09-11 19:00:43 +0200 |
---|---|---|
committer | Maciej Wereski <m.wereski@partner.samsung.com> | 2015-04-02 17:24:18 +0200 |
commit | ff934c33a97e27e94b5d84b0254a822f267383c6 (patch) | |
tree | 855ba03846fe3c3ef44587b5f6010b64a12dc538 /scripts/asn1_compiler.c | |
parent | 288cef990e0b6e60ebbbafb9ff4ac846138e206e (diff) | |
download | linux-3.10-ff934c33a97e27e94b5d84b0254a822f267383c6.tar.gz linux-3.10-ff934c33a97e27e94b5d84b0254a822f267383c6.tar.bz2 linux-3.10-ff934c33a97e27e94b5d84b0254a822f267383c6.zip |
kdbus: add policy database implementation
This patch adds the policy database implementation.
A policy database restricts the possibilities of connections to own,
see and talk to well-known names. It can be associated with a bus
(through a policy holder connection) or a custom endpoint.
By default, buses have an empty policy database that is augmented on
demand when a policy holder connection is instantiated.
Policies are set through KDBUS_CMD_HELLO (when creating a policy
holder connection), KDBUS_CMD_CONN_UPDATE (when updating a policy
holder connection), KDBUS_CMD_EP_MAKE (creating a custom endpoint)
or KDBUS_CMD_EP_UPDATE (updating a custom endpoint). In all cases,
the name and policy access information is stored in items of type
KDBUS_ITEM_NAME and KDBUS_ITEM_POLICY_ACCESS.
See kdbus.policy(7) for more details.
Signed-off-by: Daniel Mack <daniel@zonque.org>
Signed-off-by: David Herrmann <dh.herrmann@gmail.com>
Signed-off-by: Djalal Harouni <tixxdz@opendz.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts/asn1_compiler.c')
0 files changed, 0 insertions, 0 deletions