July 29Jul 29 When editing an item, pasting a new password into the masked password field does not correctly replace the existing value.Steps to reproduce:Open an item that already contains a password.Enter edit mode while keeping the password masked.Select the password field and paste a new password.Save the item or click the icon to reveal the password.Actual result:Part of the previous password remains at the beginning of the field, followed by the newly pasted content. In addition, when the item is saved, the new password is not stored correctly, even if the user does not reveal the field before saving.Expected result:Pasting a new password over the selected content should completely replace the previous value, and the new password should be saved without any changes.Enpass version 6.12.5 (2659) Edited August 6Aug 6 by Send Zero GIF Added
July 29Jul 29 I'm having the same problem, and I was wondering why several of my saved passwords - which I had recently edited - weren't working anymore, but now I know why. I hope this gets fixed soon. A bug like this really shouldn't happen in a password manager... Edited July 29Jul 29 by SVM
July 30Jul 30 We have forwarded the details to our technical team for further investigation. We will keep you updated as soon as we have any new information.SI-4877
September 6Sep 6 Is there any news on this? It has now been more than a month, and such a serious bug should be fixed as quickly as possible.I run into this issue constantly, and it results in incorrect passwords being saved in Enpass. Because of this, I have already been unable to log in to multiple services whenever I forgot to reveal the contents of the password field first before saving the entry after changing a password.This is a workaround that I have to remember every single time, and especially for other Enpass users who are unaware of this issue, there is a very high risk of losing access to their services when they try to change a password, enter the new password into the password field, and simply click the save button - exactly as one would normally expect to be able to do (and as had always worked without any issues before the major Enpass update).I therefore still hope that this bug will be fixed as soon as possible.Of course, there are other bugs that should be fixed as well, but especially in this case, since the issue affects one of the password manager's core functions and can cause serious problems there, I believe fixing this bug should be given a high priority.
September 15Sep 15 I have now updated to the latest version 6.12.6 (2723), which was released yesterday, and unfortunately the issue still persists completely unchanged...By the way, the issue also occurs when manually typing the new password in the masked password field. It is not limited to pasting it.Interestingly, the issue does not seem to occur with a text field that is marked as sensitive/confidential. As far as I can tell, it "only" affects fields of the "Password" type. Perhaps this information will help with analyzing and fixing the issue.Considering that this affects such a fundamental function of a password manager and can potentially lead to users being locked out of their accounts, it is very disappointing that the issue is still present in the latest release. I hope this will be addressed with high priority. Edited September 15Sep 15 by SVM
September 15Sep 15 I tested this and can also confirm this issue. What I also discoverd is, that you will not face this issue, if you use "Show Password" before pasting the new one. Rather than pasting over the censored password, make it clear text and paste the new one, and it works. Seems to me, like with the censoring some kind of read-only is in place for the characters already present. A longer password will be added to the end, eg.:old: 12345678 -> to be replaced with abcdefghijkl new: 12345678ijkl
September 15Sep 15 Yes, I noticed the same thing, and since I first ran into this bug in Enpass, I've been using this as a workaround to replace a password.However, I've also come very close to forgetting to do that a few times. In that case, I could easily have saved an incorrect password without noticing, which might have caused some serious problems later on.I'm glad there's at least a way to still change a password correctly in Enpass, but of course it's far from ideal. Edited September 15Sep 15 by SVM
September 15Sep 15 19 minutes ago, SVM said:Yes, I noticed the same thing, and since I first ran into this bug in Enpass, I've been using this as a workaround to replace a password.However, I've also come very close to forgetting to do that a few times. In that case, I could easily have saved an incorrect password without noticing, which might have caused some serious problems later on.I'm glad there's at least a way to still change a password correctly in Enpass, but of course it's far from ideal.Couldn't agree more with you!
September 17Sep 17 Thank you for following up. Our team is still investigating the issue and working toward a fix.We understand the impact of this issue and appreciate your patience. We’ll share an update as soon as we have further information.
Create an account or sign in to comment