From: Heinz <wurzelsepp1337@web.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] question regarding Sha1 and 512 bit key xts mode
Date: Wed, 26 Aug 2015 12:51:48 +0000 (UTC) [thread overview]
Message-ID: <loom.20150826T143643-652@post.gmane.org> (raw)
In-Reply-To: 20150822135843.GA1028@tansi.org
Arno Wagner <arno@...> writes:
> SHA1 is a "best possible" for this case. Seriously.
Okay. I always strive to understand, and i'm interested in the respective
backgrounds.
> Not to "break" it. To reverse it in one instance.
> To break it, you have to compute that table.
Okay probably not so simple.
> > Okay respect brute-force attacks is a key space of 16^128 in fact
> > impossible, but why not exploit the maximum of what is possible? :)
>
> Simplicity, use of well-knonw components, prevention of
> over-engineering. All well known and valuable engineering
> practices. Also note that in order to change the hash,
> code has to be changed and that comes with the risk of
> introducing bugs. "If it aint broke, don't fix it" is
> another very important engineering principle.
>
> Listen, I can understand your view. Every budding crypto-nerd
> goes through it, and I certainly have. But it is something
> you eventually grow out of when you understand the larger
> picture.
>
> Regards,
> Arno
>
No problem, i understand what you wanted to tell me, and can understand that
you should definitely consider again the overall picture.
Thanks.
next prev parent reply other threads:[~2015-08-26 12:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 16:31 [dm-crypt] question regarding Sha1 and 512 bit key xts mode anderson jackson
2013-12-11 18:04 ` Arno Wagner
2015-08-22 3:38 ` Heinz
2015-08-22 10:04 ` Michael Kjörling
2015-08-22 14:05 ` Arno Wagner
2015-08-26 12:29 ` Heinz
2015-08-22 13:58 ` Arno Wagner
2015-08-26 12:51 ` Heinz [this message]
2015-08-23 18:51 ` Sven Eschenberg
2015-08-23 19:38 ` Arno Wagner
2015-08-23 20:21 ` Sven Eschenberg
2015-08-24 6:18 ` Milan Broz
2015-08-24 11:54 ` 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=loom.20150826T143643-652@post.gmane.org \
--to=wurzelsepp1337@web.de \
--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.