Hi Ate, I had an issue in getting it to work as well. I'm not sure what fixed it. Anyhow here were my steps outlined below:
1) Window > Preferences > Team > CVS > Extssh Connect Method > Key management Generate DSA Key > Save private key and Export Public Key 2) Click Apply and Closed Pref Dialog 3) Re-opened pref dialog again > Load existing key > Apply again. After that I'm prompted for my key store passphase instead of the minotaur password (during a commit.) Bugger though I just closed and re-opened Eclipse and the setting is back to straight password. So next I try this: Disconnect and Rename to "_old" any projects using the connection (or delete if possible) Discard the connection Close and Restart Eclipse Create the connection again Check out a new copy of the project ... run maven eclipse ... etc ... made some file changes ... Closed Eclipse / Reopen (to verify the prompt on commit) Now prompted for id_dsa passphrase on commit. I'm not sure that helps you. It was buggy and I think the connection properties were cached either in memory or on disk which is why I did the close/reopens and the fresh checkouts to new projects. Anyhow maybe it'll help. -TR > [Ate Douma wrote] > Sent: Thursday, July 22, 2004 6:37 AM > To: Jetspeed Developers List > Subject: Using Eclipse 3.0 extssh to connect to cvs.apache.org > > > After I upgraded to the latest Eclipse I thought of trying out extssh for > connecting to cvs.apache.org (using ssh key pair, *not* my password). > This works beautifully for retrieving but fails for committing. > > I now resolved back to using a localhost tunnel with Putty which > also works > great but requires an extra step to set it up. > If possible I'd like to use the extssh connection so anymore > knows if/how to get > this working? > > Regards, > > Ate Douma > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
