This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 174948 - [terminal][ssh] Terminal asks for host key although RSE ssh connection did not ask
Summary: [terminal][ssh] Terminal asks for host key although RSE ssh connection did no...
Status: CLOSED WORKSFORME
Alias: None
Product: Target Management
Classification: Tools
Component: Terminal (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 minor (vote)
Target Milestone: 4.1   Edit
Assignee: dsdp.tm.core-inbox CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-21 07:50 EST by Martin Oberhuber CLA
Modified: 2016-06-05 21:51 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Oberhuber CLA 2007-02-21 07:50:39 EST
Setup Eclipse Preferences to an SSH Homedir with existing private key (no passphrase) and known_hosts.
Connect RSE "SSH Only" to build.eclipse.org without password.
--> It connects without further questions.
Connect Terminal-ssh to build.eclipse.org, timeout 60, no password
--> Dialog is shown "The authenticity of build.eclipse.org can't be established"

This dialog should not be shown if the ssh homedir is correctly set up.

-----------Enter bugs above this line-----------
TM 2.0M5 Testing
installation : eclipse-SDK-3.3M5 (I20070209-1006), cdt-4.0M5, emf-2.3M5
RSE install  : RSE-SDK I20070219-1645 + discovery + efs
java.runtime : Sun 1.4.2_13
os.name:     : Windows XP 5.1, Service Pack 1
------------------------------------------------
systemtype   : Unix-ssh / Linux-dstore-processes
targetos     : Red Hat Enterprise Linux WS release 4 (Nahant Update 3)
targetuname  : Linux parser.takefive.co.at 2.6.9-34.EL #1 Fri Feb 24 16:44:51 EST 2006 i686 athlon i386 GNU/Linux
targetvm     : Sun Java HotSpot(TM) Client VM (build 1.4.2_13-b06, mixed mode)
------------------------------------------------
Comment 1 Martin Oberhuber CLA 2007-02-21 08:08:55 EST
The problem seems to be that 
1. Ssh homedir is not correctly fetched from the Preferences. 
2. The jsch instance is not shared between Terminals and RSE, since I can 
   connect correctly in Terminal B but it consistently fails in Terminal A.
3. Sessions are not re-used. There should be a simple session cache as long
   as there are multiple connections to the same host.
Comment 2 Martin Oberhuber CLA 2008-06-09 19:54:32 EDT
Will need to look at this in 3.0.1
Comment 3 Martin Oberhuber CLA 2008-09-30 09:04:42 EDT
bulk update of target milestone
Comment 4 Martin Oberhuber CLA 2010-02-26 19:09:54 EST
Bulk update of target milestones to 3.2
Comment 5 Martin Oberhuber CLA 2011-01-12 15:43:04 EST
Check for 3.2.2
Comment 6 Martin Oberhuber CLA 2016-06-05 21:51:10 EDT
The host key message has been working reasonably recently.
I'm closing this issue as WORKSFORME since RSE is no longer actively maintained.