Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 340326

Summary: CVS keeps asking for password to decrypted private keys
Product: [Eclipse Project] Platform Reporter: ck <registerallweb>
Component: CVSAssignee: platform-cvs-inbox <platform-cvs-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3    
Version: 3.5.2   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug
Attachments:
Description Flags
The password required dialog none

Description ck CLA 2011-03-17 11:22:36 EDT
Build Identifier: M20100211-1343

I've connected to my cvs server using extssh and public key authentication

When the key is not encrypt, there is no problem, it could update,commit file to repository but after I encrypted my private key with 'ssh-keygen -p' dialog named Password Required keep pop up asking for key password even my password is corrected until dialog asking for password to access server show up and it failed to connect to server

I have tested on Windows machine and it just ask my password once and can update/commit as usual

Reproducible: Always

Steps to Reproduce:
1.Encrypt private key for using to access CVS server with command 'ssh-keygen -p'
2.Open Eclipse and try to update repository
3.Dialog named Password Required pop up asking for key password
4.Enter key password and hit OK
5.Dialog show up again again again until dialog asking for password to access server show up and it failed to connect to server
Comment 1 ck CLA 2011-03-17 11:26:33 EDT
Created attachment 191430 [details]
The password required dialog
Comment 2 Eclipse Webmaster CLA 2011-03-17 11:52:16 EDT
Moving to platform as this doesn't seem to involve the Webmaster(s).

-M.
Comment 3 Lars Vogel CLA 2019-11-08 04:40:12 EST
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.

If the bug is still relevant please remove the stalebug whiteboard tag.