All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Variable data offset for a LUKS volume that uses a detached header.
Date: Wed, 23 Dec 2015 05:26:35 +0100	[thread overview]
Message-ID: <20151223042635.GA27503@tansi.org> (raw)
In-Reply-To: <CAFnMBaRjP0-XttdYmq9VzNam1ZjDgmQBxUQHpqZBg9SUR+x80w@mail.gmail.com>

On Tue, Dec 22, 2015 at 16:39:48 CET, .. ink .. wrote:
[...]
> >> Reason for doing this is an attempt at having a detached LUKS header
> >> capable of unlocking a VeraCrypt volume since
> >> unlocking a VeraCrypt volume takes too long and its annoying.
> >
> > Oh, yes. I did complain to them, never got an answer. I plan
> > to move my Windows machine back to the last Truecrypt, since
> > the one known vulnerability seems not to affect single-user
> > machines anyways.
> >
> 
> Recent versions of VeraCrypt has an option to default to TrueCrypt
> volumes when unlocking
> and hence you can use it the same way you use TrueCrypt and because of this,i
> think its better to continue to use VeraCrypt with the option set to
> use it as if its TrueCrypt.
> 
> You can set the option at: menu->settings->preferences->mount
> options->TrueCrypt mode.

I agree. Thanks for the info, will try that.

> > Currently I am attaching 8 zeros to the pasphrase, so I can unlock
> > my high-entropy passhrase with iteration 10 and not wait 70 seconds
> > in VeraCrypt. Somebody there really has no clue why usability is
> > important and that users should be able to ovverride most things.
> > They may just know more than the developers about their application
> > scenario...
> >
> 
> zuluCrypt can create VeraCrypt volumes with a PIM value of 1 and a
> blank password as minimum
> requirements.

Also good to know. I think I will make it easier on me and just
decrypt, then recrypt with TrueCrypt and use VeraCrypt on that
volume. Takes longer but is 5 minutes of actuial work. 

> 
> > Does anybody know what the status of CipherShed and TCnext is and
> > whether they have more of a clue?
> >
> 
> I peek at their mailing lists at a rate of about once a month and i do
> not think they are going
> anywhere anytime soon[1].

That was my impression as well. Maybe in a year or two they
will have something.

Regards,
Arno

-- 
Arno Wagner,     Dr. sc. techn., Dipl. Inform.,    Email: arno@wagner.name
GnuPG: ID: CB5D9718  FP: 12D6 C03B 1B30 33BB 13CF  B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier

  reply	other threads:[~2015-12-23  4:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 12:00 [dm-crypt] Variable data offset for a LUKS volume that uses a detached header .. ink ..
2015-12-22 13:01 ` Arno Wagner
2015-12-22 15:39   ` .. ink ..
2015-12-23  4:26     ` Arno Wagner [this message]
2015-12-22 13:44 ` Milan Broz
2015-12-22 15:47   ` .. ink ..
2015-12-22 20:31     ` .. ink ..
2015-12-23  4:30       ` Arno Wagner
2015-12-23  6:15         ` .. ink ..
2015-12-23  6:23           ` Arno Wagner
2015-12-23  8:39             ` .. ink ..
2015-12-23 10:50               ` Milan Broz
2015-12-23 12:10                 ` .. ink ..
2015-12-23 12:29                   ` Milan Broz
2015-12-23 22:15             ` .. ink ..
2015-12-24  6:31               ` 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=20151223042635.GA27503@tansi.org \
    --to=arno@wagner.name \
    --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.