Bug 71832 - [SSH2] Multiple ssh keys for the same cvs host not handled properly
Summary: [SSH2] Multiple ssh keys for the same cvs host not handled properly
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.0   Edit
Hardware: PC Linux
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2004-08-11 17:01 EDT by David Minor CLA
Modified: 2019-09-06 16:19 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Minor CLA 2004-08-11 17:01:46 EDT
We have multiple (chrooted) ssh servers running on different ports of our cvs
server and using different host keys, but Eclipse only looks for one key in
known_hosts (the first key it finds). If you have shared projects that use
repositories on different ports, Eclipse will only work with the server whose
key is listed first in the known_hosts file.

Two workarounds:
1. Keep multiple copies of known_hosts, and close Eclipse and switch them when
you want to synchronize with a different server.

2. (Linux) Edit your /etc/hosts and add a bogus host name for the server ip, and
use that name when adding the repository to Eclipse. This will trick Eclipse
into thinking it's a different machine.
Comment 1 Olivier Thomann CLA 2004-08-12 11:14:29 EDT
Move to Platform/CVS
Comment 2 Jean-Michel Lemieux CLA 2004-08-31 08:36:43 EDT
Thanks for the workarounds.
Comment 3 Atsuhiko Yamanaka CLA 2007-06-24 23:37:18 EDT
Since Eclipse SDK 3.3(which used jsch 0.1.31), if the standard port number(22)
is not specified, the given port number will be saved in 'known_hosts' file,
as the recent OpenSSH's ssh clinet has done.

So, you don't have to do such workarounds mentioned at comment #1.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:19:03 EDT
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.