I guess a better "mutator" would be something more complex, taking into account your personal habits of writing passwords, likely misspellings like "O" vs "0" if you wrote the characters off the screen, swapped pairs etc. If unsuccessful, the program would increase the number of mutations (breadth first search). Also, it might be worth checking if the 0.5 sec delay is not mostly a loop for preventing attacks. System load might reveal an idle loop, source analysis (profiling?) might reveal a busy loop. Modifying the source of ecryptfs-unwrap-passphrase to directly include your code might help too, as you would save on starting a process each time. -- To unsubscribe from this list: send the line "unsubscribe ecryptfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
