ksssaskpass does not work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ksshaskpass (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ksshaskpass
I am reporting an issue with ksshaskpass that I encountered on Kubuntu Jaunty 9.04 x64 while using SVN/Subversion with NetBeans 6.5.1.
Here is the issue:
1) I installed ksshaskpass (sudo apt-get install ksshaskpass).
2) When I try to import source into Subversion through NetBeans, I get the ksshaskpass dialog, as expected.
3) I enter the passphrase for my SSL connection to the Subversion repository.
4) After that, I ger an error:
"SVN command returned with the following error: kbuildsycoca running..."
However, if I uninstall ksshaskpass, and install ssh-askpass, then everything works fine:
1) When I try to import source into Subversion through NetBeans, I get the ssh-askpass dialog.
2) I enter the passphrase for my SSL connection to the Subversion repository.
3) I am then able to successfully connect to Subversion.
I have also tried launching NetBeans from the command-line with ksshaskpass installed and ssh-askpass *not* installed.
1) When I try to import source into Subversion through NetBeans, I get the following message on the command-line (no ksshaskpass dialog): "Enter passphrase for key '/home/
2) I enter the passphrase for my SSL connection to the Subversion repository.
3) I am then able to successfully connect to Subversion.
So it looks like ksshaskpass is getting invoked, and the dialog appears.
But the ksshaskpass dialog does not seem to pass the pass-phrase back to the invoking application.
Additional infofmation:
My NetBeans SVN setup is pretty standard, so I do not think this is an SVN or NEtBeans issue. This setup works with SVN and ssh-askpass, but not with ksshaskpass...
Repository URL: svn+ssh:
Tunnel Command: ssh -l <user_id> -i /home/<
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.