Chris Beck <cbeck@gene.concordia.ca> wrote on 12/08/2004 12:52:39 PM:
> It is whispered that Philipp Schneider was heard, on or about 12/08/04
12:32 to say:
> > thanks for your help. I found the article.
> > But I think I dont get it.
> > My server (berlios.de) has not keys for svn, or I dont know how to get
> > them. I have a username and a password.
>
> Normally with SSH, the first time you connect to a server it saves that
> servers public key so the next time you connect to it, you can see if
you are
> talking to the same server. So if subclipse tries to connect to the
server
> and can't find/save the server key it chokes.
There is a similar issue when using the https:// access method. To
resolve it for that, you just use the svn command line and run a command
like svn ls against the server. The command line will then ask you to
accept the server certificate. If you accept it permanent, then it is
cached locally and Subclipse can then work. Perhaps you can do something
similar for ssh? Try to use the svn command line and access the
repository. See if it prompts you to accept some credentials from the
server, and if it does, just accept them permanent.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Thu Dec 9 04:55:55 2004