https://bugs.kde.org/show_bug.cgi?id=384051
Moritz Bunkus <kde@bunkus.online> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kde@bunkus.online
--- Comment #7 from Moritz Bunkus <kde@bunkus.online> ---
I just came over here to finally report this myself after being annoyed by it
for many, many years. I'm using a rather long passphrase for aqbanking's
certificate, and mistyping it is common occurrence. kmymoney not recognizing
this and me having to restart kmymoney is incentivizing using shorter, easier
to type and hence less secure passwords. Instead, a program dealing with such
an important topic should make it easy to do the right (the secure) thing.
Ideally kmymoney should figure out that updating accounts through aqbanking
failed due to a wrong password and un-cache the password.
I can imagine, though, that the API doesn't expose this kind of detail, only
whether or not the update succeeded. If this is indeed the case, I'd very much
appreciate if kmymoney always un-cached the passphrase when aqbanking fails to
update. If that seems too hostile to the user[1], making this behavior optional
via the settings would be totally fine.
[1] Of course aqbanking might fail for reasons other than wrong passphrases —
network outages, DNS not working, the bank's servers not being reachable etc.
--
You are receiving this mail because:
You are the assignee for the bug.
