DCONF(7) Conventions and miscellaneous DCONF(7)NAME
dconf - A configuration systen
DESCRIPTION
dconf is a simple key/value storage system that is heavily optimised for reading. This makes it an ideal system for storing user
preferences (which are read 1000s of times for each time the user changes one). It was created with this usecase in mind.
All preferences are stored in a single large binary file. Layering of preferences is possible using multiple files (ie: for site defaults).
Lock-down is also supported. The binary file for the defaults can optionally be compiled from a set of plain text keyfiles.
dconf has a partial client/server architecture. It uses D-Bus. The server is only involved in writes (and is not activated in the user
session until the user modifies a preference). The service is stateless and can exit freely at any time (and is therefore robust against
crashes). The list of paths that each process is watching is stored within the D-Bus daemon itself (as D-Bus signal match rules).
Reads are performed by direct access (via mmap) to the on-disk database which is essentially a hashtable. For this reason, dconf reads
typically involve zero system calls and are comparable to a hashtable lookup in terms of speed. Practically speaking, in simple non-layered
setups, dconf is less than 10 times slower than GHashTable.
Writes are assumed only to happen in response to explicit user interaction (like clicking on a checkbox in a preferences dialog) and are
therefore not optimised at all. On some file systems, dconf-service will call fsync() for every write, which can introduce a latency of up
to 100ms. This latency is hidden by the client libraries through a clever "fast" mechanism that records the outstanding changes locally (so
they can be read back immediately) until the service signals that a write has completed.
PORTABILITY
dconf mostly targets Free Software operating systems. It will theoretically run on Mac OS but there isn't much point to that (since Mac OS
applications want to store preferences in plist files). It is not possible to use dconf on Windows because of the inability to rename over
a file that's still in use (which is what the dconf-service does on every write).
API STABILITY
The dconf API is not particularly friendly, and is not guaranteed to be stable. Because of this and the lack of portability, you almost
certainly want to use some sort of wrapper API around it. The wrapper API used by GTK+ and GNOME applications is GSettings[1], which is
included as part of GLib. GSettings has backends for Windows (using the registry) and Mac OS (using property lists) as well as its dconf
backend and is the proper API to use for graphical applications.
SEE ALSO dconf-service(1), dconf-editor(1), dconf(1), GSettings[1]
NOTES
1. GSettings
http://developer.gnome.org/gio/stable/GSettings.html
dconfDCONF(7)
Check Out this Related Man Page
telepathy_logger_selinux(8) SELinux Policy telepathy_logger telepathy_logger_selinux(8)NAME
telepathy_logger_selinux - Security Enhanced Linux Policy for the telepathy_logger processes
DESCRIPTION
Security-Enhanced Linux secures the telepathy_logger processes via flexible mandatory access control.
The telepathy_logger processes execute with the telepathy_logger_t SELinux type. You can check if you have these processes running by exe-
cuting the ps command with the -Z qualifier.
For example:
ps -eZ | grep telepathy_logger_t
ENTRYPOINTS
The telepathy_logger_t SELinux type can be entered via the telepathy_logger_exec_t file type.
The default entrypoint paths for the telepathy_logger_t domain are the following:
/usr/libexec/telepathy-logger
PROCESS TYPES
SELinux defines process types (domains) for each process running on the system
You can see the context of a process using the -Z option to ps
Policy governs the access confined processes have to files. SELinux telepathy_logger policy is very flexible allowing users to setup their
telepathy_logger processes in as secure a method as possible.
The following process types are defined for telepathy_logger:
telepathy_logger_t
Note: semanage permissive -a telepathy_logger_t can be used to make the process type telepathy_logger_t permissive. SELinux does not deny
access to permissive process types, but the AVC (SELinux denials) messages are still generated.
BOOLEANS
SELinux policy is customizable based on least access required. telepathy_logger policy is extremely flexible and has several booleans that
allow you to manipulate the policy and run telepathy_logger with the tightest access possible.
If you want to allow users to resolve user passwd entries directly from ldap rather then using a sssd server, you must turn on the authlo-
gin_nsswitch_use_ldap boolean. Disabled by default.
setsebool -P authlogin_nsswitch_use_ldap 1
If you want to deny any process from ptracing or debugging any other processes, you must turn on the deny_ptrace boolean. Enabled by
default.
setsebool -P deny_ptrace 1
If you want to allow all domains to use other domains file descriptors, you must turn on the domain_fd_use boolean. Enabled by default.
setsebool -P domain_fd_use 1
If you want to allow all domains to have the kernel load modules, you must turn on the domain_kernel_load_modules boolean. Disabled by
default.
setsebool -P domain_kernel_load_modules 1
If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default.
setsebool -P fips_mode 1
If you want to enable reading of urandom for all domains, you must turn on the global_ssp boolean. Disabled by default.
setsebool -P global_ssp 1
If you want to allow confined applications to run with kerberos, you must turn on the kerberos_enabled boolean. Enabled by default.
setsebool -P kerberos_enabled 1
If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default.
setsebool -P nis_enabled 1
If you want to allow confined applications to use nscd shared memory, you must turn on the nscd_use_shm boolean. Enabled by default.
setsebool -P nscd_use_shm 1
If you want to support ecryptfs home directories, you must turn on the use_ecryptfs_home_dirs boolean. Disabled by default.
setsebool -P use_ecryptfs_home_dirs 1
If you want to support fusefs home directories, you must turn on the use_fusefs_home_dirs boolean. Disabled by default.
setsebool -P use_fusefs_home_dirs 1
If you want to support NFS home directories, you must turn on the use_nfs_home_dirs boolean. Disabled by default.
setsebool -P use_nfs_home_dirs 1
If you want to support SAMBA home directories, you must turn on the use_samba_home_dirs boolean. Disabled by default.
setsebool -P use_samba_home_dirs 1
NSSWITCH DOMAIN
If you want to allow users to resolve user passwd entries directly from ldap rather then using a sssd server for the telepathy_logger_t,
you must turn on the authlogin_nsswitch_use_ldap boolean.
setsebool -P authlogin_nsswitch_use_ldap 1
If you want to allow confined applications to run with kerberos for the telepathy_logger_t, you must turn on the kerberos_enabled boolean.
setsebool -P kerberos_enabled 1
MANAGED FILES
The SELinux process type telepathy_logger_t can manage files labeled with the following file types. The paths listed are the default paths
for these file types. Note the processes UID still need to have DAC permissions.
cache_home_t
/root/.cache(/.*)?
/home/[^/]*/.nv(/.*)?
/home/[^/]*/.cache(/.*)?
cifs_t
config_home_t
/root/.kde(/.*)?
/root/.xine(/.*)?
/root/.config(/.*)?
/var/run/user/[^/]*/dconf(/.*)?
/root/.Xdefaults
/home/[^/]*/.kde(/.*)?
/home/[^/]*/.xine(/.*)?
/home/[^/]*/.config(/.*)?
/home/[^/]*/.cache/dconf(/.*)?
/home/[^/]*/.Xdefaults
ecryptfs_t
/home/[^/]*/.Private(/.*)?
/home/[^/]*/.ecryptfs(/.*)?
fusefs_t
/var/run/[^/]*/gvfs
nfs_t
telepathy_logger_cache_home_t
/home/[^/]*/.cache/telepathy/logger(/.*)?
telepathy_logger_data_home_t
/home/[^/]*/.local/share/TpLogger(/.*)?
FILE CONTEXTS
SELinux requires files to have an extended attribute to define the file type.
You can see the context of a file using the -Z option to ls
Policy governs the access confined processes have to these files. SELinux telepathy_logger policy is very flexible allowing users to setup
their telepathy_logger processes in as secure a method as possible.
STANDARD FILE CONTEXT
SELinux defines the file context types for the telepathy_logger, if you wanted to store files with these types in a diffent paths, you need
to execute the semanage command to sepecify alternate labeling and then use restorecon to put the labels on disk.
semanage fcontext -a -t telepathy_logger_cache_home_t '/srv/telepathy_logger/content(/.*)?'
restorecon -R -v /srv/mytelepathy_logger_content
Note: SELinux often uses regular expressions to specify labels that match multiple files.
The following file types are defined for telepathy_logger:
telepathy_logger_cache_home_t
- Set files with the telepathy_logger_cache_home_t type, if you want to store telepathy logger cache files in the users home directory.
telepathy_logger_data_home_t
- Set files with the telepathy_logger_data_home_t type, if you want to store telepathy logger data files in the users home directory.
telepathy_logger_exec_t
- Set files with the telepathy_logger_exec_t type, if you want to transition an executable to the telepathy_logger_t domain.
telepathy_logger_tmp_t
- Set files with the telepathy_logger_tmp_t type, if you want to store telepathy logger temporary files in the /tmp directories.
Note: File context can be temporarily modified with the chcon command. If you want to permanently change the file context you need to use
the semanage fcontext command. This will modify the SELinux labeling database. You will need to use restorecon to apply the labels.
COMMANDS
semanage fcontext can also be used to manipulate default file context mappings.
semanage permissive can also be used to manipulate whether or not a process type is permissive.
semanage module can also be used to enable/disable/install/remove policy modules.
semanage boolean can also be used to manipulate the booleans
system-config-selinux is a GUI tool available to customize SELinux policy settings.
AUTHOR
This manual page was auto-generated using sepolicy manpage .
SEE ALSO selinux(8), telepathy_logger(8), semanage(8), restorecon(8), chcon(1), sepolicy(8) , setsebool(8)telepathy_logger 14-06-10 telepathy_logger_selinux(8)