307e63aac7
No longer support setting the statistics_log path in WT_CONNECTION::reconfigure.
No longer support setting a custom name for statistics files, only allow a destination directory.
Be more explicit about which logging configuration options are allowed in WT_CONNECTION::reconfigure.
The aim of these changes is to avoid situations where applications that embed WiredTiger allow their users to overwrite unexpected files on a file system.
This potentially requires an upgrade step for applications that were specifying a non-standard file name component for statistics log file names, it's not backward compatible.
(cherry picked from commit 9cc5d0f4b1)
39 lines
1.6 KiB
Plaintext
39 lines
1.6 KiB
Plaintext
/*! @page security Security
|
|
|
|
@section directory_permissions Database directory permissions
|
|
|
|
By default, WiredTiger files are stored beneath the database home directory.
|
|
The WiredTiger database directory should have its permissions set to ensure
|
|
database objects are not accessible to users without appropriate permissions.
|
|
See @ref home for more information.
|
|
|
|
@section absolute_path Absolute paths
|
|
|
|
WiredTiger prepends the name of the database home to file names which
|
|
do not appear to be absolute paths. (The absolute path test is
|
|
simplistic, matching a leading slash character on POSIX systems or a
|
|
leading alphabetic character and colon on Windows.) No file path
|
|
sanitization or validation is done by WiredTiger, for example, file
|
|
paths may match universal naming conventions (UNC), or include \c "../"
|
|
(dot dot slash) components.
|
|
|
|
Applications are responsible for validating user-supplied file paths as
|
|
necessary to prevent directory traversal attacks.
|
|
|
|
@section file_permissions File permissions
|
|
|
|
WiredTiger creates file system objects readable and writable by the
|
|
process owner, group and user, as modified by the process' umask value.
|
|
The group ownership of created file system objects may vary depending
|
|
on the system, and is not controlled by WiredTiger.
|
|
|
|
@section environment_variables Environment variables
|
|
|
|
Consider security when configuring WiredTiger to use the WIREDTIGER_HOME
|
|
environment variable, especially in applications which run with
|
|
permissions other than the user's. Such applications are potentially
|
|
vulnerable to allowing users access to databases they could not
|
|
otherwise access. See @ref home for more information.
|
|
|
|
*/
|