https://bugs.kde.org/show_bug.cgi?id=424063
--- Comment #9 from lestofant...@gmail.com --- Of you want to encrypt i see no need for any complication, is saving only the hash that will make complications on editing older values. They array of temp hash will make possible to delete right to left but not delete/edit the middle On Mon, 13 Jul 2020, 18:11 Nate Graham, <bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=424063 > > --- Comment #8 from Nate Graham <n...@kde.org> --- > (In reply to Ivan Čukić from comment #7) > > It will hide *and* clear the field. This is to follow the new screen > locker > > policy (or did I dream it Nate?). > Nope, you're right and that's the case now. :) > > > > > Password reveal button is useful, though it kills the point of having a > long > > passphrase :) > > > > The main issue I have with it (apart from the over-the-shoulder ones like > > this bug was) is that in order to have the reveal button, the string > needs > > to sit in memory unencrypted. If password fields were simpler (no > reveal, no > > left-right arrow keys, no random character deletion/change), each char > could > > be encrypted as soon as it is entered without decrypting the old ones. > Could we not still encrypt each character in memory but store them all in > an > array to preserve the above-mentioned features? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
