Community
Participate
Working Groups
When team/cvs/ssh prompts for passphrase info, I see the following dialog box: Passphrase for C:\Document and Settings\hlavana\ssh\id_rsa User name: [ ] Password: [ ] ^^^^^^^^^ I would like to see "Password" string in the last line replaced with "Passphrase" to make it explicitly clear. I have often ended up providing my password here because it is very easy miss reading of the first line where it mentions that it is expecting a passphrase. PS: This issue is also seen in RSE (bug 261740).
Changed the summary to reflect the actual problem rather than the solution. Previous value was: change password label to passphrase in its dialog box I think that the fix must go into org.eclipse.jsch.internal.core.UserInfoImpl#promptPassphrase(String) since it cannot call #promptSecret(String,boolean) which is also used for the password. One option is to change the signature of promptSecret into #promptSecret (String msg, String secretLabel, boolean includeLocation) such that the "secretLabel" would specify what kind of secret is being prompted for. The problem here is that this relays into IUserAuthenticator which doesn't provide this "secretLabel" support yet, and we'd thus need to make an API change involving IUserAuthenticator2 (Well it's likely we won't get away without API changes anyways).
Created attachment 123214 [details] CVS passphrase dialog
Created attachment 123215 [details] CVS password dialog The password dialog is shown when clicking CANCEL in the passphrase dialog; this is not obvious. Also, it's unclear why the password can be stored in secure storage but the passphrase can not.
When asking for community help, could the Platform Team explain the relationship between jsch.UserInfo / IUserAuthenticator as well as the mechanics of caching the password in Equinox secure storage? I'm not quite sure at this time as to what would be the right approach getting this fixed.
(In reply to comment #3) > The password dialog is shown when clicking CANCEL in the passphrase dialog; this > is not obvious. This is probably the same fallback you would see if you ssh'ed to the host with putty. When asked for the password and pressed enter, you would be asked for the password. I _guess_ this may depend on ssh daemon configuration.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
