From: Tyler Hicks <tyhicks@canonical.com>
To: Wiebe Cazemier <wiebe@halfgaar.net>
Cc: ecryptfs@vger.kernel.org
Subject: Re: Key derivation and passprhase wrapping
Date: Fri, 29 Jan 2016 16:57:11 -0600 [thread overview]
Message-ID: <20160129225710.GD15683@boyd> (raw)
In-Reply-To: <497366096.234710.1453320193682.JavaMail.zimbra@halfgaar.net>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
On 2016-01-20 21:03:13, Wiebe Cazemier wrote:
> ----- Original Message -----
> > From: "Wiebe Cazemier" <wiebe@halfgaar.net>
> > To: "Tyler Hicks" <tyhicks@canonical.com>
> > Cc: ecryptfs@vger.kernel.org
> > Sent: Wednesday, 20 January, 2016 8:51:43 PM
> > Subject: Re: Key derivation and passprhase wrapping
> >
> > I think I missed an important bit. I was looking at ecryptfs-wrap-passphrase,
> > which makes you supply the FEK and FEKEK, but ecryptfs-setup-private
> > actually already uses a random passphrase:
> >
> > -m, --mountpass MOUNTPASS
> > Passphrase for mounting the ecryptfs directory, default is 16 bytes from
> > /dev/urandom if omitted
> >
>
> I do see an issue though. The bash script says:
>
> random_data=`head -c 16000 /dev/urandom | od -x` || error_testing "$temp" "$(gettext 'Could not generate random data')"
>
> But when urandom can't be read (doesn't exist, no file handles, whatever):
>
> random_data=`head -c 16000 /dev/urando | od -x` || echo "fail"
> head: cannot open ‘/dev/urando’ for reading: No such file or directory
>
> Note, no 'fail' and $? == 0. And:
>
> echo $random_data
> 0000000
For completeness, we should mention that this is being tracked in
Launchpad:
https://launchpad.net/bugs/1539553
Tyler
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-01-29 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <794484591.224591.1452104561446.JavaMail.zimbra@halfgaar.net>
2016-01-18 10:27 ` Key derivation and passprhase wrapping Wiebe Cazemier
2016-01-20 3:05 ` Tyler Hicks
2016-01-20 19:51 ` Wiebe Cazemier
2016-01-20 20:03 ` Wiebe Cazemier
2016-01-29 22:57 ` Tyler Hicks [this message]
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=20160129225710.GD15683@boyd \
--to=tyhicks@canonical.com \
--cc=ecryptfs@vger.kernel.org \
--cc=wiebe@halfgaar.net \
/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).