#236 Display password

open
AxCrypt (102)
5
2009-12-05
2009-12-05
Anonymous
No

1. It would be great if there would be an option to display the password upon encryption like in TrueCrypt. Sometimes the user may mistype the intended password twice, and currently there is no mechanism to verify the typed password before encrypting as far as I can see.

2. Would it be possible to add an option not to compress when enctrypting? (something more easily available than editing the registry)

Discussion

  • Hello,

    1. Yes, there should be such an option. I fully agree. I fact, the default for encrypting should be to display the password, and a checkbox selection to hide it.

    2. Well, I'm extremely unwilling to add options and choices that not all users will understand the purpose of. So, I think I'd rather ensure that the time taken to encrypt is negligable instead. The current implementation is not too smart, and uses a temporary file which causes it to take considerable time. This will be fixed in a future version.

     
  • heraldo
    heraldo
    2009-12-05

    Hi Svante. I posted this feature request. Thanks for replying :)

    I just have a question regarding compression. Does the file compression make the file more difficult to recover if a file corruption occurs?

     
  • Kob
    Kob
    2011-04-20

    I would like to add my request that if a user selects to display the entered password, then to automatically disable the PW verification field - as WinRAR does.
    I want to use a very strong PW - about 22 char long, and I usually avoid this due to the effort required to enter this twice.

     
  • It's a thought to disable the verification. However, I'm not too sure... The only real issue users have with AxCrypt is every now and then someone claims that they are entering the right password but it does not work. This is resolved in too many cases by the user figuring out the typo that I really don't think that it's a bug in AxCrypt. I think users are consistently mistyping when they enter the passphrase, and thus the verification is safe-guard that in conjunction with visibility might reduce these case. I'll consider.

     
  • Kob
    Kob
    2011-04-21

    Regarding people compaining about non-working PW:
    I looked up at some old forum complaints, and noticed at least one case where a user had built a new computer and then encountered a problem. I wonder if the user used only a 7-bit ASCII set for his PW, since using the full 8-bit set is keyboard, locale and OS specific, and this may have changed between hardware builds.

    One helpful solution for such cases might be to add a informational label on the PW entry form to let the user know about such a possibility and recommend to store the PW in a safe place...

     
  • Actually, the most common cause for problems after reinstallation of Windows or move to new hardware is that the files are encrypted with EFS rather than AxCrypt (sometimes in addition to) and that the user was not aware of this or the need to export the recovery certificate...