From fb2ee7cc02ab2cd28848a1282689d1948c596501 Mon Sep 17 00:00:00 2001 From: Johannes Amorosa Date: Sat, 9 Apr 2016 00:31:01 +0200 Subject: [PATCH] Update s3fs.1 --- doc/man/s3fs.1 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/man/s3fs.1 b/doc/man/s3fs.1 index e0c9a6c..6c005ec 100644 --- a/doc/man/s3fs.1 +++ b/doc/man/s3fs.1 @@ -92,8 +92,8 @@ If you specify only "kmsid"("k"), you need to set AWSSSEKMSID environment which You must be careful about that you can not use the KMS id which is not same EC2 region. .TP \fB\-o\fR load_sse_c - specify SSE-C keys -Specify the custom-provided encription keys file path for decrypting at duwnloading. -If you use the custom-provided encription key at uploading, you specify with "use_sse=custom". +Specify the custom-provided encryption keys file path for decrypting at downloading. +If you use the custom-provided encryption key at uploading, you specify with "use_sse=custom". The file has many lines, one line means one custom key. So that you can keep all SSE-C keys in file, that is SSE-C key history. AWSSSECKEYS environment is as same as this file contents.