Issue 6124 - ssh tunnel doesn't work anymore
Summary: ssh tunnel doesn't work anymore
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: _openoffice.org CVS (obsolete) (show other issues)
Version: current
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-26 01:32 UTC by Martin Hollmichel
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Martin Hollmichel 2002-06-26 01:32:08 UTC
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@       WARNING: POSSIBLE DNS SPOOFING DETECTED!          @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The DSA host key for openoffice.org has changed,
and the key for the according IP address 64.125.133.202
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the DSA host key has just been changed.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts2 to get rid of this message.
DSA host key for openoffice.org has changed and you have requested strict checking.
Comment 1 Unknown 2002-06-26 01:39:10 UTC
Martin,

Once you remove the listing for Openoffice.org in your 
/root/.ssh/known_hosts2 file the tunnel will function properly (though
the message itself is quite frightening).

Kat
Comment 2 Martin Hollmichel 2002-06-26 01:44:07 UTC
the workaround is to use IP address instead of DNS name, Prio reset 
to 2.
Comment 3 Unknown 2002-06-26 01:52:18 UTC
Martin,

To get rid of the message and still use the domain name, you will need
to edit your .ssh/known_hosts2 file and re-accept the new host. There 
is nothing more we can do. Closing the issue.

Kat
Comment 4 Martin Hollmichel 2002-06-26 02:10:14 UTC
ok this works
Comment 5 lsuarezpotts 2002-06-26 18:43:05 UTC
Hi am using this issue for all.
If you have established a tunnel, you will see this:
 
Last login: [date/location]
   
    #####################################################
        #                                                   #
        #       Unauthorized use is prohibited.             #
        #       Violators will be prosecuted.               #
        #                                                   #
        #       If you make any major changes to this       #
        #       host, record it with the script             #
        #       change_log.sh. and please use (vi)rcs       #
        #       when requested.                             #
        #                                                   #
        #####################################################

                s002.sfo.collab.net (SUNW,Ultra-80)
                SunOS 5.8 sparc
                2048 MB RAM / 5677 MB SWAP
                (2 x 450 MHz) processors

                INSTALL DATE: unknown


that is as it should be.
-louis 
Comment 6 michael.bemmer 2003-03-13 11:09:08 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.