From 40f0a8ee72dd3091480d73f8e76979545a3668ea Mon Sep 17 00:00:00 2001
From: danim7
Date: Sat, 25 Mar 2017 18:22:08 +0100
Subject: Further explain the use of 'scryptn' parameter (#94)

* Further explain the use of 'scryptn' parameter

* Further explain the use of 'scryptn' parameter in MANPAGE

* Use 28 as reasonable upper limit
---
 Documentation/MANPAGE.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'Documentation')

diff --git a/Documentation/MANPAGE.md b/Documentation/MANPAGE.md
index 7387424..fe2d73f 100644
--- a/Documentation/MANPAGE.md
+++ b/Documentation/MANPAGE.md
@@ -200,9 +200,9 @@ Options:
 	For more details visit https://github.com/rfjakob/gocryptfs/issues/92 .
 
 **-scryptn int**
-:	scrypt cost parameter logN. Setting this to a lower value speeds up
-	mounting but makes the password susceptible to brute-force attacks
-	(default 16)
+:	scrypt cost parameter logN. Possible values: 10-28. Setting this to a lower
+        value speeds up	mounting and reduces its memory needs, but makes
+	the password susceptible to brute-force attacks	(default 16).
 
 **-speed**
 :	Run crypto speed test. Benchmark Go's built-in GCM against OpenSSL
-- 
cgit v1.2.3