Summary: | Only one attempt to enter correct password; it will not be asked a second time | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | Enrico Tagliavini <enrico.tagliavini> |
Component: | general | Assignee: | KIO Bugs <kio-bugs-null> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | a.samirh78, elvis.angelaccio, frambooisier, jan.rathmann, kapsh, kdelibs-bugs, nate, simonandric5, vkrause |
Priority: | NOR | ||
Version: | 5.38.0 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Enrico Tagliavini
2017-10-21 21:38:59 UTC
This is on Fedora 26, Plasma 5.10.5, dolphin 17.04 Confirmed. There is a workaround though, run 'kquitapp5 kiod5'. This will kill the kpasswdserver module which is responsible for the authentication. There is another problem with this behaviour: Even if you entered the correct password, there may be usecases where you want Plasma/KIO to discard the password you have entered for the network share to effectively terminate the connection and require the password to be entered again on further access. This would not be a problem if there was a GUI option in Dolphin or FileDialog to explicity disconnect/terminate a KIO network connection, but there isn't any, as I'm aware of. And it seems a bit confusing to me that KIO doesn't respect the settings for Kwallet under Systemsettings -> KDE password storage. Even if I have disabled KWallet completely, passwords for network shares are stored/not asked again until I log out of the session or do 'kquitapp5 kiod5'. It would seem more intuitive to me that if e.g. storing passwords with KWallet is disabled, passwords for network shares would be discarded when the application that accessed the share (e.g. Dolphin) is closed. Allthough the issue of not asking for wrong passwords again and the issue of not offering an "easy" way to discard entered passwords during the session seem to be related to the same underlying problem (-> how this is currently handled by KIO), I wondered if it would make sense to open a separate report for the latter case? (In reply to Elvis Angelaccio from comment #2) > Confirmed. There is a workaround though, run 'kquitapp5 kiod5'. This will > kill the kpasswdserver module which is responsible for the authentication. Thanks for the tip. I also confirm that the bug still exists on OpenSuse Tumbleweed build 20210913. |