passing keyfiles and missing GUI password dialog

[Anonymous]

In truecrypt, when multiple keyfiles are passed as command line arguments in nontext mode, a GUI password dialog opens with the passed keyfiles pre-selected.

In veracrypt, no GUI password box opens(except the one for admin needed for mounting) and only after waiting for the mount to fail does the password box open with the passed keyfiles pre-selected. If the '-tc' truecrypt mode option is passed to speed up the timeout, the keyfiles are not pre-selected and have to be manually re-selected.

Is there a way to initially force showing the GUI password box when passing keyfiles via command line without passing the password directly or waiting for the missing password to fail? Adding '--display-password' doesn't work and there is no '--interactive' equivalent. The '-t' text mode option will ask for the password from the command line but want the GUI password dialog to open from a script without opening a separate terminal mirroring behavior in truecrypt.

Alternatively, would it be possible to add a cancel button to the 'Please wait... This process may take a long time...' popup dialog without risking damage to the volume? The cancel button here would also be useful if the wrong password or keyfiles are input which is evident when the mount delay exceeds normal mount time of a few seconds.

[Mounir IDRASSI]

First, it appears you are running under Linux which is important to note since there are differences between Windows and Linux.

There is no difference between TrueCrypt and VeraCrypt in the case you are describing: the only thing is that TrueCrypt is quicker for checking password/keyfiles and that's why it seems as if TrueCrypt password dialog opens automatically whereas in reality TrueCrypt tries to load the volume using the passed keyfile and after it failed it displayed the password dialog.

There are two points that I get from this:

1. the -tc changes the behavior of the password with regards to the keyfile parameter. This is not normal and it will be looked at to implement a fix.
2. you want to force showing the GUI even if you passed a keyfile in the command line. This is not supported by TrueCrypt nor VeraCrypt. I think the best solution for this case if to have another switch for passing this keyfile in order for it to be considered as default one.

Concerning the cancel button on the waiting dialog, I understand its need. On Linux/MacOSX, it should be possible to implement one. On Windows, it is more tricking as the processing is done on the driver side and for now I don't see how this can be implemented.

[Anonymous]

"...TrueCrypt is quicker for checking password/keyfiles and that's why it seems as if TrueCrypt password dialog opens automatically..."

Thanks! This is clear now that you point it out. Sorry for not considering the delay differences before posting.