From: Eric Lan <tenoreamer@gmail.com>
To: ecryptfs@vger.kernel.org
Subject: 32-byte encryption key for ecryptfs-setup-private ?
Date: Sun, 21 Dec 2014 16:57:21 +0000 (UTC) [thread overview]
Message-ID: <loom.20141221T175441-142@post.gmane.org> (raw)
The default key-bytes for ecryptfs-setup-private is 16 bytes. I tried to
change "KEYBYTES" in ecryptfs-setup-private to "32" but failed when running
the script.
How about offering options for the users to determine "encryption
parameters" (like encryption algorithm, encryption key bytes, etc.) ? Or is
there a workaround now ?
next reply other threads:[~2014-12-21 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 16:57 Eric Lan [this message]
2015-01-06 3:05 ` 32-byte encryption key for ecryptfs-setup-private ? Christian Kujau
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=loom.20141221T175441-142@post.gmane.org \
--to=tenoreamer@gmail.com \
--cc=ecryptfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.