Password Spaces Bug

Tomb 1.0 hase a bug. A VERY GRAVE BUG. Passwords containing odd characters where badly interpreted: this means that if you password was I am 12!! perfectly 7^!@^#38123 secure, it could have been understood by tomb as I. yes, it was "splitted" at the first odd character. And yes, you thought to have a really great passphrase. Instead, you were using a single character one. Try it yourself, even with an old release of tomb. You might be able to open your tomb using just I as password. Now, this bug has been fixed. This, however, won't fix the tomb that you created and used. You need to create a new one, move the content, then securely delete the old tomb and the old key.

If you still use tomb 1.0, you have to do it the hard way:

• create a new tomb, and use a password with no spaces
• move the content from the old to the new one
• WIPE the old tomb and, most importantly, the old key (actually, wiping the key shoudl be enough). Please note that you shouldn't just delete the file; you have to securely delete it. There are lots of tools that can do it, altough their effectiveness is debated, especially on journaling filesystems, like ext3/ext4.