diff -r 3070d72f54af -r 0e36bb75a732 docs/html/encryption.html
--- a/docs/html/encryption.html	Sat Aug 05 13:35:27 2017 +0200
+++ b/docs/html/encryption.html	Sun Aug 06 14:41:20 2017 +0200
@@ -4,7 +4,7 @@
   <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   <meta http-equiv="Content-Style-Type" content="text/css" />
   <meta name="generator" content="pandoc" />
-  <title></title>
+  <title>Encryption</title>
   <style type="text/css">code{white-space: pre;}</style>
   <link rel="stylesheet" href="davdoc.css" type="text/css" />
 </head>
@@ -64,7 +64,9 @@
 
 <!-- begin content -->
 <div class="content">
-<h1 id="encryption">Encryption</h1>
+<div id="header">
+<h1 class="title">Encryption</h1>
+</div>
 <p>The davutils programs have an integrated client-side encryption feature, that allows you to encrypt and decrypt on the fly with AES256 or AES128. To use this feature, the server <strong>must</strong> support WebDAV dead properties.</p>
 <p>The tools support both, encryption of the resource content and encryption of the resource name. Each resource is encrypted separately. With activated name encryption, the actual resource name is disguised by a random name but the name used by the client is stored encrypted as a WebDAV property. This means, an attacker can see the directory structure and the file length, but can't guess the file names and in particular which files have the same name.</p>
 <p>To enable encryption a key must be configured in <code>$HOME/.dav/config.xml</code>. A key must have a unique name. To access encrypted resources, all clients must configure the same key with the same name. Currently a key can only be loaded from a file and not generated from a password.</p>