All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Lefebvre <alto.spam@laposte.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] zuluCrypt v3.0 released.
Date: Wed, 05 Oct 2011 17:07:34 +0200	[thread overview]
Message-ID: <4E8C72B6.1040302@laposte.net> (raw)
In-Reply-To: <CAFnMBaQExk2dm-jQwoXpJ0W0gtO74zATJVkOUoREy0r7SXvZpg@mail.gmail.com>

Hi,

This looks like a very nice project.

On 05/10/2011 08:28, .. ink .. wrote :
> project page: http://code.google.com/p/zulucrypt/
> 
> screenshots of the new release:
> https://picasaweb.google.com/109794855728648275729/ZuluCryptV30?authuser=0&feat=directlink
> 
> video showing features of the new release:
> https://docs.google.com/leaf?id=0B8juRKTjN4Q9Njk0MTY4OWQtODcyMi00MGY2LTg5ODktOTg2MGYyNGRiNzI1&hl=en_US
> 
> This release put cryptsetup/zuluCrypt at the same level as truecrypt feature
> wise when used from the GUI.
> 
> It can now (from the GUI)
> 1. Create key files( 512 bytes in size composed of only the 94 printable
> characters).

512 bits rather than bytes ?

> 2. Create volumes both in files and partitions.
> 3. Create both plain type and luks types volumes.
> 4. Add keys to luks type volumes.
> 5 . Delete keys from luks type volumes.
> 6. Close a bunch of bugs.
> 
> All volume management can be done through either passphrases or key files.
> 
> The core functionality is now in place and next version(version 4) will be
> for GUI user configuration options of things like font type, font size, use
> of tray icon and maintaining a list of favorite volumes.
> 

I just took a look at the screenshots and I'm a bit surprised about the
fact keys are generated from /dev/urandom. Even for 512 bits, that is 64
bytes, wouldn't it be better to read key files from /dev/random ? Unless
there is a setting allowing the user to explicitly choose the source ?

Best,
Quentin

  reply	other threads:[~2011-10-05 15:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05  6:28 [dm-crypt] zuluCrypt v3.0 released .. ink ..
2011-10-05 15:07 ` Quentin Lefebvre [this message]
2011-10-05 15:39   ` Arno Wagner
2011-10-05 16:13     ` Milan Broz
2011-10-05 18:26       ` .. ink ..
2011-10-05 21:36         ` Arno Wagner
2011-10-05 18:18   ` .. ink ..
2011-10-06  1:27     ` .. ink ..
2011-10-06  8:36       ` Quentin Lefebvre
2011-10-06 14:27       ` Arno Wagner

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=4E8C72B6.1040302@laposte.net \
    --to=alto.spam@laposte.net \
    --cc=dm-crypt@saout.de \
    /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.