From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup 1.6.0 crash when attempting to open truecrypt volume if the key is large enough
Date: Fri, 15 Feb 2013 12:51:38 +0100 [thread overview]
Message-ID: <20130215115138.GA28135@tansi.org> (raw)
In-Reply-To: <511DF951.1010606@gmail.com>
On Fri, Feb 15, 2013 at 10:01:05AM +0100, Milan Broz wrote:
> On 02/14/2013 06:06 PM, .. ink .. wrote:> >
>
> I think the GUI widget trimmed so you in fact entered just first 64
> bytes. Check with "display password" option...
> And try commandline, at least I get
> Error: Password is longer than 64 characters.
>
> I really do not like encryption systems which quietly trims anything
> pretending longer password is correct. This is recipe for disaster.
I agree. Never, ever, ever quietly degrade a password. Or other
input data for that matter. Any GUI doing things like this can
only be regarded as fundamentally broken. Silent errors are
unacceptable, except in the one case where verbose errors help
an attacker. That is not the case here.
Arno
> I changed return code for TCRYPT oversized passphrase to -EPERM
> (So it is handled like "bad passphrase", just early, this is way
> I prefer.)
>
> Thanks,
> Milan
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
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
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
prev parent reply other threads:[~2013-02-15 11:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 11:44 [dm-crypt] cryptsetup 1.6.0 crash when attempting to open truecrypt volume if the key is large enough .. ink ..
2013-02-14 13:43 ` Milan Broz
2013-02-14 16:39 ` .. ink ..
2013-02-14 16:57 ` Milan Broz
2013-02-14 17:06 ` .. ink ..
2013-02-15 9:01 ` Milan Broz
2013-02-15 11:51 ` Arno Wagner [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=20130215115138.GA28135@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.