New 'MPW Hash Mis-Match' dialog

[tanstaafl]

This is a FR for a new 'MPW Hash Mis-Match' dialog window when the MPW Hash doesn't match the Stored Hash.

Currently, when using auto-populate, if the Hash of the MPW has been saved for an Account, if the user enters the wrong MPW (Hashes don't match), the 'OK' button is the default behavior for when the 'Enter' key is pressed, and PWM just goes ahead and populates the wrong generated password.

With this in mind, I propose that the MPW prompt function, whether initiated by the auto-populate feature, or user initiated, should be changed to work in the following manner...

Given that the user has correctly stored the MPW Hash and enabled auto-populate for Account X, and has not elected to store the MPW on disk:

• User navigates to the site for Account X
• PWM prompts for MPW (whether by auto-pop or user initiated)
• User typos the MPW, causing a Hash mismatch, and hits 'Enter'
• PWM should pop-up a different dialog - similar to the one that it currently pops-up if the user hists 'Enter' without entering anything for the MPW - informing the user that the MPW hash of the entered PW doesn't match the Hash that is currently stored for this account, and give the user 3 options (buttons):
  
  
  • 'Re-enter MPW' (default)
  • 'Continue'
  • 'Replace Hash'

[Eric H. Jung]

Excellent suggestion. Add my vote to it, please.

[tanstaafl]

Done...

[tanstaafl]

Hmmm... I just noticed that this request is very similar to the request from Romeo to don't auto-populate username if MPW not entered correctly... should we combine these somehow? Or just leave them separate, but if/when you get around to implementing one, you could do the other at the same time (since it looks like it would be affecting the same code)?

[Eric H. Jung]

Please combine the two. They are nearly identical.

[tanstaafl]

Done...

[tanstaafl]

Eric - read the first post for this FR, then...

Do you have any plans/interest in expanding on the current behavior in line with what I initially suggested?

If not, I'll close this FR as 'fulfilled' by the new release.

I do still like the idea of having the three options, rather than it just refusing to go any further, but it really is not a big deal... I started to just mark this one as fulfilled/closed anyway, but decided to ask, since you seemed to like the original idea (enough to put down a vote from yourself for it)...

[Eric H. Jung]

If you don't need it/won't use it, let's remove it because that means one more thing I can work on that will be used.

[tanstaafl]

If you don't need it/won't use it, let's remove it because that means one more thing I can work on that will be used.

Agreed and done...

The following get one vote back:

jonathankpa, Romeo, LkonKbd, Eric H. Jung