| Summary: | Add "Login As" context menu entry when browsing FTP | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Kai Uwe Broulik <kde> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | jplx256 |
| Priority: | NOR | ||
| Version First Reported In: | 2.1.97 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Kai Uwe Broulik
2013-01-10 01:13:30 UTC
Thanks for the suggestion. In principle, one can add entries to the 'Actions' submenu of the context menu without any modifications in Dolphin using a service menu or KAbstractFileItemActionPlugin. However, it might be difficult to use this approach to tell the SFTP kioslave about the username/password. Adding a hard coded menu entry to Dolphin itself seems like overkill for this use case to me. Note that Dolphin's code is quite abstract in the sense that it isn't aware of the details of the different protocols, usernames, and passwords at all. All this is handled by the kioslaves. I see that the situation you describe can be annoying, but IMHO, the best resolution is to have the kioslave ask for a new username/password after a failed login attempt. I can confirm that this happens with SFTP as well and it's very annoying. I just accidentally entered the password for different key than the one that corresponds to the server I wanted to connect to (my .ssh/config specifies the correct key). The connections obviously fails and Dolphin reports a timeout. The server's logs show that it tried to connect using multiple keys (which are all wrong but can the unlocked with the password I gave), then my IP got banned for too many failed logins. This also means that it doesn't honour the `IdentityFile` property given in .ssh/config. I think it should immediately ask for the password again after a failed connection attempt, instead of stubbornly trying again until the server mistakes it for a bot. In addition, I also think an option the reenter the credentials, as suggested in the original report, would be a good idea. |