From: keescook@chromium.org (Kees Cook)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 15/17] doc: ReSTify keys-ecryptfs.txt
Date: Sat, 13 May 2017 04:51:51 -0700 [thread overview]
Message-ID: <1494676313-144890-16-git-send-email-keescook@chromium.org> (raw)
In-Reply-To: <1494676313-144890-1-git-send-email-keescook@chromium.org>
Adjusts for ReST markup and moves under keys security devel index.
Cc: David Howells <dhowells@redhat.com>
Cc: Tyler Hicks <tyhicks@canonical.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
---
Documentation/security/00-INDEX | 2 --
.../security/{keys-ecryptfs.txt => keys/ecryptfs.rst} | 19 ++++++++++++-------
Documentation/security/keys/index.rst | 1 +
3 files changed, 13 insertions(+), 9 deletions(-)
rename Documentation/security/{keys-ecryptfs.txt => keys/ecryptfs.rst} (91%)
diff --git a/Documentation/security/00-INDEX b/Documentation/security/00-INDEX
index a840095bb11c..08a6e7a195ef 100644
--- a/Documentation/security/00-INDEX
+++ b/Documentation/security/00-INDEX
@@ -1,7 +1,5 @@
00-INDEX
- this file.
-keys-ecryptfs.txt
- - description of the encryption keys for the ecryptfs filesystem.
keys-request-key.txt
- description of the kernel key request service.
keys-trusted-encrypted.txt
diff --git a/Documentation/security/keys-ecryptfs.txt b/Documentation/security/keys/ecryptfs.rst
similarity index 91%
rename from Documentation/security/keys-ecryptfs.txt
rename to Documentation/security/keys/ecryptfs.rst
index c3bbeba63562..4920f3a8ea75 100644
--- a/Documentation/security/keys-ecryptfs.txt
+++ b/Documentation/security/keys/ecryptfs.rst
@@ -1,4 +1,6 @@
- Encrypted keys for the eCryptfs filesystem
+==========================================
+Encrypted keys for the eCryptfs filesystem
+==========================================
ECryptfs is a stacked filesystem which transparently encrypts and decrypts each
file using a randomly generated File Encryption Key (FEK).
@@ -35,20 +37,23 @@ controlled environment. Another advantage is that the key is not exposed to
threats of malicious software, because it is available in clear form only at
kernel level.
-Usage:
+Usage::
+
keyctl add encrypted name "new ecryptfs key-type:master-key-name keylen" ring
keyctl add encrypted name "load hex_blob" ring
keyctl update keyid "update key-type:master-key-name"
-name:= '<16 hexadecimal characters>'
-key-type:= 'trusted' | 'user'
-keylen:= 64
+Where::
+
+ name:= '<16 hexadecimal characters>'
+ key-type:= 'trusted' | 'user'
+ keylen:= 64
Example of encrypted key usage with the eCryptfs filesystem:
Create an encrypted key "1000100010001000" of length 64 bytes with format
-'ecryptfs' and save it using a previously loaded user key "test":
+'ecryptfs' and save it using a previously loaded user key "test"::
$ keyctl add encrypted 1000100010001000 "new ecryptfs user:test 64" @u
19184530
@@ -62,7 +67,7 @@ Create an encrypted key "1000100010001000" of length 64 bytes with format
$ keyctl pipe 19184530 > ecryptfs.blob
Mount an eCryptfs filesystem using the created encrypted key "1000100010001000"
-into the '/secret' directory:
+into the '/secret' directory::
$ mount -i -t ecryptfs -oecryptfs_sig=1000100010001000,\
ecryptfs_cipher=aes,ecryptfs_key_bytes=32 /secret /secret
diff --git a/Documentation/security/keys/index.rst b/Documentation/security/keys/index.rst
index ddfe7e4726e6..d34f663354bb 100644
--- a/Documentation/security/keys/index.rst
+++ b/Documentation/security/keys/index.rst
@@ -6,3 +6,4 @@ Kernel Keys
:maxdepth: 1
core
+ ecryptfs
--
2.7.4
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-05-13 11:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 11:51 [PATCH 00/17] convert/reorganize Documentation/security/ Kees Cook
2017-05-13 11:51 ` [PATCH 01/17] doc: ReSTify seccomp_filter.txt Kees Cook
2017-05-13 11:51 ` [PATCH 02/17] doc: ReSTify no_new_privs.txt Kees Cook
2017-05-13 11:51 ` [PATCH 03/17] doc: ReSTify IMA-templates.txt Kees Cook
2017-05-13 11:51 ` [PATCH 04/17] doc: ReSTify credentials.txt Kees Cook
2017-05-13 11:51 ` [PATCH 05/17] doc: ReSTify self-protection.txt Kees Cook
2017-05-13 11:51 ` [PATCH 06/17] doc: security: minor cleanups to build kernel-doc Kees Cook
2017-05-14 23:17 ` James Morris
2017-05-15 17:21 ` Jonathan Corbet
2017-05-15 0:00 ` Casey Schaufler
2017-05-15 14:42 ` Kees Cook
2017-05-13 11:51 ` [PATCH 07/17] doc: ReSTify and split LSM.txt Kees Cook
2017-05-13 11:51 ` [PATCH 08/17] doc: ReSTify SELinux.txt Kees Cook
2017-05-17 20:08 ` Paul Moore
2017-05-13 11:51 ` [PATCH 09/17] doc: ReSTify apparmor.txt Kees Cook
2017-05-13 19:47 ` John Johansen
2017-05-13 11:51 ` [PATCH 10/17] doc: ReSTify tomoyo.txt Kees Cook
2017-05-14 6:51 ` Tetsuo Handa
2017-05-13 11:51 ` [PATCH 11/17] doc: ReSTify Yama.txt Kees Cook
2017-05-13 11:51 ` [PATCH 12/17] doc: ReSTify LoadPin.txt Kees Cook
2017-05-13 11:51 ` [PATCH 13/17] doc: ReSTify Smack.txt Kees Cook
2017-05-15 14:13 ` Casey Schaufler
2017-05-13 11:51 ` [PATCH 14/17] doc: ReSTify keys.txt Kees Cook
2017-05-13 11:51 ` Kees Cook [this message]
2017-05-13 11:51 ` [PATCH 16/17] doc: ReSTify keys-request-key.txt Kees Cook
2017-05-13 11:51 ` [PATCH 17/17] doc: ReSTify keys-trusted-encrypted.txt Kees Cook
2017-05-15 17:26 ` [PATCH 00/17] convert/reorganize Documentation/security/ Jonathan Corbet
2017-05-15 17:33 ` Kees Cook
2017-05-18 16:49 ` Jonathan Corbet
2017-05-18 17:01 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1494676313-144890-16-git-send-email-keescook@chromium.org \
--to=keescook@chromium.org \
--cc=linux-security-module@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).