\label{doc_SECURITY_md_md_doc_SECURITY}%
\Hypertarget{doc_SECURITY_md_md_doc_SECURITY}%
 Security is a very important point in libraries. In most use cases there is nearly no point of danger in using Elektra. But some a very security related, especially when you use a daemon or some kind of distributed configuration.\hypertarget{doc_SECURITY_md_autotoc_md3740}{}\doxysection{Access Permissions}\label{doc_SECURITY_md_autotoc_md3740}
We only use access permissions from the kernel, we do not add an additional layer (or daemon). So configuration file access is as secure as with direct access to configuration files.\hypertarget{doc_SECURITY_md_autotoc_md3741}{}\doxysection{Namespaces}\label{doc_SECURITY_md_autotoc_md3741}
Elektra by default guarantees that configuration from specific namespaces come from respective paths in the file system\+:


\begin{DoxyItemize}
\item {\ttfamily dir}-\/namespace\+: from current working directory
\item {\ttfamily user}-\/namespace\+: from users home directory
\item {\ttfamily system} or {\ttfamily spec}-\/namespace\+: no restrictions
\end{DoxyItemize}\hypertarget{doc_SECURITY_md_autotoc_md3742}{}\doxysection{Environment Variables}\label{doc_SECURITY_md_autotoc_md3742}
Environment variables are usually avoided, but instead Elektra itself is used to configure Elektra. The core is not allowed to use any environment variables.

For some plugins, however, Environment variables are used for better integration in systems. This might be a security risk.\hypertarget{doc_SECURITY_md_autotoc_md3743}{}\doxysection{Compiler Options}\label{doc_SECURITY_md_autotoc_md3743}
Can be changed using standard CMake ways. Some hints\+:

\href{http://wiki.debian.org/Hardening}{\texttt{ http\+://wiki.\+debian.\+org/\+Hardening}}\hypertarget{doc_SECURITY_md_autotoc_md3744}{}\doxysection{Memory Leaks}\label{doc_SECURITY_md_autotoc_md3744}
We use Valgrind ({\ttfamily -\/-\/tool=memcheck}) and ASAN (clang+gcc) to make sure that Elektra does not suffer memory leaks and incorrect memory handling. 