*
* Doxygen documentation root for Veil
*
- * Copyright (c) 2005 - 2011 Marc Munro
+ * Copyright (c) 2005 - 2014 Marc Munro
* Author: Marc Munro
* License: BSD
*
/*! \mainpage Veil
-\version 9.1.0 (Stable))
+\version 9.2.0 (Stable))
\section license License
BSD
\section intro_sec Introduction
discover whether specific names appear in the database.
This is not something that Veil is intended to, or is able to, prevent.
-Changes to the underlying query engine to attempt to plug such holes
-have been proposed, but they all have their limitations and are likely
-to lead to degraded performance.
A more serious problem occurs if a user is able to create user defined
functions as these can easily provide covert channels for leaking data.
- \subpage Performance
- \subpage Credits
+\subsection BetterNews Better News
+
+In the latest versions of PostgreSQL, some have been made in the area of
+security, particularly with respect to security functions and ensuring
+that untrusted functions may not leak data that should be hidden.
+
+Note that there are likely to be costs associated with some of these
+improvements, as the query engine will apply untrusted functions later
+in the query execution plan. If those untrusted functions are used to
+significantly reduce the size of a dataset, moving their execution to
+later in the plan may have an adverse effect on performance. For this
+reason, you should test and benchmark and decide for yourself whether
+there is a performance hit, and whether the value of improved security
+is worth any measured loss of performance.
+
+You are also advised to follow the progress of Row Level Security
+support in later versions of Postgres, as this may obviate your need for
+Veil.
+
Next: \ref overview-page
*/
\code
shared_preload_libraries = '<path to shared library>/veil.so'
-custom_variable_classes = 'veil'
-
#veil.dbs_in_cluster = 1
#veil.shared_hash_elems = 32
#veil.shmem_context_size = 16384
*/
/*! \page History History and Compatibility
\section past Changes History
+\subsection v9_2 Version 9.2.0 (Stable) (2014-06-25)
+This version supports PostgreSQL V9.2.
+
+Only documentation changes have been made. This means that both this
+and the previous version support both postgres 9.1 and 9.2.
+
\subsection v1_0 Version 9.1.0 (Stable) (2011-07-22)
This is the first version of Veil to be considered production ready and
completely stable. It is for use only with PostgreSQL 9.1. Support for
<TABLE>
<TR>
<TD rowspan=2>Veil version</TD>
- <TD colspan=9>Postgres Version</TD>
+ <TD colspan=10>Postgres Version</TD>
</TR>
<TR>
<TD>7.4</TD>
<TD>8.4</TD>
<TD>9.0</TD>
<TD>9.1</TD>
+ <TD>9.2</TD>
</TR>
<TR>
<TD>0.9.0 Alpha</TD>
<TD>-</TD>
<TD>-</TD>
<TD>-</TD>
+ <TD>-</TD>
</TR>
<TR>
<TD>0.9.1 Alpha</TD>
<TD>-</TD>
<TD>-</TD>
<TD>-</TD>
+ <TD>-</TD>
</TR>
<TR>
<TD>0.9.2 Alpha</TD>
<TD>-</TD>
<TD>-</TD>
<TD>-</TD>
+ <TD>-</TD>
</TR>
<TR>
<TD>0.9.3 Alpha</TD>
<TD>-</TD>
<TD>-</TD>
<TD>-</TD>
+ <TD>-</TD>
</TR>
<TR>
<TD>0.9.4 Alpha</TD>
<TD>-</TD>
<TD>-</TD>
<TD>-</TD>
+ <TD>-</TD>
</TR>
<TR>
<TD>0.9.5 Alpha</TD>
<TD>-</TD>
<TD>-</TD>
<TD>-</TD>
+ <TD>-</TD>
</TR>
<TR>
<TD>0.9.6 Alpha</TD>
<TD>-</TD>
<TD>-</TD>
<TD>-</TD>
+ <TD>-</TD>
</TR>
<TR>
<TD>0.9.8 Beta</TD>
<TD>-</TD>
<TD>-</TD>
<TD>-</TD>
+ <TD>-</TD>
</TR>
<TR>
<TD>0.9.9 Beta</TD>
<TD>3</TD>
<TD>-</TD>
<TD>-</TD>
+ <TD>-</TD>
</TR>
<TR>
<TD>0.9.11 Beta</TD>
<TD>3</TD>
<TD>-</TD>
<TD>-</TD>
+ <TD>-</TD>
</TR>
<TR>
<TD>0.9.12 Beta</TD>
<TD>3</TD>
<TD>3</TD>
<TD>-</TD>
+ <TD>-</TD>
</TR>
<TR>
<TD>9.1.0 (Stable)</TD>
<TD>-</TD>
<TD>-</TD>
<TD>Yes</TD>
+ <TD>Yes</TD>
+ </TR>
+ <TR>
+ <TD>9.2.0 (Stable)</TD>
+ <TD>-</TD>
+ <TD>-</TD>
+ <TD>-</TD>
+ <TD>-</TD>
+ <TD>-</TD>
+ <TD>-</TD>
+ <TD>-</TD>
+ <TD>-</TD>
+ <TD>Yes</TD>
+ <TD>Yes</TD>
</TR>
</TABLE>
Notes:
the backend, eg:
\verbatim
-$ gdb /usr/lib/postgresql/9.1/bin/postgres 5444
+$ gdb /usr/lib/postgresql/9.2/bin/postgres 5444
\endverbatim
Hit c and Enter to get gdb to allow the session to continue. Now,