On Sun, 2010-02-21 at 18:55 +0000, Steve Langasek wrote:
> (I don't consider this incomplete, the question about initramfs
> selection is most likely orthogonal to cryptsetup not supporting
> /dev/disk/by-uuid syntax)
> 
> ** Changed in: cryptsetup (Ubuntu)
>        Status: Incomplete => New
> 

http://code.google.com/p/cryptsetup/

The packaged cryptsetup in Lucid is a Release Candidate. (1.1.0-rc2)
Since then rc-3, rc-4 and the final 1.1.0 has been released.
There have been at least a dozen bugs fixed since rc-2. I suggest
upgrading the package to the final stable version. While it may not fix
any of the experienced problems, it can at the very least attempt to
rule out the actual cryptsetup package as the problem. Furthermore it
may also prevent further since that have already been fixed and the
1.1.0 is marked as stable. I would like to see this package updated.
I will be testing cryptsetup for Lucid, however I will be using
non-default modes (aes-xts-benbi). This is off topic but the XTS code
has been in the kernel for a while, and it computes test vectors
correctly. I have used XTS mode with no problems. Switching to something
that is *standardized*  rather than just created to counter CBC attacks
(ESSIV) would be preferred. XTS has most likely received more attention.
It is also  *standardized* in IEEE P1619. "CBC-HMAC-SHA" is also
standardized in P1619, which is similar to ESSIV algorithm. However the
ESSIV algorithm is more complex, from what i have read simple is good
for an algorithm. AES is a good choice for the default encryption
algorithm, however with the recent AES 192-256 attacks AES128 seems to
be a better choice. AES128 is faster and 128 bits more then enough
security for most peoples needs.  I also have a question about the Lucid
defaults. Since hashes besides SHA1 (--hash) are now accepted will
SHA256 be used by default? 

My two cents.

-- 
crypttab entries not processed automatically at startup despite upstart files
https://bugs.launchpad.net/bugs/522341
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to