Hi there!

--
Found key of size 1
Trying to generate a strong key (> 2000 characters)
cut: option requires an argument -- d
Try `cut --help' for more information.
./lukstool: line 168: =: command not found
--

I tested it from the CentOS live CD - worked perfectly, specifically this part..? It's looping because it's striving to find a key of appropriate length and will keep trying, but the keygen routine is faulting.

First thing to check - do you have uuencode? If you don't it'll try to create a key with binary characters which it won't take unless you write it to a file first; I don't want the password to ever hit the hard disk, so I'm using uuencode to ensure the characters are all ANSII.

What are the results of 'lukstool runcheck'?

- Raston

I found a problem with my sudoers file and I had to add some modules in, but it still gives the same error:
Try `cut --help' for more information.
./lukstool: line 168: =: command not found
Found key of size 1
Trying to generate a strong key (> 2000 characters)
cut: option requires an argument -- d
Try `cut --help' for more information.
./lukstool: line 168: =: command not found
Found key of size 1

[test@xen01 ~]$ ./lukstool runcheck
This script was designed on OpenSuSE and BASH - this routine will help verify compatibility with
your particular system. Make sure you review the filesystem and blocksize preferences prior to running.
You need to run 'lukstool make' as root - make sure you can do so. Proceeding..
ReiserFS not found, but filesys correctly set to ext3 - moving on..
Testing complete, looks good. You should be able to use this script without grief.
[root@xen01 ~]# which uuencode
/usr/bin/uuencode

Hmm, Okay - that's not expected..

strongkey=$(head -c 20$total /dev/urandom | uuencode -m - | grep -v "begin-base64 644 -" | grep -v "====" | cut -d "=" -f1)

let's break this down - the strongkey var is the result of the first 2000-ish bytes off of /dev/urandom, which is binary. That's coded by uuencode, and with the -m switch that puts it to base64, and the upper and lower strings are stripped so as to ensure there are no consistent characters (everything in output is nothing but random, always). The cut statement make sure the output is clean, but that's what's complaining - either uuencode isn't outputting as expected or cut is misbehaving.

I'll pull up CentOS on a VM and mess with it; perhaps there's a more universal means of outputting the data we need..

- Raston

I was considering a way to do this without uuencode a little bit ago 'just because', and figure this is the perfect time to do it. The new genkey routine is more CPU intensive and as a result takes longer, but the results remain excellent and the routine will be more compatible across the board.

I've run the newest version on a CentOS VM and it worked perfectly - please download the latest update at 'http://www.death-zone.org/luks/luksfile' and see if that resolves what you ran into.

- Raston

Thanks! That worked.

Great! Glad to hear - please use and abuse it and let me know if you run into anything, have questions, enhancement requests, etc.

- Raston