openstack-manuals/doc/common/tables/swift-swift-swift-hash.xml
Gauvain Pocentek b88212e062 config reference update for juno-1
Generate the config tables with the autohelp script and include the new
tables in the config ref sections.

For consistency, use the 'database' and 'auth_token' keywords in all
projects.

Split the LBaaS tables.

Closes-Bug: #1327802
Closes-Bug: #1331180
Closes-Bug: #1331175
Closes-Bug: #1330279
Closes-Bug: #1323946
Closes-Bug: #1323437
Closes-Bug: #1322075
Closes-Bug: #1321621
Closes-Bug: #1319564
Closes-Bug: #1318081
Closes-Bug: #1311474
Change-Id: I5602dda76fdf929d9124f5aa67d31ca4ac17c6d5
2014-06-29 20:55:34 +02:00

46 lines
1.9 KiB
XML

<?xml version='1.0' encoding='UTF-8'?>
<para xmlns="http://docbook.org/ns/docbook" version="5.0">
<!-- The tool that generated this table lives in the
openstack-doc-tools repository. The editions made in
this file will *not* be lost if you run the script again. -->
<table rules="all">
<caption>Description of configuration options for
<literal>[swift-hash]</literal> in <literal>swift.conf</literal>
</caption>
<col width="50%"/>
<col width="50%"/>
<thead>
<tr>
<th>Configuration option = Default value</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>swift_hash_path_prefix = changeme</td>
<td>
A prefix used by hash_path to offer a bit more security when generating hashes for
paths. It simply appends this value to all paths; if someone knows this suffix,
it's easier for them to guess the hash a path will end up with.
New installations are advised to set this parameter to a random secret,
which would not be disclosed ouside the organization.
The same secret needs to be used by all swift servers of the same cluster.
Existing installations should set this parameter to an empty string.</td>
</tr>
<tr>
<td>swift_hash_path_suffix = changeme</td>
<td>
A suffix used by hash_path to offer a bit more security when generating hashes for
paths. It simply appends this value to all paths; if someone knows this suffix,
it's easier for them to guess the hash a path will end up with.
New installations are advised to set this parameter to a random secret,
which would not be disclosed ouside the organization.
The same secret needs to be used by all swift servers of the same cluster.
Existing installations should set this parameter to an empty string.</td>
</tr>
</tbody>
</table>
</para>