From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Bug in cryptsetup?
Date: Sun, 20 Jun 2010 21:54:52 +0200 [thread overview]
Message-ID: <20100620195452.GB14850@tansi.org> (raw)
In-Reply-To: <1276986375.16395.22.camel@fermat.scientia.net>
Hi Chris
I think adding a trace to each FAQ article is overkill.
I also do not expect to put a lot into the version specific
section.
While the FAQ should be correct, current, etc. it is
significantly better to have one that is actually there than
one that is overengineered enought that it never gets written.
I also think that I do a pretty good job of checking what I
put in there without being one of the developers...
As to the security questions you raidse, you are welcome to
contribute the relevant articles to the FAQ, just send them
to me or to wait until I find the time to add them. Could
take a while thogh.
Arno
On Sun, Jun 20, 2010 at 12:26:15AM +0200, Christoph Anton Mitterer wrote:
> Hi Arno.
>
> Nice to see that you've used a separate section for legacy stuff in the
> FAQ :)
>
> I guess for something like crpytsetup (with its active development and
> changes to crypto theory) it's important for a FAQ that it's really
> always up to date and double checked for correctness by the developers.
>
> Therefore, may I suggest to add information to each FAQ point for/during
> which version of cryptsetup it was created?
> Of course this would required to check all entries again when a new
> version comes out (whether they still are correct) and update the
> version info.
>
>
> btw: May I suggest to add the questions I put up here some weeks ago ...
> about which is the "securest" algo, keysizes when using XTS,
> essiv/benbi/plain when using XTS, how the masterkey is generated
> using /dev/urandom (at least currently) and that one should not manually
> use /dev/random as Milan said, etc.
>
> It may also be nice to add that LRW is insecure, at least this is the
> case AFAIK, and that therefore XFS was created.
>
>
> Cheers,
> Chris.
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2010-06-20 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-19 17:20 [dm-crypt] Bug in cryptsetup? Si St
2010-06-19 20:16 ` Heinz Diehl
2010-06-19 21:50 ` Milan Broz
2010-06-19 22:13 ` Arno Wagner
2010-06-19 22:26 ` Christoph Anton Mitterer
2010-06-20 19:54 ` Arno Wagner [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-20 12:54 Si St
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=20100620195452.GB14850@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.