From 0453e8a3c9a2ef59b5ab546e0f2aafd69df67e5f Mon Sep 17 00:00:00 2001
From: Jaime Perez <jaime.perez@uninett.no>
Date: Thu, 7 Aug 2014 20:08:41 +0200
Subject: [PATCH] aggregator2: clarify documentation about signing the
 aggregate.

---
 modules/aggregator2/docs/aggregator2.txt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/modules/aggregator2/docs/aggregator2.txt b/modules/aggregator2/docs/aggregator2.txt
index 75f29f9af..3e499cecc 100644
--- a/modules/aggregator2/docs/aggregator2.txt
+++ b/modules/aggregator2/docs/aggregator2.txt
@@ -55,7 +55,8 @@ The aggregator can be configured with the following options:
 
 `sign.privatekey`
 :   The private key that should be used to sign the metadata, in PEM format.
-    The path to the private key can be absolute, or it can be relative to the `cert`-directory.
+    The path to the private key can be absolute, or it can be relative to the `cert`-directory. Skip this option or
+    set it to NULL if you don't want to sign the generated metadata.
 
 `sign.privatekey_pass`
 :   The password for the private key.
-- 
GitLab