Bug 383960

Summary: SFTP connection always askes for public/private key authentication but connection is already etablished
Product: [Applications] dolphin Reporter: cecoding
Component: bars: locationAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: justin.zobel
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description cecoding 2017-08-24 15:45:55 UTC 
Precondition: Assuming on my system a private SSH Key already exists. 

Steps to Reproduce:
1. open dolphin
2. location > network > add new sftp network folder
3. insert necessary connection information to sftp server. This server has NO public/private key authentication and has nothing to do with my private key
4. a passphrase for my private key appears (why?)
5. insert random password, not the correct one and confirm
6. username/password dialog will appear (great, I need this dialog) 
7. inserting correct username/password and connection will established successfully
8. Leaving dolphin and open it again, navigate to the newly create network folder

Actual result:
The passphrase dialog appears again, but in the background the connection is already establised. 

Expected Results:
No passphrase dialog should appear when the connection is already established via username/password. When setting up the connection a selection between public/private key authentication and simple username/password authentication would be great.

It's not a showstopper, but it's an irritating bug.
Comment 1 Justin Zobel 2020-10-25 00:18:42 UTC 
Can you please confirm this still occurs in a recent version of Dolphin.
Comment 2 Bug Janitor Service 2020-11-09 04:33:44 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2020-11-24 04:34:09 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!